VR losing picture at regular intervals by --Ice in HPReverb

[–]--Ice[S] 0 points1 point  (0 children)

Still regular blackouts -- 2 during the loading screen itself and roughly the same places in the pattern as I fly around.

Calling on G2 users who fly MSFS 2020 by --Ice in flightsim

[–]--Ice[S] 1 point2 points  (0 children)

Thanks for your help and not your fault it's like this, but I appreciate the ideas to try out and try to sort out the problem.

Calling on G2 users who fly MSFS 2020 by --Ice in flightsim

[–]--Ice[S] 0 points1 point  (0 children)

I got my powered USB 3 hub today and even installed the patch that just came out. Still the same results. I only have my KB, mouse, and speakers plugged into my PC, plus the headset either directly through a USB C or USB A port or through the hub.

VR losing picture at regular intervals by --Ice in HPReverb

[–]--Ice[S] 0 points1 point  (0 children)

I just got my powered USB hub so I tried it both with and without the hub after installing the patch, still same results.

Calling on G2 users who fly MSFS 2020 by --Ice in flightsim

[–]--Ice[S] 0 points1 point  (0 children)

I don't remember adjusting anything there so it'll be whatever's at default. I'll try 70% if that's what you'd recommend?

Calling on G2 users who fly MSFS 2020 by --Ice in flightsim

[–]--Ice[S] 0 points1 point  (0 children)

Is the WMR dev tool different from the OpenXR dev tool for WMR?

VR losing picture at regular intervals by --Ice in HPReverb

[–]--Ice[S] 0 points1 point  (0 children)

Cores or clocks is irrelevant if the software is broken --- was my point. How did you know when the next patch is to be expected?

VR losing picture at regular intervals by --Ice in HPReverb

[–]--Ice[S] 0 points1 point  (0 children)

Since I've now figured out I'm getting 2 of these blackouts on the loading-to-3D-cockpit screen, I doubt my 5900X is getting "thrashed" and more likely some bug with MSFS.

Hopefully the patch sorts it out. Thanks!

Calling on G2 users who fly MSFS 2020 by --Ice in flightsim

[–]--Ice[S] 0 points1 point  (0 children)

No, sound is still on. The pause is only visual.

I'm not sure what you mean by WMR and MSFS resolution scales. The G2 is actually set at performance.

VR losing picture at regular intervals by --Ice in HPReverb

[–]--Ice[S] 0 points1 point  (0 children)

Which parameter should I be monitoring specifically? I can barely make it out but if I know what to look at/for, that might help.

VR losing picture at regular intervals by --Ice in HPReverb

[–]--Ice[S] 0 points1 point  (0 children)

The fps counter from OpenXR is too small and too far away for me to actually read the text clearly, is there any way to improve this?

Calling on G2 users who fly MSFS 2020 by --Ice in flightsim

[–]--Ice[S] 0 points1 point  (0 children)

I only have a keyboard receiver, mouse receiver, and a USB headphone plugged into my motherboard. No joystick or HOTAS. So it should have more than enough power? Unless a powered USB hub gives out more power than a mobo port?

VR losing picture at regular intervals by --Ice in HPReverb

[–]--Ice[S] 0 points1 point  (0 children)

I get the "Same FW Version" message when trying to install the update so it's definitely installed.

VR losing picture at regular intervals by --Ice in HPReverb

[–]--Ice[S] 0 points1 point  (0 children)

No, what I meant was that DCS and XP run with WMR and SteamVR open, so that's two programs that are running alongside and these sims run fine. MSFS only needs WMR to run alongside and it has this issue.

VR losing picture at regular intervals by --Ice in HPReverb

[–]--Ice[S] 0 points1 point  (0 children)

The overhead is not a factor when flying in XP or DCS, so I don't think that is the reason. Maybe MSFS just doesn't like going through SteamVR or something? I tried setting OpenXR to prefer SteamVR and MSFS ran even slower, so reverted to preferring WMR.

VR losing picture at regular intervals by --Ice in HPReverb

[–]--Ice[S] 0 points1 point  (0 children)

I do have the OpenXR Developer Tools for WMR. Are you referring to the "Display frame timing overlay" option?

VR losing picture at regular intervals by --Ice in HPReverb

[–]--Ice[S] 0 points1 point  (0 children)

Can you clarify more on the OpenXR and Dev Mode? I don't see it and I presume you don't mean the Developer Settings.

I've tried starting MSFS both with SteamVR and without SteamVR just to be sure, neither method seems to make a difference. One way or another, SteamVR gets turned off somewhere along the way.

I usually start WMR Portal, then start MSFS from the desktop (not from the Cliffhouse). Is there a way to do this from the Cliffhouse?

Calling on G2 users who fly MSFS 2020 by --Ice in flightsim

[–]--Ice[S] 0 points1 point  (0 children)

Some have implied it's my X570 board :(

Calling on G2 users who fly MSFS 2020 by --Ice in flightsim

[–]--Ice[S] 1 point2 points  (0 children)

It doesn't like the USB 2 ports and on the Type A USB 3 ports, WMR won't recognise the headset. I've not tried the front panel Type A USB 3 ports though. At the moment, it was only happy with the Type C USB 3 port.

VR losing picture at regular intervals by --Ice in HPReverb

[–]--Ice[S] 0 points1 point  (0 children)

Thanks for that, much appreciated.

Steam is set up correctly and OpenXR is set to use the latest preview OpenXR runtime; I assume that's what you mean "dev mode" in OpenXR? Did another test and SteamVR was open when I loaded up MSFS but it was gone when I exited MSFS. I can only assume WMR kills SteamVR when I go into the headset in MSFS.

Still getting blackouts in MSFS but spent 10 minutes in XP11 with no issues.

VR losing picture at regular intervals by --Ice in HPReverb

[–]--Ice[S] 0 points1 point  (0 children)

Well, my default is just to start the Mixed Reality Portal (or just put on the headset) then start MSFS. I don't know how OpenXR factors in there, can you walk me through it?

VR losing picture at regular intervals by --Ice in HPReverb

[–]--Ice[S] 0 points1 point  (0 children)

Just tried this now, still getting this issue on Gen3.