"Quake 2 engine" mouse issues

[Hipshot]

I didn't know where to place this, so I'm just gonna try here.

So, I have this strange mouse issue, that sometimes the mouse can just go haywire, like turn really really fast when I don't want it to, in a split second I'm kinda looking down in the floor or turn or something. Like it overreacts, it's very very annoying and what happens is that I can't trust the mouse in a MP game. It doesn't matter whatever mouse sensitivity I use, or if the game have any other settings, it's not an FPS issue either, since both games are running a "low" rates, like 100 or so.

This happens in Soldier of Fortune 1 and in Daikatana, I never experienced this playing on my xp install a few years back, I don't even know what to search for to see if someone else have this issue and/or how they might have solved it.

I have yet to play actual Quake 2 and also Kingpin to see what happens in those games.

I'm running a windows 7 64 using a logitech G400, it's black.


edit: Like this I guess https://steamcommunity.com/app/38430/di ... 741384473/

[Hipshot]

Happens in Kingpin too, damn this is annoying.

[MKJ]

I had the same problem with the Serious Sam games on one of my machines way back when. The only thing that seemed to at least minimize the frequency of the problem was using a different surface to mouse on.

You'd think it'd be an OS wide problem and not just some applications.

[Hipshot]

I have thought about switching back to an older mouse, It's just so damn annoying having to do that while playing just these games. The G400 is just so much lighter than the MX518 or whatever it was called, it feels better =)

Can you have to mice connected at the same time?

[Bacon]

I had a similar issue with my mouse and had to turn the polling rate down from 1000 hz to 125 hz

[obsidian]

Turn off acceleration?

[MKJ]

I know that never fixed it for me as I always have acceleration disabled.

[Captain]

I had a similar issue with my mouse and had to turn the polling rate down from 1000 hz to 125 hz

That sounds like it might've been a CPU latency issue.

[SoM]

m_filter 1

?