Mouse control issues: Difference between revisions

From OniGalore
Jump to navigation Jump to search
m (link fixes)
m (link fix)
Line 3: Line 3:
Windows 8: Right-click Oni.exe, choose "Properties", go to the "Compatibility" tab, and check the "Disable display scaling on high DPI settings" box.<br />
Windows 8: Right-click Oni.exe, choose "Properties", go to the "Compatibility" tab, and check the "Disable display scaling on high DPI settings" box.<br />
Windows 10: Right-click on Oni.exe and choose "Properties". Go to the "Compatibility" tab. Click on the "Change high DPI settings" button. Check the "Override high DPI scaling behavior" box. Scaling should be performed by "Application".<br />
Windows 10: Right-click on Oni.exe and choose "Properties". Go to the "Compatibility" tab. Click on the "Change high DPI settings" button. Check the "Override high DPI scaling behavior" box. Scaling should be performed by "Application".<br />
Also see [https://pcgamingwiki.com/wiki/Oni#Choppy_mouse.2Fkeyboard_control this PCGamingWIki page] on Oni for a patch that adjusts for monitors which use refresh rates above 60Hz.}}
Also see [https://www.pcgamingwiki.com/wiki/Oni#Choppy_mouse.2Fkeyboard_control this PCGamingWIki page] on Oni for a patch that adjusts for monitors which use refresh rates above 60Hz.}}


There have been many issues reported on {{OCF}} about mouse lag or unresponsive controls. This issue is most common to (or only occurs to?) Vista users. It also occured to me (rossy) but appears to have gone away with the latest drivers/updates to my system.
There have been many issues reported on {{OCF}} about mouse lag or unresponsive controls. This issue is most common to (or only occurs to?) Vista users. It also occured to me (rossy) but appears to have gone away with the latest drivers/updates to my system.

Revision as of 15:07, 17 August 2020

There have been many issues reported on Oni Central Forum about mouse lag or unresponsive controls. This issue is most common to (or only occurs to?) Vista users. It also occured to me (rossy) but appears to have gone away with the latest drivers/updates to my system.

Complete (?) list of Help and Troubleshooting Topics in chronological order

Known facts (symptoms) of the issue

  • (Probably/usually) exclusive to Windows Vista.
  • (Probably/usually) exclusive to multi-core CPUs.
  • Fraps reports the game's framerate to be much higher than 60fps. (I'm unsure whether the same data is returned by Oni's internal framerate counter, Ctrl+Shift+Y)
  • Higher graphics settings can cause the problem to become less noticable as the framerate gets closer to or below 60. (Try 8x antialiasing in the nVidia Control Panel)
  • This suggests that the problem is somehow related to framerate and internal timing issues in Oni.
  • Quote from Gumby "If the game runs much faster than 60 clicks, the mouse input data isn't updated fast enough."
  • The mouse moves in steps, as if it's on a "grid".
  • Combos are hard to pull off as keys are only responsive some of the time, it is also almost impossible to dash.
  • This thing is interesting http://social.msdn.microsoft.com/Forums/en-US/windowssdk/thread/980e5018-3ade-4823-a6dc-5ddbcc3091d5 .

Possible fixes

There is no guaranteed fix; the solutions below have been reported to work by some people but have been ineffective for others. In some cases, a combination of some of these fixes might be necessary.

  • Force V-sync in the Catalyst/NVIDIA Control Panel (confirmed fix)
  • Update your graphics drivers. Do not use Windows Update; instead go to your graphics card's website and download the drivers directly from there. (Nvidia)
  • Run Windows Update. Ensure you are on the latest Service Pack for your operating system.
  • If you have a multi-core system (Pentium Dual Core, Core 2 Duo, Quad, etc.) there are patched EXEs that force Oni to only run on a single core. See here and here.
  • Install the Daodan DLL, which has a "performance patch" that could fix timing errors caused by faulty chipsets. This fix has been reported to work by some people.
  • Run in windowed mode or "-noswitch" mode, if you already use windowed mode run in fullscreen.