Wondering if anyone is getting CTDs with the Q3 as soon as selecting VR? Nothing I do gets it working. Thanks
I don’t think majority have the headset yet 
Have you tried with link cable anyway?
Don’t have a cable at hand for this… so can’t test. Works for everything else so I think it’s MSFS related… maybe device ID issue or something.
Would you mind letting us know how / why you have the Q3 before the release date? Are you a developer or just flexing? 
should be delivered tomorrow for pre-orders - so may be he just received it because DHL is so fast? Nothing to worry about one day.
I live on a small island, so assume the retailer sent early to account for additional shipping time. Got here in two days, so had it just under a week early
1 Like
in france, the shops have had the q3 for more than 2 weeks, but they only give them out from the 10th.
I won’t be able to collect mine until tomorrow.
Are you using virtual desktop? It’s just been updated for the quest 3.
Yep using the latest version. Hoping its just not me so there will be a solution!
Anyone else experiencing the same issue?
Yup - exact same issue - crashes after entering VR - but not immediately. If I don’t move or do anything it stays up on the msfs splash screen for a bit. I suspect it may be attempting to use too much bandwidth to deliver higher res - going to experiment a bit.
Updated: dropped the resolution to minimum supported in the oculus desktop. Same results. Changed the oculusclient.exe priorities to all run above normal - got a graphics card crash.
Not much in the logs - error on GPUID: 100 pretty much everything else is null - guessing there is a buffer overflow. I’m going to open a ticket with Meta.
All’s working fine with my new, 20 hour old Q3 with msfs using Link (500mbps) and Air Link (200mbps dynamic). This is with my i913900k/rtx4090 PC and my device graphics settings at 80Hz refresh with the res slider full right. All ODT settings at default except distortion Low and mobile asw disabled. I also use OTT game profiles to turn ASW off. Pretty early days, but so far so good, touch wood, lol!
maybe my poor old 2070 isn’t enough? I have the airlink setting dynamic 200 but don’t have a cable.
Coming from a G2, what is the most efficient way to use the Q3 with MSFS? I presume the VR button in the main MSFS menu is only for WMR?
I don’t have a G2 or WMR headset so I can’t say for sure. The VR button is there with my Quest headsets (or just hit ctrl+tab). I always startup msfs in 2d projected on my Rift home virtual desktop (not to be confused with the Virtual Desktop app, which I’m not using right now). Once msfs starts up I switch to VR (hitting space bar to center my view). Then I usually use my PC mouse to navigate through the menus and a HOTAS for flight controls. I don’t use my VR controllers at all and just leave them off to the side. Anyway, if you have managed to live with WMR for a while I’m sure it won’t take you too long to figure this all out.
Update - got and tried with a proper usb-c cable - same result - oculus server app crashes entering VR with an access violation error code (finally found that). Have supplied all logs to meta support. Logs suggest not enough memory (somewhere) have 32GB which is more than enough - suspect something is not honoring the available graphics memory.
Tried lots of troubleshooting. Nothing helps. Looks to me that the issue is buffer overflow on dedicated GPU memory. Crashes when there is just under 1GB left consistently. I suspect that memory is fragmented (does this happen on a GPU?) and the server fails when asking for a contiguous chuck that is too large. Whether that much is actually needed idk; error handling is poor it would seem. Also - for performance why not grab and reuse what is needed up front?
What is your VR runtime?
If you don’t know. Try with GitHub - WaGi-Coding/OpenXR-Runtime-Switcher: OpenXR Runtime-Switcher for Windows
I just remember that I had a similar issue… violation error. I was able to manage it. As I did so many things in the last days (going through SteamVR, going trough VD, cable via Oculus etc.) I had a lot of problems and errors and problems and do not remember well 
Maybe we can go through step - by - step?
Might be a daft question but are you enabling VR in the main menu or once loaded into a flight?
I’ve had several CTD’s from the main menu but loading a flight and then ctrl+tab while sitting on the runway consistently works. You can then go back to main menu etc with no issues.
Okay - so applied the 10/17 nvidia update as well as the latest windows insider canary. Nothing obvious in release notes, but the problem has now vanished. I can successfully run MSFS 2020 with airlink or a cable in an RTX 2070 - including with the oculus resolution full right. still playing with settings - DX12 is not great. Overall so far this is a significant improvement over the Q2. Can see VASI now at a distance and actually read instruments. WIll update anything further in the performance thread.
1 Like