Do not Alt+Tab

from Demigod Forums

A friend told me that I should not Alt + Tab out of a game, in lobby, or ever if possible. He told me this a while back and I have been watching very closely when my game crashes to see if there is something that I am doing that can be prevented. I realized when I have Atl + Tab or do some other combination of buttons to get out of DG to the windows screen about 35-50% of the time the game crashes. The number of % is not precise, it seems to be like winning "the game is going to crash lottery." you never know what could happen. Anyone care to enlighting me as to why this could happen other then maybe shoty programming (or so I hear, but what do we know).

Of course not surfing the net while you are waiting for a game can be a real patience builder. Well I hope some find this helpful.

Side note: almost all the time while the game is loading if for some reason if I Tab out or whatever the game will crash, like clock work

1,473 views 7 replies
Reply #1 from Demigod Forums Top

You can alt tab out of any menu in my experience, as long as there is no chance that a game will start while it is minimzied

Reply #2 from Demigod Forums Top

I have to side with calebL_blood here it crashes when u alt+tab about 35-50% of the time and it never used to till like 2 updates ago

WindowBlinds - Free yourself of the default settings, customize your desktop.
Reply #3 from Demigod Forums Top

Most games crash period if you alt tab during a loading screen. It's common sense.

 

Game alt tabs fine during menus for me.

Reply #4 from Demigod Forums Top

crashing almost every alt tab here, regardless of me being in game or in the menus.

Reply #5 from Demigod Forums Top

If I alt + tab during the running game, the only problems I have are the missing "target areas", the abilities no longer show how far they can target, the semitransparent circle around your character.

Reply #7 from Demigod Forums Top

Alt+TAB in DirectX isn't defined by Microsoft's DirectX API (at least not under DX9 and prior - I don't know about DX10).  What this means is that developers and video card and driver manufacturers cannot know in advance how to handle what happens if a user task switches out from full-screen. If a game is running full-screen, and requires some sequence of events to complete once that sequence begins, it (the game, and the developers of the game) can't really know in advance if a user is going to alt tab out in the midst of that critical sequence.  Sometimes, nothing bad happens.  Sometimes something bad happens.  And it varies from system to system, not just game-to-game.  And a developer or video card/driver manufacturer can't always put in code checks to see if alt-tabbing occurs at each little step in code - because you may add too much overhead and result in poor performance that makes the game run horribly.  So they may make trade-offs, between necessary performance for their game, at the expense of risking the game/app not functioning well if/when a user decides to alt-tab out to check email or what-not in the middle of the game.

I tend to be able to Alt-tab out without problems in most games I've played.  In fact, alt-tabbing has fixed some problems (early release versions of Oblivion under 7 series nVidia GPUs would not clear texture memory from GPU cache effectively, and in some cases would start swapping and thrashing between GPU texture memory and system main RAM which is much slower).  Alt-tabbing would be one of several ways to force my particular GPU to drop it's 3d textures in cache, to display the 2d desktop - and then return to a decent level of performance in-game when I switched back.  Sometimes alt-tabbing corrupts textures for pretty much the same reason it fixed the above issue for me.

Running windowed mode doesn't 'fix' the problem, but because video memory isn't swapping between full-screen 3d and 2d desktop when in windowed mode, it sort of side-steps the fact that DirectX API doesn't clearly define how to handle alt-tabbing back and forth out of 3d mode.