So yesterday’s oculus update broke OpenXR Toolkit. And with development of the toolkit stopped, it appears there will be no fix. 
2 Likes
I’ve got a Quest 2 and my OpenXR Toolkit seems to be working fine. It was all working for me last night and I’ve just tried it now with no problems at all. I’m on Windows 11.
I left the oculus beta and went back to the previous version (67) to be able to use my quest 3 again.
It works again.
1 Like
I’m on beta version of Oculus. Probably should have specified that on my original post
1 Like
I’m having a CTD just starting MSFS (not in VR mode) with OpenXR Toolkit enabled ever since this week’s MSFS update. Too bad because I really appreciated the toolkit - especially for the FPS printouts.
EDIT: Having OXRTK enabled at startup causes a CTD for me but I can enable it during actual VR operation
1 Like
I used to be on the Beta version of Oculus but had a problem a while back of it not connecting using Link Cable so left the Beta.
Strange one that. Not too sure about that one. Just hope that no other updates break OpenXR Toolkit as I can’t live without it as it’s such a useful tool!
I’m getting both an openxr_loader.dll and a VCRUNTIME140.dll errors when MSFS crashes just before getting to the menu. MSFS Crashes started yesterday (Monday). I updated oculus before I ran MSFS. I had no issues with MSFS on Sunday.
My Oculus CV1 (Yes… I’m that far back) by itself is working fine after the oculus update. I’m think I’m in the oculus beta.
1 Like
Yeah, revert back to stable and it should work. Hopefully they might revert the change that breaks it in beta version.
1 Like
You are the man!!! Going OFF the oculus beta resolved the problem!
That makes me more than a little scared to think about
1 Like
Thanks for this thread, I was going nuts with the CTD and did everything (updating my system, taking out all Community items and side apps). But all the CTDs did happen after the Meta update. Can’t even launch DCS in VR either.
I just clicked the Disable OpenXR Toolkit in it’s options and MSFS started up. I had forgotten I’m in the Meta Beta. So now, go without OpenXR toolkit or leave the Beta? The Beta could become the normal in a week and I’d be right back here. Ugh, VR so good and so bad at times
1 Like
Per @Krazsus initially pointing out that OpenXR Toolkit is discontinued and I see this on its site:
" AS OF 2024, SUPPORT FOR OPENXR TOOLKIT IS DISCONTINUED. THERE IS NO NEW DEVELOPMENT AND NO TECH SUPPORT OF ANY SORT. THE DEVELOPER DOES NOT RECOMMEND TO INSTALL/USE OPENXR TOOLKIT, AS IT IS KNOWN TO CAUSE ISSUES WITH MANY OF THE NEWER GAMES RELEASED IN SINCE 2024."
I’m leaning towards uninstalling it 
I’ve not had the best experience with Meta updates from Beta to Live.
1 Like
I’ve disabled my OpenXR Toolkit for now. Just to see if I can get a smooth experience in VR and so far I have good results. Only things I really miss are the sunglasses and brightness, contrast and colour adjustments as well as the FPS display but I figure that if OpenXR Toolkit is discontinued then I’m going to avoid potential problems in the future. I just wish that Asobo would implement a way in which we could adjust the above-mentioned things in the future.
1 Like
I think I would miss being able to set the sim render scaling to 100% to help with the sharpness of the displays. It’s been a while since I’ve run w/o the OpenXR Toolkit but I recall that I had to adjust the sim render scale much lower to get performance.
From the OpenXR Toolkit site…
" Many of the features of OpenXR Toolkit took less than a week for their initial implementation and have proven their value. THERE ARE NO EXCUSES FOR GAME DEVELOPERS TO NOT SPEND TIME ON DEVELOPING THESE FEATURES. "
I agree that I hope Asobo will implement more of this stuff natively.
4 Likes
Virtual desktop user but on some point I have to give up the toolkit too I think. I will miss the FOV setting, 85% was a big increase in clarity.
1 Like
As the same developer is now working on VD, I was hoping to see that feature (and others) come to VD. But in the latest update, still nothing like that!
Very sad news. I used OpenXR Toolkit for “Turbo mode” only. Thanks to this feature enabled I had no stutters during turns (eg. during taxi), etc. and flying in VR (Q3, cable) was much more smooth. I hope to find an alternative to this feature.
1 Like
I have a branch of VDXR with most of OpenXR Toolkit features included (except for post-processing). This is the proper way things should be done since game devs don’t care to do it themselves (doing inside the runtime, as opposed to an API layer like OpenXR Toolkit today, which creates many issues). The problem is I currently have no option for user configuration.
Lots of users complained about OpenXR Toolkit user experiences (the in-game menu). I unfortunately do not have a solution to this. So right now the integration to Virtual Desktop is blocked. I have very little time (and interest) for User Experience work. Unless I can find a developer to work on the User Experience, this path is likely doomed.
2 Likes
Thanks for the reply 
I’m more than happy with F2 menu lol
Maybe include it as an “experimental” option, off by default?
I do have some experience with UX design but I am not a coder. I’d be happy to design a set of screens for it though if that is helpful at all?
Thanks, design isn’t the concern, it is 100% the implementation that is.
2 Likes