[b256] mouse behaviour

elodea

Seems like input delay has been reduced across the board, but it's still especially noticeable when your fps tanks to 30-60. Usually this happens on a beacon with gorges biling things, effects being applied, explosion cinematics, or really any sudden scene that has alot of sudden rendering.

The other part of the mouse problems, which does not seem to have changed much, is sensitivity dropping with lower fps.

Nearly all times these two things happen, there is greater than 0 ms waiting on gpu. This never used to happen prior to the linux build so yea :x.

Ghosthree3

That's because input is delayed for a number of frames (now 2 instead of ...5+?). So the less fps you have the longer those delayed frames last, the more noticeable it is. There really isn't a way to fix that.

IronHorse

According to a 240 fps camera, there is 3 frame delay (from 5 frames) now, which you can lessen one frame further by setting "Maximum pre rendered frames" to 0.. but no promises on whether this helps or hurts you. (was told it might still have adverse effects )

But even at 3 frames, its matching Quake 3's input delay... which is a pretty good achievement.
Be sure to not test these things on biodome for the time being, too, as it can sometimes be a bit GPU heavy.

As for the sensitivity dropping based on FPS, i'll look into it, but what levels of FPS are you accounting for?

philogl

Did something weird happen with sensitivity this patch? I've had to nearly half my sensitivity and still can't get it to feel the same.

Ghosthree3

You now aim as UWE intended phil!

IronHorse

Interested if anyone else has issues with sensitivity being changed based on FPS..
Hard to measure such a thing