Clicking "off game" and switching out of view
WillzZz
Join Date: 2013-01-31 Member: 182667Members
Join Date: 2013-01-31 Member: 182667Members
Not necessarily an NS2 problem.. but I don't remember it happening in other games (I don't play many games).
Does anyone know why this happens? It'll shoot me out of game and decide I have right clicked on my desktop (or whatever). Is it some magic key combo I don't know about? It happened twice in a row just now, but it's very rare otherwise. Maybe once a day or less. When I try to make it happen on purpose it never happens. I use default binds.
Does anyone know why this happens? It'll shoot me out of game and decide I have right clicked on my desktop (or whatever). Is it some magic key combo I don't know about? It happened twice in a row just now, but it's very rare otherwise. Maybe once a day or less. When I try to make it happen on purpose it never happens. I use default binds.
Comments
The windows flag key + P shortcut (WIN+P) is also very nice for quickly enabling/disabling a 2nd monitor.
Update: Just played a game on summit. Problem didn't happen once for 3 rounds. Looks like multiple monitors was indeed the cause of my issue, well spotted Frothybeverage
I shall search this message board for solutions. I can safely say NS2 is the only game I have causing a display driver crash though. Minecraft without a frame limiter doesn't cause this, though NS2 capped at 61 FPS (using 'maxfps', no V-sync) does.
This issue did occur twice without a 2nd monitor enabled. It could be caused by another application (Skype?) trying to steal focus when someone signs in. (random thought)
A new issue has arisen where NS2 will completely halt my computer (alt+tab / win-key doesn't respond too), but I'm not sure if it's related. Only had it twice since build 240. Only recovery option is a hard power reset upsetting my RAID controller -- it then takes about an hour to boot as it's doing a RAID verification at the same time
Always had ATI cards though, don't know if this is related.
VGA/DVI and DVI/HDMI and even VGA/DVI/HDMI setups.
Interestingly I've noticed a bunch of failed WinVNC connections in my event log. (trying to use protocol 3.3 or 3.4 when RealVNC only allows protocol 4+) These could be related as there are also events from Desktop Window Manager:
"A request to disable the Desktop Window Manager was made by process (4)"
"The Desktop Window Manager was unable to start because composition was disabled by a running application" <- NS2 being the application in question perhaps?
Looks like I may need to disable VNC server while playing NS2. Still odd that no other game I play is effected by this.
Goodluck and let us know.
Thanks
Edit : be doubly sure to disable any and all overlays
I'll keep an eye on the clock when this next happens and be sure to check out the event log.
Lower your windows send and/or mouse DPI and raise your in game sens. Happens in nearly every game I've played until I fixed it. My assumption as to why it happens is that the game attempts to lock your cursor in the game, usually the center, but it doesn't disable it. Every whenever milliseconds it places your mouse in the center of your screen. So if you flick your mouse to the side your 2nd monitor is on andclick before it can replace your cursor, you click off the screen. Note it only happens if you have dual monitors and only on the side of your 2nd monitor.
So the idea is to lower the distance your desktop cursor moves, but maintaining your in game sens.
Typed on my phone, I see some red squiggly lines but I can't be bothered.
TL;DR: lower windows send and/or DPI, while raising your in game sens.
"Display driver nvlddmkm stopped responding and has successfully recovered."
I also had switched off both RDP and VNC services so it won't be those.
I have been using nVidia driver version 314.22 (GTX560Ti), but I'll update to 320.18 and see how that goes.
Be careful with 320 version, people have reported issues with ns2.
goodluck and thanks for updating us on your investigation
What I'll do next time I play is have nVidia Inspector running to log the GPU's sensors. There could be an overheating issue. (though I hope not)
On a more related note this particular thread at the GeForce forums could be exactly the same issue I'm having. There is even multiple mention of Natural Selection 2, and also downgrading to drivers 306.23 can be a temporary workaround.
It would be interesting to see if cards overclocked by manufacturer are the common factor in all of this, and more importantly if increasing the GPU input volts by 0.06 really does fix it. 2nd post on page 2 claims +0.06V fixed this completely. This is a very modest boost so I'll happily try this out and report back, and the fan rarely surpasses 50% at maximum load so there is plenty of room to cool off additional heat.
Today during the intense heat (lol) in the UK I'm trying again as it's currently 31c in this room. Attached screen shots show a graph dip where 2 nVidia driver crashes happened, however I noticed that the GPU volt change in nVidia Inspector doesn't save persistently so that'll be why. Kinda makes the 2 attachments irrelevant... I'll try again now in the high heat at the correct GPU volt.
Edit: Yep, pushing GPU volts back up to 1.087 fixed it again. Also attached a screen shot with CoreTemp, looks like even in a 31c room my computer is not overheating.
Weird that a voltage settings decides your ability to click off screen??