Hello guys
May be someone can help, since the last update I am having constant CTDs, and it’s impossible to pass 2-5 minutes on the simulator, the error always refers to LibOVRRT64_1.dll and to Oculus Application on MSFS, here is the log from evet viewer:
Fault bucket 1657904401599254166, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0
Problem signature:
P1: Microsoft.FlightSimulator_1.32.7.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.32.7.0
P4: 00000000
P5: LibOVRRT64_1.dll
P6: 53.0.105.132
P7: 43fba069
P8: c0000005
P9: 00000000000feb22
P10:
I already tried 3 different driver versions, I am having CTDs with all of them, so I believe the driver is not the problem, I am using DX11 only.
I use the simulator only with Oculus Quest 2 VR.
Does anyone knows if there is an available solution to this problem?
Hello!
Your topic has been moved into the Community Support category.
The Bug Reporting category is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug topic. Using the template is required in order to provide valuable information, feedback, and replication steps to our test team.
If you are not sure if your issue is a bug or need further input from the community, please use the Community Support category. If the community can replicate your issue, first search the Bug Reporting category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.
If you believe it is a new report, then create a new bug topic using the provided topic template.
NOTE: All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.
As you’ve already mentioned, this appears Oculus related. One thing to check would be can you launch the sim without any VR hardware connected, or software loaded? This would be a test of overall simulator health, as we need to establish whether this is a sim issue or a third party software/driver issue.
If the sim works without it, then its the unfortunate dance of finding the right combination of driver/software that will play nice with MSFS.
Hi hobanagerik
I don’t believe there are many Oculus drivers, I only open the Oculus APP on the PC, Oculus Debug Tool and then open MSFS, I tried again 5 minutes ago, same crash error:
Faulting application name: FlightSimulator.exe, version: 1.32.7.0, time stamp: 0x00000000
Faulting module name: LibOVRRT64_1.dll, version: 51.0.168.269, time stamp: 0xc14cac7e
Exception code: 0xc0000005
Fault offset: 0x00000000000fac92
Faulting process id: 0x0x3408
Faulting application start time: 0x0x1D97E0E99AF9940
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.32.7.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\Oculus\Support\oculus-runtime\LibOVRRT64_1.dll
Report Id: a1dbc874-145b-4207-b1ca-3d0986435830
Faulting package full name: Microsoft.FlightSimulator_1.32.7.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
I know the sim can run without the headset connected, but that doesn’t help, because the Oculus is working perfect with other games, this is an issue that started to happen to me with the last update, so it should be the simulator.
I will try to remove/uninstall everything else and start the simulator again, however, it is sad to have to do this EVERY TIME there is an update on the sim.
It was just a diagnostic step. So if you are sure the sim runs normally without it, then as you say it has to be the Oculus driver causing it for some reason.
It might be worth checking on the Oculus support forums to see if anyone else is experiencing this.
Thank you hobanagerik, I am re-installing the whole Oculus app to see if that fixes it, I will try to play a bit without VR as you suggest just to rule out problems regarding the simulator installation.
If it doesn’t work with a new Oculus installation I am lost, and the next step is to reinstall the whole Windows, which I don’t want at all.
Also the error is weird, I googled it and didn’t find anything 
1 Like
I doubt a Windows re-install will help. Your error is very specific, and certainly appears driver related.
I had a quick look at the Oculus support site, expecting to see a page where it would show various versions of the driver, but it had a single download.
If those do exist somewhere, it might be on a third party Oculus community site.
1 Like
After testing and testing, reinstalling and testing again, I found that, in Oculus Debug Tool, if I touch the Pixel Override and the Tangent Multiplier values , and after some minutes of playing, I got the CTD.
I left those as it is on the image and was able to perform a full 1.30 hr flight without CTDs, may be it is the problem, or may be it is something else, I am not sure, but I made several flight test and for now…that seems to be the problem.
Before the update I was using the ODT with those values on 1.4 and 0.8, 0.8, but now I am not able to change them to those values anymore without causing a CTD.
Just want it to let anyone knows in case you have the same issue as me, I will continue testing this to see if I have any other CTD.
