I had my Reverb G2 display go black for a few seconds, then recover when I was seeing how far I could push OpenXR Toolkit’s upscaling in Elite Dangerous. Got blackouts at Size 115%, backed off to 100% and no problems.
This problem is not unique to MSFS as I mentioned above. My friend with a G2 also sees it while in IL2 Great Battles. He thinks it may be the cable or its connection into the HMD since it has more than once blacked out while moving the head mount.
Just to confirm. You were using the OpenXR Toolkit´s override resolution? What was the display resolution per eye you had when the Reverb G2 went black, and what is the resolution you have now that solved the problem?
Yes, OpenXR Toolkit, Performance page, Size setting 100% (3156 x 3084) no problems. When I tried 115% I experienced the blackouts.
I think the lesson is the Reverb will momentarily go black if it can’t keep up with VR settings that are too demanding.
At this point it is off-topic but just wanted to state that I had a chance to test but was unable to reproduce the issue. After darkening the room, the G2 actually continued tracking left and right head motions somehow – not so well leaning forward and back. No instances of going black so I stand corrected!
Today I removed the G2 to check the monitor. The image was there but it was frozen. So the G2 goes black as it did not receive an image.
I’ve been getting blackouts for the past year! Getting worse with every update (MSFS, Nvidia, Windows etc…). It’s like a giant microstutter. I count each black flash at about 2-3 seconds, usually in high density areas. And the worst blackouts lately comes with CTD’s. I also notice yesterday that the taxiway lines and runway lines are blurry about 20 meters out, this is new.
Now with HP announcing they’re discontinuing Reverb and VR support and Microsoft laying off VR Department, didn’t expect a devolution in VR.
Very disappointing.
(i9-12900, 3080, G2, W11, new cable, blah blah blah…)
I just started getting these in the past month. I have a version 2 cable and the headset is only 2 months old. I’ll see if I upped any settings in the OpenXR toolkit that may be contributing.
One thing I did notice is that it’ll go black during the loading screen (flight, not sim) and when I had the FPS counter in the toolkit, it would recover with low frames (less than 10) and had a red “CPU limited. . .” something for a split second the all would be fine. I’m in a bright room.
Running Win10, everything updated
RTX 3090 with 528.24s
i9-9900k
32GB or RAM
Few month old 1000W PSU
I did read something somewhere that I can’t find that the GeForce experience overlay can cause problems, but I haven’t tried shutting it off.
Oh, and in my windows reliability report I do get occaisional “spatial data service” stopped working or “MixedRealityPortal.exe” stopped working.
I’ll keep checking things. . .
Oh, one other thing I read and noticed: each of the new Nvidia drivers I’ve used keeps turning DX12 on by default. I’ll try with DX11 since that seemed to give me the fewest problems.
Short test: FBW A320 at KCYS. Cold and dark. Flight out to JESAR then MILKY the CYS then visual touch 'n go to 27. Left traffic, landed 27. Only had a “blackout” during the initial loading. So maybe 30 minutes without? DX11 seemed to help. I’ll try a longer flight in the next day or two and see if that’s what the culprit was.
After messing around I can tell you that, in my case, after stopping running FSRealistic in the background the blackout stopped. I’ve already done two flights to confirm that.
This is not true, check some other post on this forums explaining who actually was laid off.
Ok, that’s good thanks! But if HP is getting out of VR, then there’d be no mid-range replacement for the Reverb G2?
Last night I noticed my G2 had a vertical line dividing the right eyepiece into two scenes offset by just a micro-millimeter. Today it’s gone, bizarre behaviour. Terrified that it’ll break and no more support. Called HP this morning and a recording said they were not taking any calls, was disconnected. This is new.
This morning I lowered OXT Dev Tool to 80%, 100 res, TLod 100, OLod 100, everything else is around med-high and notice no stutters at all flying in NW USA/Canada. I’ll try NYC or Toronto as a true test in heavy scenery.
This happened to me too. I shut down and restarted WMR and it went away. It only happened once for me though.
1 Like
The rumours that HP is going to abandon VR business, also say that Reverb G2 will be supported till 2026. They also say that HP has a lot of units produced so there is a chance for bargain price for a potential buyers.
Don’t be too upset regarding HP decision to pull out of VR. Make no bones about it, VR is here to stay. I believe MSFS also realizes it’s potential. It is used by the Military, and the medical world just to name some current users. What we will see, is some major changes that are on the horizon that will bring VR into a whole new concept. Just watch this space.
1 Like
CTD CTD CTD!!
I’m also getting plenty of CTD’s, which is new for me. Settings intentionally turned way down yet getting lots of ctd’s after about 20 min. Seems more often since recent updates. Something major changed. I’m so frustrated with 2.5 years of this games instability. Takes time to set up and plan a flight, then at random it just simply crashes. I’m losing my interest with MSFS (once bitten…) and don’t want to bother with this foolishness anymore. I’ve got other things to do with my life lol!
1 Like
I’ve been flying unintetrupted for hours with a Quest2 - maybe it’s just WMR
1 Like
I’ve been flying uninterrupted for hours with Reverb G2. The only case when I experienced some CTD was related to too aggressive GPU overclocking I applied.
1 Like
Blackscreens are something i have experienced from start, it’s nothing new.
CTD because of blackscreen is possible.
I only experience the G2 going black while loading the flight and “maybe” rar at the very beginning being in the cockpit after loading in there. If it happens later there are more possibillities:
-too high graphics settings
-too high USB-2.0-audio volume
-bad USB port (it’s true, not all USB ports did work flawless for me!)
-motherboard bios old (x570 motherboards)
-enabled power savings or sleep (usb, G2 setting, etc)
-Garmin G1000nxi from marketplace installed (triggered ctd on my system)
I have nearly 1000 add-ons installed and all runs well, my ddr4 ram runs @3800mhz
2 Likes
You can try these in a windows powershell:
Dism.exe /online /Cleanup-Image /checkhealth
Dism.exe /online /Cleanup-Image /scanhealth
Dism.exe /online /Cleanup-Image /Restorehealth
sfc /scannow
Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
Dism.exe /Online /Cleanup-Image /StartComponentCleanup
RESTART your computer as the last step. Then go for a test flight.
Forgot where i read it in the forums, but it has been a life saver. Constant updates do create breaks that mess things up and need to be repaired on occasion.
3 Likes
Please check out this post. It solved my black screen issues. Hope it helps you!
2 Likes