SunDevilPilot

If you mouse cursor isn’t there..... follow this sequence Open the WMR portal. Open the SteamVR Portal Open DCS Once DCS is at the main menu push the Windows Button on your keyboard... The blue WMR Menu Screen will pop up in your VR headset on top of DCS... Then, just push the Windows Button on the keyboard again to make the WMR menu disappear. Your mouse cursor will now be on DCS and work properly.

My volume resides in the low 30s. Not volume related for me. After the standard two blackout issue it won’t happen again for the remainder of the session, no change in volume. The blackouts are random though... don’t always occur. And.. only in DCS.

Well... my latest experiment... Checked and turned off the screensaver. Not sure why that was even turned off. I never saw it active on the main screen. I noticed I’d get the black screen when I was just sitting there (like INS Alignment or flying to a location but not using the keyboard or mouse). Screen would go black... about 5 seconds later it would come back on... few seconds later back to black.., few more seconds back on and would never happen again for that session. Last flight zero issues with black screen.... time will tell. * Update - Still get the occasional black screen / followed by sparkles resolved by reopening WMR Portal.

Even with my purposeful WMR / SteamVR opening sequence I’m still getting the black screen issue. Strangely, I only get two.. separated by about 5 - 10 seconds. Then it will never do it again for the session. Some type of software issue may be at play. Who knows???? I really enjoy my G2 but if a better quality / less quirky headset, such as an Index with high resolution, comes out I would upgrade. At least mine is usable. I feel bad for you Alpine, being totally out of service. Speaking of usb issues. Have you tried plugging in everything with exception of the power plug at the little power brick. I had a supplemental card inside my box that specified this sequence, with power being the last thing to plug in. SunDevilPilot

Anything is possible but on my system.... after a blackout and the resulting snow / lines. If I reboot the WMR Portal the headset returns to normal, with no snow / lines. No change to cable. My cable is secure at the back under a soft Velcro on cloth counterweight. Zero damage to my cable.

Try playing with the MSAA Mask size in the VR section. Solved a cockpit flood light issue I was having in VR causing a similar flicker.

Make that three multiplayer missions with no blackout. Not sure why my new boot method solved the black screen issue but it sure seems to have fixed it. Alpine, you get your headset back up and running?

No errors after a black screen event but there are tiny static like pixels all over, and little horizontal randomly appearing lines... not too visible in a daytime scene but very visible in a nighttime setting. Headset keeps on going just annoying to have the static... a reset of WMR and SteamVR eliminates the issue until the next black screen event. I just had a black screen free several hour session in DCS. I’ll have to try it again but I booted up my computer, intentionally closed the WMR Portal.... Then manually reopened the WMR Portal... waited about 10 seconds.... manually opened the SteamVR Portal... waited about 10 seconds... then opened DCS. I’ll try it again over the next few sessions and report back if it resolved the issue. My thinking was giving each bit of software time to load and stabilize before opening up another piece of the pie. *** Update... make that two complete multiplayer sessions with no black screen issues. I think I may be onto something.

I have the latest and greatest PC (Asus Maximus Hero MB, 10900K and an EVGA 3090) and I get the very same problems as you initially described. I’m not buying the excuse it’s your system. Change in MHz did nothing... Tried switching my main monitor to HDMI leaving the headset as the only DisplayPort output... no difference.

My 3090 powered system with an HP Reverb G2 has exactly the same issue as yours, random blackouts followed by sparkles and lines (visible in dark areas). I’m trying a few experiments in an effort to resolve the problem. My latest experiment is to change the main monitor from 144Hz to a lower setting, while leaving the headset at 90Hz. I’m no engineer but maybe saving some graphical power for the 90Hz on the headset. Last DCS session had no problems with this setting. Time will tell... will report back later.

Try changing the MSAA Mask size in the VR tab. I changed mine from 40 to 60 and the flashing went away. My flashing was just like yours. It seemed to be tied to MSAA and some of the lighting effects. I have MSAA on 2X and with the change in mask size all seems ok. The cockpit flood light in the A10CII would really get my setup glitching. HP Reverb G2 and 3090.

I changed the MSAA Mask size and that, at least for the last flight, got rid of the issue. I went from MSAA Mask size 40 to MSAA mask size 60 in the VR Options.

Spoke too soon, problem still persists. Seems to be the right eye only.. Will work on a track file

Strangely.... I had shadows turned off and moved them to high and it solved the issue... I also had the DCS MSAA and Steam VR Advanced Super Sampling turned on at the same time so I changed that after fixing the issues with the shadows setting. Sorta strange but at least there was a fix. Thanks for the help guys. Only issue with just the instrument lighting is you can see what the switches are for, just not the actual switch position. Sorta need some degree of flood lighting to get the whole picture.

Happens with a few models but really bad in the A10CII. Flying at night with the cockpit flood light turned on makes a huge amount of large black square / overlay flicker. Turning down the flood lights until they are completely off solves the issue, but leaves you sitting in the dark. I fly in VR using an HP G2 but the flicker can be seen on the monitor also. 3090 graphics card.

I am having a similar issue. Generally occurs with the F16 fully loaded with max number of CBU bombs. I can pickle the first set of bombs, say a single pulse pair. Subsequent drops will get hung up and will fail to release. Seems to happen only with the 3 quantity stations and not when the jet is configured with the 2 station hard points.