Help! Does anyone else get black screen on certain lights?

[Hawkeye_UK]

Thanks for helping.

 

Ok so i have a problem that's driving me mad and i cant seem to bottom the problem out. Essentially on certain lights, i believe its the aircraft position lights that cause the whole screen to "black out" outside the cockpit, except for certain details. It started this summer and i really don't know what's happened. I've tried a DCS repair also but to no avail.

 

I've looked at the ndivia control panel settings and tried just about every combination. I run the game with shadows on low, global shadows terrain on default set within the main DCS menu. I run 436.30 however have had this with the last 2 or 3 versions of Nvidia. That said i cannot say the problem suddenly started when i update my Nvidia software.

 

It makes playing the game near enough impossible - Has anyone else had this problem.

 

Lastly i run my Rift S on an EVGA RTX2080 however everything else runs fine so im confident its not a hardware issue.

 

Just put a few screenshots up from today, i've switched on labels so you can see what units are there. It's as i pan my head around i lose vision (black) on one eye then within a few degrees the other eye. Then look where no lighting and everything instantly comes back!! It makes multiplayer impossible as all anyone has to do is fence out or equally forget to fence in and i can't see anything. Also ruins SP play also.

 

If anyone has any ideas - no matter how basic i'm happy to literally start from stage 1 to rectify the problem (i really don't want to have to reinstall the 200Gb DCS folder however if at all possible).

Edited November 13, 2019 by Hawkeye_UK

[BIGNEWY]

Hi Hawkeye_UK

 

remove any unofficial mods and run a cleanup and repair ( guide in my signature below)

 

Then delete your metashader2 and fxo folder in your saved games dcs folder.

 

restart DCS and test.

 

First load will take longer as it creates new shaders

 

let us know if it helps

[Hawkeye_UK]

@Bignewy

 

Really appreciate the quick posting - after further testing i should have referenced this only occurs when the Shadows tab in DCS settings is in either Flat, Low, Medium or High. If i switch this to off then the problem instantly goes away. Note the terrain shadows i have set to default and this does not cause the screen to black out.

 

I also get it around the Harrier carrier its down to lights im confident of this aspect in the fault.

 

Yes i've removed all mods etc in fairness i uses OvGME for this anyway for qucik removal.

 

I regularly remove the FXO and metashaders2 folders in addition to the track files (multiplayer) to save disc space. I have removed them again today however its always down to the shadows Tab, obviously i don't want to lose the functionality of this in terms of immersion.

 

Is there a way to just repair this section of the install if that's the problem?

Edited November 13, 2019 by Hawkeye_UK

[Hawkeye_UK]

@Bignewy

 

Ok so i did the clean up and repair exactly as listed - Now DCS wont even load it just crashes? IN the crash log i get this issue (username blanked out by me)

...

 

# -------------- 20191113-153420 --------------

DCS/2.5.5.39262 (x86_64; Windows NT 10.0.17763)

C:\Program Files\Oculus\Support\oculus-runtime\LibOVRRT64_1.dll

# C0000005 ACCESS_VIOLATION at 86FD444B 00:00000000

SymInit: Symbol-SearchPath: '.', symOptions: 534, UserName: '-----'

OS-Version: 10.0.17763 () 0x300-0x1

0x000000000016444B (LibOVRRT64_1): ConfiguratorUnregisterC + 0x2543B

0x00000000000B0CF5 (LibOVRRT64_1): ovr_Lookup + 0x41905

0x00000000000B1935 (LibOVRRT64_1): ovr_Lookup + 0x42545

0x00000000000A54BD (LibOVRRT64_1): ovr_Lookup + 0x360CD

0x000000000003AB1E (LibOVRRT64_1): ovr_GetFovStencil + 0xC3BE

0x00000000000455FF (Visualizer): MouseCursorOwner::setMouseCursorPosition + 0x395F

0x0000000000076C8D (Visualizer): smCamera_Implement::SetProjBounds + 0x3B7D

0x0000000000084FC6 (Visualizer): smSceneManager::CreateSceneManager + 0x126

0x000000000056C831 (DCS): (function-name not available) + 0x0

0x000000000056995F (DCS): (function-name not available) + 0x0

0x00000000001BB4FB (DCS): (function-name not available) + 0x0

0x000000000072CB76 (DCS): (function-name not available) + 0x0

0x0000000000017974 (KERNEL32): BaseThreadInitThunk + 0x14

0x000000000006A271 (ntdll): RtlUserThreadStart + 0x21

Edited November 13, 2019 by Hawkeye_UK

[BIGNEWY]

Strange don't think I have ever seen that crash.

 

Is Oculus up to date?

 

Can you attach your dcs.log here ( rename it to dcs.txt and you can attach it )

[Hawkeye_UK]

I've bit the bullet and decided to unistall everything and reinstall the full program - hopefully that should resolve it. If not then i'll post the log file on the new build.

 

Yes oculus is fully upto date - strange how after the clean and repair it caused this crash though.

 

Fingers crossed by tomorrow should be back up and running! Thanks for the reply.

[BIGNEWY]

I've bit the bullet and decided to unistall everything and reinstall the full program - hopefully that should resolve it. If not then i'll post the log file on the new build.

 

Yes oculus is fully upto date - strange how after the clean and repair it caused this crash though.

 

Fingers crossed by tomorrow should be back up and running! Thanks for the reply.

 

Understood, going full nuclear is a good option sometimes. :)

 

If you still get the same attach your dcs.log

 

Thank you

[Hawkeye_UK]

Happy to confirm that a full new install did indeed remove the problem - clearly something somehow had got corrupted!

 

Back to enjoying seeing the world in full technicolor ;-)!

[Doon1]

Now is the time to buy a cheap HDD and backup your entire system. I update my system before each major Windows update. It's saved me a couple of times. $50 well spent IMO.

[BIGNEWY]

Happy to confirm that a full new install did indeed remove the problem - clearly something somehow had got corrupted!

 

Back to enjoying seeing the world in full technicolor ;-)!

 

Great to hear :thumbup: