Screen going black from time time

[Hadji]

Now and then my screen goes black for a few seconds when flying. It's not a freezing issue - the game runs during the blackout. My buddy has the same problem and it happens with all modules and mostly during multiplayer sessions. Anyone else experience this? It started with DCS 1.2.6 (have been playing since 1.2.3 and never had any issues).

I have monitored my system when it happens and temperatures etc are fine. I have tweaked the game according to recommendations in the offical Eagle forums and FAQ's. I'm beginning to think there is a problem with the game itself since I never have any issues in other resource hungry titles like Arma II/III etc.

My system:
i5 3570K @4,2GHz (cooled with Corsair H100)
16 GB Corsair Vengeance DDR 3 1600 RAM
MSI Nvidia GTX 680 Lightning @1.3GHz (cooled with TwinFrozr)
Corsair Force 3 SSD
Win 7/64
TrackIR 5 + Track Clip Pro (connected to mainboard slot)
Thrustmaster HOTAS Warthog (connected to mainboard slot)
Fibre LAN 100/100 Mbps (connected with CAT-6 cable and no router etc)
Single monitor setup

Installed DCS Modules:
DCS World (latest non Steam version)
DCS A-10C
DCS P-51D
DCS UH-1
DCS Combined Arms
Flaming Cliffs 3

Any help appreciated!

[Surveyor]

You probably meant the screen switching off by Windows during what it thinks is the "inactivity time"? Almost three years later this problem still persists. One of the workarounds it to forbid Windows from doing that.

Developers, can you do something about this issue already? Can be really annoying to either have the screen go black on you just when you are hovering really close to ground installations, or not having the screen switched off while AFK and forgetting about it.

[PotHat]

I think I might also be having this issue, although it seems to happen when I pull many Gs

[PotHat]

I will try and recreate it today

[kazereal]

Originally posted by PotHat:

I think I might also be having this issue, although it seems to happen when I pull many Gs

You are talking about pilot blackout. That means your pilot is passing out.
Also see redout in other direction.

Another thing that is simulated is hypoxia due to low oxygen (high altitude) when cabin is not pressurized.

[kazereal]

So, not a bug: working correctly.

[PotHat]

No, it's a bug because I can't access the main menu when it happens. The whole game blacks out and all I can hear is the sound.

[PotHat]

Blacks out instantly*

[PotHat]

And then it comes back after a bit, usually after I crash and explode.

[PotHat]

For example it happened once in the tutorial for ATG missles when you have to pitch down fast to aim at the truck; it blacked out and it came back after I blew up.

[PotHat]

Originally posted by coxy:

To many high Gs

So it's normal for the menu to be inaccessible when that happens then?

[kazereal]

Originally posted by PotHat:

Originally posted by coxy:

To many high Gs

So it's normal for the menu to be inaccessible when that happens then?

Menu access might be separate thing.

Some things like F10 map can be disabled by mission settings, might be possible to disable menu too to prevent bailout.

[Sandy]

Originally posted by kazereal:

Some things like F10 map can be disabled by mission settings, might be possible to disable menu too to prevent bailout.

Is this some LUA scripting feature or something? To my knowledge, the only editor options regarding the F10 map are the same as in general options. The mission creator can limit what's displayed on the F10 map, the most limiting option is still "map only" meaning you still get the F10 view.

--

Considering OP's problems have existed since 1.2, I'd speculate this might be a GPU+driver+game compatibility issue.

[Troll Norris]

Well, sometimes when the update is released, I have experience with black screen after changing controls binding. I've found that is caused by changes in bindable keys. Last time I had problems in update 1.5.5->1.5.6OB where I had to delete SU-27 and SU-33 input configs from Saved games\DCS\CONFIG\INPUT folder because they added there new funcions which were in conflict with old control setup.

[Surveyor]

I'm still having the problem with the screen going black after the "inactivity time" has passed. Except now hitting a keyboard key brings me to a static screen with the aircraft continuing to fly in the background (the audio is still being played). So, when this happens, I have to Alt+Tab somewhere else, then Alt+Tab back into DCSW. Please do something about this already?

Flying the standalone 2.0 OA.