Quest 2 Unsolvable Crashing

So I got my Quest 2 months ago to play pretty much flight sims exclusively. When I got it it worked pretty well albeit I couldn’t figure out much with graphics settings that would make it look decent without becoming unplayable. I played for a while and left it because I was too busy.

In the last three or so days I’ve tried to pick it back up to even worse issues. The first day it worked pretty well, I’d connect using oculus link, some minor bugs but ok graphics and so on.

The last two days have been hell. When I would try with the link, it crashes on the same spot about 90% done loading a flight every time I play. It seems that it crashes in bigger area maybe? When I try to fly out of my local rural airport it seems to work but anything slightly bigger crashes me. I haven’t tested this enough to know if the times it has worked are flukes or not though.

Virtual Desktop seems extremely promising but when I try to play off that, starting the game through the VD interface without steam VR, it won’t “find my headset” when switching to VR. (I’ve tried the whole registry editor thing and it seems like everything is as it should be in my reg). Loading with steam VR pretty much has the same effect but it seems to be less smooth and more of a pain to figure out how to actually get the game to pop up on my quest. Regardless I’m left playing the game in what looks like a movie theater.

Airlink is a total loss, same issues as the first one with oculus link, crashes and the graphics are way worse given my router is far away, I can’t change that.

I’m really at a loss here. Don’t know what else to try, I have watched tons of videos, read forums, can’t find anything that helps me. I’m pretty much at the point of thinking that I can’t play with my quest 2 and might have to get rid of it for something else that will actually work if there is such a thing. If it helps anymore too it seems that pretty much any other game doesn’t recognize my headset. (If there are war thunder players, when I load it up and activate VR mode, it restarts, loads back up and VR mode is still off, doesn’t even try to start it.)

1 Like

So i have a RTX3070 with i9-9900k and 32g of ram. I have my settings as follows and seem to have pretty decent smooth fps/graphics quality. This is just for reference if you want to try to “switch things up”.

I get occasional CTD but seems to be reated when i have MSFS2020 running and tweak something in the Oculus Debut tool and then thg flight sim crashes. Just a heads up on that and happens more with the recent world update.

Provided you have your openx set for oculus and not steamvr or windows mixed reality (can be checked and reset through the Settings/Beta tab open xr runtime).

  1. Use the official Oculis link or super high quality cable with a motherboard USB-C connection ( I never had a great experience with wifi vd or airlink)
  2. Set the Oculus app device settings to 72hz and 1X scaling
  3. Use the Oculus debug tool and set the following (you can try encode rate 0 or adjust pixels override if your specs can’t handle)

ott_suggest

See if this help

1 Like

So when I check the settings / beta tab I don’t even get a section where I can see where openxr is running I can’t even see if it is running to oculus which I have read that it means my headset isn’t even connected or being registered to whatever programs it needs to be. I had a thought that changing my debug options a few days ago might have been the catalyst to all this but I reset all the options and nothing was solved :frowning:

I just cannot seem to find the way of getting into the game that consistently works

Are you running a AMD card or Nvidia?

I have a 1660 Ti

Fyi on my earlier post I failed to mention I have both the VR and PC scaling in the sim at 70.

As for the Oculus app you don’t see the last line?

Ok yes, my confusion. I do have that.

I had that OpenXR registry set up the whole time but I’ve gone in a double checked multiple times to make sure that it is correct. I had the feeling I igual y that that is why VD would give me the “no headset found”.

Ive had a bit of a new finding that if I start the flight sim on my PC, then go into oculus link and enter VR in the menu (I can enter it in the menu it just dies upon loading) then go back into VD I will be in VR mode but I cannot get VD to enable a “full screen” mode so to speak. Like I just get the movie theater effect.

Ive gone into the VD menu and pressed enter VR and it brings me back to the movie theater view. Starting steam VR from the menu has the effect of bring up the “up next…” loading icon showing MSFS loading even though it’s already loaded up, it stays loading too.

I find that if you wan to use VD the set the openxr runtime for steamvr instead of the oculus one.
If you want to use the oculus app and the diag tool you have to set it for the oculus runtime.

For steam open the steamvr app and in the settings somewhere and beta section should be a way to change it back to the steamvr runtime.

For me, VR didn’t work until I connected my PC to my wifi with an ethernet cable. I got a fifty-foot cable and ran it to the other room where I have my router. I was able to get VR working with Airlink but it still crashed occasionally. Also, I found that VD and SteamVR aren’t needed. Once I made a stable connection to my wifi, I removed VD and SteamVR from my system completely and VR still works. I can load the sim, open the Oculus app on my PC, then link the Q2 to the PC.

Thanks, GalacticClown15 because of your post, I connected my Q2 to my PC with the Link cable and it works great. The connection is solid, I flew for 30 minutes without a VR-crash, and the graphics are 100% better. A lot of the shimmering is gone. Once I got things working with Airlink, It didn’t occur to me to try the link cabl.

Yeah, I find you never get the best experience with streaming to the headset via wifi when it comes to MSFS2020.

For other games, perhaps you can get away with it.

Also, always connect your PC to the router/switch via ethernet. You don’t want to be upstreaming from the PC and downstreaming to the VR headset via wifi. Too much bandwidth eaten up.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.