VOGONS


First post, by DoZator

User metadata
Rank Member
Rank
Member

In many DOS games that I run on Windows, the mouse works noticeably smoother than in pure DOS. This is especially noticeable in first-person shooters. The reason for this phenomenon lies in the fact that in Windows, the mouse uses USB drivers + MouseWare + HIDUSBF, and thanks to this, it operates at a frequency of 500 Hz (the response time is only 2 milliseconds), which far exceeds the screen refresh rate. As a result, all mouse movements look very smooth:

The attachment MOUSRAT2.PNG is no longer available

In turn, in bare DOS, the mouse works through internal BIOS emulation services as a PS/2 device, and the maximum polling rate is only 200 Hz for a USB optical mouse connected to a PS/2 port via an adapter, or only 125 Hz when connected directly to USB.

I noticed that fresh USB 3.0 (xHCI) drivers for DOS were released just recently, but will they help me fully overclock my mouse to 500Hz so that it works as smoothly and responsively in MS-DOS as it does in Windows? I didn’t find anything about this right away in the driver’s description:

https://github.com/ages2001/WINUSB (New USB driver with MS-DOS support).

Has anyone managed to overclock their USB gaming mouse under DOS to 500Hz or even 1000Hz? What DOS tools and drivers do you usually use for overclocking in DOS?

Reply 1 of 3, by pavunoDev

User metadata
Rank Newbie
Rank
Newbie

I'm thinking that if you experienced really bad mouse responsiveness, it would be much much slower than 200 Hz polling. I can remember there was DOS software using the 18.2Hz clock to poll the mouse (BIOS timer IRQ0 / INT 08h, with the user hook INT 1Ch). Obviously this is so bad it wouldn't be workable for most games, which reprogrammed the PIT, but typically at 60 - 120 or so, especially since most PS/2 mice ran at 100 Hz. That’s the mouse’s power-on default, and it’s what most software left it at. In DOS, the driver owns this setting.

I remember distinctly how Amiga mouse felt so much smoother when I switched to DOS/Windows PCs circa 1993. In fact, it would take several generations of hardware until I couldn't notice the mouse lagging in the screen any longer. But this was because of the hardware acceleration Amiga has specifically for the mouse pointer. Hardware drivers would only be standard in Windows NT and later (2000, XP, etc).

For DOS games like Doom or Quake, mouse input is read per frame, so better framerate is a also better input rate, except it needs to sync with the mouse poll rate (typically 100 Hz). Vanilla Doom's framerate is sh1t, so it doesn't make much difference 35fps cap IIRC. Quake's cap was closer to 100Hz (70? or so) I think it would be noticeable if you tweaked the mouse driver to 200Hz (speaking of the era-appropriate PS/2 mice - potentially more with these new USB drivers?). But honestly I doubt the difference would be noticeable if the polling happened at 200Hz or higher, so long as it's stable without hiccups. At 200Hz stable the mouse input should feel perfect or near-perfect.

As much as I love the DOS era, the truth is that FPS games from the time were really primitive, except maybe Quake 1? Or maybe modern community ports of later games. Maybe that's why I didn't even pay attention to mouse responsiveness in DOS FPS games.

Reply 2 of 3, by DoZator

User metadata
Rank Member
Rank
Member

Hi, thank you for the detailed response, and no, at 200hz it’s still very far from ideal. Any user sensitive to such nuances can verify this themselves by launching any FPS game with vertical sync enabled (or simply with a stable match between the game’s frame rate and the screen refresh rate) on any available version of Windows (98 and above), first setting it to 500Hz and assessing the smoothness of the mouse movement in the game, and then lowering this value to 200hz. The difference should be immediately noticeable (provided the user is generally attentive and meticulous about such things). The same thing is observed in DOS\Windows.

When the refresh rate in the game is a multiple of the mouse refresh rate, it’s even less noticeable. For example, at 100hz\200hz, the difference is less noticeable if you don’t make sudden and rapid movements that provoke deviations in the frequency from the base (200hz), which immediately disrupts synchronization and manifests as image jitter. However, when the refresh rate is not a multiple at all - for example, 70hz\125hz, 70hz\100hz, or even 70hz\200hz - this becomes very noticeable: the image literally always trembles a little, compared to 70hz\500hz on Windows, where the image moves truly smoothly (realistically) with the mouse.

A higher frequency, such as 500hz, fully compensates for any polling frequency drops, even during very fast and sharp movements. Frequency drops no longer affect the smoothness to the extent that it can be noticed. Therefore, the movements look realistic. At least, that’s roughly how I understand the observed difference in mouse behavior between DOS (200hz) and Windows (500hz).

Yes, the frequency under DOS can be adjusted using a mouse driver (TSR), but only for PS/2 connections (Not USB). For USB connections, I haven’t found any fully functional mouse driver yet that supports any change in the polling frequency for USB (Always 125hz, with any driver).

And yes, you’re right that 200hz is better than 100hz (the default for PS/2). Furthermore, 125hz (with a USB connection) is relatively suitable for games that run at 60hz(60fps), provided you don’t make sudden and fast movements. But still, it’s not the same and not as good as on Windows (500hz).

As for Quake I, it uses 72fps by default and vertical synchronization is enabled (if Write Combining works). Therefore, neither 100hz, nor 125hz, nor even 200hz in any way correlate with this value (200\72»2,777777). 500hz is almost perfect. But in DOS, unfortunately, so far 500hz cannot be configured in any way. Windows only).

Reply 3 of 3, by pavunoDev

User metadata
Rank Newbie
Rank
Newbie

What are the games that concern you the most? I'm guessing some hacking of the game, if the code is available, could get it to sync better with 100Hz or 200Hz, which would be a massive improvement.