Please update the mouse input and probably input in general so that it is not lost when LFS runs at high FPS.

Was told to post in test patch but then, no feature requests there so posting here.

Input is buggy when LFS runs high FPS above 200.
Also mouse sensitivity especially for steering is missed since LFS was released, WHY? Please redo the mouse input and allow ingame mouse sensitivity adjustment. It's still running the 90s style mouse input where mouse sensitivity is handled by Windows itself, problem is Windows has only a few settings that are worth using, 6/11 = 1, 4/11 = 0.5, 3/11 = 0.25, rest is useless and produces skipping and lag and other irregularity in mouse movement.
Having ingame sensitivity would grand because it is quite a basic feature and not all mice can be adjusted with special mouse software to match the screen resolution and mouse sensitivity with different screen resolutions. Updating to a higher resolution means a loss of ingame sensitivity.

There is a bug thread already with more info about it but no one replies there.

Do you have a bug tracker or feature request tracker where we can add?

Quote from JackCY :

Do you have a bug tracker or feature request tracker where we can add?

No, they use the Improvement Suggestion and Bug report forums for that.

There is no point of running LFS at >100 FPS, because some frames will be pixel to pixel same. In the end visualy its 100 FPS, no matter of your actual FPS.

Quote from DANIEL-CRO :

There is no point of running LFS at >100 FPS, because some frames will be pixel to pixel same. In the end visualy its 100 FPS, no matter of your actual FPS.

No. Just no.

Here is an article about rough ... an example about racing. Granted, it's about lower frame rates than discussed here, but there is no way two frames are ever the same except you're not moving. Also, there is no single argument against higher framerates: more = better, every time. Whether you get to see them is just a matter of your hardware...

Quote from bbman :

No. Just no.
...
but there is no way two frames are ever the same except you're not moving...

In LFS, the outer physics loop (currently) runs at 100Hz. There is (again, currently) no interpolation between physics updates. Therefore no position updates of the cars/view/whatever will happen more often than 100Hz, so if you render faster than 100fps you will get duplicate frames.

Go watch a replay at 0.125 speed and the effect will be obvious.

Quote from Degats :

In LFS, the outer physics loop (currently) runs at 100Hz. There is (again, currently) no interpolation between physics updates. Therefore no position updates of the cars/view/whatever will happen more often than 100Hz, so if you render faster than 100fps you will get duplicate frames.

Go watch a replay at 0.125 speed and the effect will be obvious.

Exactly this

Wanned to make a vid, but nahhhh. Quite obvious in BF1 and slowed down replay, no matter of 300+ FPS, in reality you get only 12.5 FPS ...

Right, I had the tyre physics in mind and forgot that everything else is on another process... My bad!

sorry to continue off topic, but should we then have to limit fps to max 100fps ?

Improve refresh rate of physics to 200Hz can be a solution for people who have 144Hz monitors, any recent CPU can handle it.