Unplayable with Keyboard & Mouse

[Velochiractor]

Ok so this game looks great and can be a ton of fun....
But sadly it's unplayable with keyboard and mouse.
Partialy because of the UI but mainly because of the mouse lag / input stuttering.

You've got two options here for you keyboard & mouse players.
Either you play with vsync on and you'll have about ONE FULL SECOND of input lag on every movement....
Or you turn off vsync and then the camera will be jerky / stutter like crazy giving you headaches after 10 minutes of gameplay. (Footage of mouse lag / stuttering : https://www.reddit.com/r/HiTMAN/comments/98vih2/horrendous_stutteringmouse_lag_after_buying/ )

No ammount of "Switching to DX11, cap your fps, turn down graphics, etc" will help you. The only solution is to grab a controller either you like it or not.

EDIT : video footage more precision in the post below https://www.youtube.com/watch?v=I3AdIem4U4U

[Sandvich]

I'm not having any problems, and I use a keyboard and mouse. This is all on your end.

[Velochiractor]

This work on my machine™

Well I'm glad it work for you guys. But it doesn't for me and a bunch of others according to the comments I found while looking for a solution. And I'm pretty sure my hardware is not at fault here. i5-7300HQ / GTX 1060 / 16 Gb DDR4

[Sandvich]

Are you using a wireless mouse?

[makkun・マックン]

Works for me.

[Hotdog 7]

I had the same problem on the first startup. The resolution in the options was on 1920x1080, while my screen is 3840x2160. Setting the correct resolution in the options fixed it for me.

[Velochiractor]

Originally posted by Sandvich:

Are you using a wireless mouse?

I'm not using a wireless mouse but a LG502

Originally posted by Dr.Doctrine:

I had the same problem on the first startup. The resolution in the options was on 1920x1080, while my screen is 3840x2160. Setting the correct resolution in the options fixed it for me.

I'm playing on my native resolution(1080p).
Framerate might be what's causing the issue.... But sadly no matter what I try I cannot get it past 60fps.... When I try putting everything on high/ultra/DX12 I have about 40/50 fps and when I try putting everything on low I got about 45/55 fps.... So yeah I don't know what's up here

[Talby]

I did notice a very slight lag and stutter when running on ultra - especially noticeable in Sapienza.

2500k, r9 390, 8gb, win10, 1080p@60

Dropping from ultra to high made it buttery smooth.

[Velochiractor]

Well I managed to make the game run at 70fps on some places. And the stutter remains so I guess the problem is not framerate related (at least to me).

I'll try to record footage later this day to demonstrate what I'm saying.

[Velochiractor]

Here's footage of what I'm experiencing https://www.youtube.com/watch?v=I3AdIem4U4U
Sorry about the steam UI poping from time to time, I blame shadowplay for this as it didn't happen when I was playing and was only visible on the recording.

Also obviously I did my best to do smooth gesture while recording. I don't have parkinson or anything and I was recording with the same setup I use while playing more compettive games like csgo / overwatch / etc

And that was recorded at low settings, DX12, 1080p 70fps. It gets way worse at high settings 45/50 fps.

[JokerVIP [NL]]

Yep works too for me on Keyboard and Mouse ,dont know whats your problem

[geryboy85]

not sure what you're talking about, just finished the tutorial facility.

[LeeIzaZombie]

My only issue with kb&m is not being able to walk slowly, everything else works fine

[gooooood mewing vietnam!]

it's only you, babe.

[Miles]

No issues like that at all and my mouse is on it way out lol

[Ezekial Jeans]

Originally posted by Rawhide:

it's only you, babe.

Not just him. I have the jittery mouse problem as well. For the longest time I thought this was a microstutter issue tied to fps and my monitor, but it is 100 percent coming from the mouse input. Tested with a Razer deathadder. The problem goes away if you use an xbox one controller. I play primarily with a Steam Controller using KB&M binds, so this is a huge bummer. Haven't found a fix yet.