In the meanwhile I finished the tutorial zone and my first missions and I still don't have any problems, since changing the SmoothFrameMinimum (to 20) and Maximum(to 30) (while mouse smoothing is active). VSync ist set to TRUE.

The mouse only begins stucking again, when I record a video while playing (so probably if the framerate sinks below 20).

 

I do also own the Steam version of the game. But... why should DRM only break mouse input, and not controller input? That's not the problem I think.

In the meanwhile I finished the tutorial zone and my first missions and I still don't have any problems, since changing the SmoothFrameMinimum (to 20) and Maximum(to 30) (while mouse smoothing is active). VSync ist set to TRUE.

The mouse only begins stucking again, when I record a video while playing (so probably if the framerate sinks below 20).

 

I do also own the Steam version of the game. But... why should DRM only break mouse input, and not controller input? That's not the problem I think.

 

I've mentioned this elsewhere but bear in mind the speed when turning using controller input is usually constant. A mouse movement made by a human hand is usually non-constant. So if the developr is just feeding mouse input to a code routine specifically designed for a console controller, this may be the cause of issues. This kind of thing is extremely common with games poorly ported to the PC from console. The solution is to code specifically for the most popular input devices for the platform, not code for one platform to save time and effort and then just 'force-feed' input from devices on different platforms into it.

 

Just a theory mind