DirectQ , multiple monitors. Wtf???

[Mindf!3ldzX]

I have been more and more getting the screwed up problem of whenever I turn right with the mouse mid-fight,for use with ROCKETJUMPING , my snap aim whenever its involving turning right, its like I took the mouse and LEFT clicked the right monitor/desktop, and took DirectQ out of fullscreen mode..

This just recently started occuring, really bad. I've been increasing mouse sensitivity via console naturally,as always. I can't replicate the FN thing by just "goofing off" on a server, the shit is occuring mid-fight, and today....

matt was like....

Exalt says:NO!
Exalt says :You gave up!

HELL NAW BRAH,I WAS STARING AT THE DAMNED DESKTOP OR W/E WAS LURKING BEHIND IN THE BACKGROUND.It's become violently intolerable,cuz it happens mid-fight. I can nail the enemy 3x and practically be able to SNEEZE on the enemy for the "finishing" but its at that moment I just stop moving,cuz its the equivilant to I had alt-tabbed,or somehow "clicked" off the program running in the front,which is quake.

Holy fn failsauce!!

Two monitors, two desktops. im not running eyefinity, just dual monitors. Main is the one on the left, hence the problem occurs while turning right. I'm wondering if raising windows sensitivity & lowering quake sensitivity can supply a fix....

[Magnus]

[LambentHammerBurst]

I recommend getting UltraMon, with it you can disable the secondary monitor by application. So upon running Quake it will turn off the secondary and when you exit - it will turn it back on.

[Mindf!3ldzX]

Monitor 2 is devoted to entertainment. Disabling it will solve the Quake problem, and then break the functionality needed. I'm probably gonna just try a newer version of directQ and see what happens, the last one broke down dramatically via graphics.

[LambentHammerBurst]

That's why I suggested UltraMon - it will disable it when using Quake and then re-enable it automatically when you exit the game.

[MH]

It's more likely a driver problem as the video startup code is utterly standard (if a little on the messy side).

Another possible option is that the input code isn't clipping mouse movement to the game monitor. This should be handled automatically by Raw Input but I have seen odd cases in the past where it doesn't happen.

[Mindf!3ldzX]

What are some steps that I can take to correct the clipping issue? I'm deeply troubled about your real understanding of whats happening and my lack of grasp of whats happening, besides the mouse is "making it past" the clipping zone.....

[MH]

Try adjusting your maxfps downwards and see if that fixes it. At the very least it will confirm if the theory is sound or not.