MC-43093Mouse sensitivity affected when limiting FPS or activating VSync
When using vsync, mouse movement is less sensitive than when vsync (and frame limiting) is not active.
With vsync and frame limit off, movement appears to track perfectly and accurately, but as soon as the frame rate is limited to below the level the GPU is capable of, movement appears to track less well.
This is a subtle effect. If the player always plays with vsync on, or vsync off or with the FPS limit set to the same value all the time, they will likely not notice anything amiss.
Environment
Win 8.1 x64, Java 1.7.0_45 (64 bit), NVidia driver 331.93.
Linked Issues
Created Issue:
Mouse sensitivity affected when limiting FPS or activating VSync
When using vsync, mouse movement is less sensitive than when vsync (and frame limiting) is not active.
With vsync and frame limit off, movement appears to track perfectly and accurately, but as soon as the frame rate is limited to below the level the GPU is capable of, movement appears to track less well.
This is a subtle effect. If the player always plays with vsync on, or vsync off or with the FPS limit set to the same value all the time, they will likely not notice anything amiss.
Environment
Win 8.1 x64, Java 1.7.0_45 (64 bit), NVidia driver 331.93.
relates to
This ticket is incomplete without the requested information, no response has been received within a reasonable time and we are assuming this is no longer an issue. If you are still experiencing this issue, we can reopen it at your request.
<wild_guess>Sounds like the mouse position is sampled only in the screen refresh intervals.</wild_guess>
That's exactly what it feels like, but I didn't want to put that in the bug report because it's not something I can be sure about.
This may be related to how LWJGL records input. I've just begun to read how to use LWJGL in my own programs and documentation surrounding handling input seems to indicate that the poll rate can affect mouse input events.
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.
Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket.