Thanks @mbucchia and the rest of the people who got involved in fixing this issue.
Unfortunately I wasn’t available during the weekend to assist with any help.
You guys rock!
Thank you.
Guess what,
I just kept OpenXR Toolkit (OpenXR 150%, my Toolkit MSFS settings are FSR 80%, 80%, 9900K, 6800XT) on when with my HP Reverb 2 I ran
DIRT RALLY 2.0, which is a SteamVR game, with the Windows Mixed Reality runtime active, not the SteamVR driver.
No OpenXR Toolkit menu to popup, but Dirt Rally 2.0, my favorite car game ran absolutely & extremely Smooth, and guess what, this improved my rally times with quite the decent margin (as in 20 seconds on a 5 minutes track).
The Toolkit menu would be nice then one could know what exactly is going on here, is there another way to see what the Toolkit is set at?
How about them apples.
Unless you are using OpenComposite-ACC to use DR2 with OpenXR, then DR2 is definitely not using OpenXR and you’ve been dreaming 
If running with the original openvr_api.dll then you are not using OpenXR.
In your case, it is not running OpenXR. Having the OpenXR Tools window open makes absolutely no difference btw. This window is just telling you that if your application is using OpenXR, then it will use the WMR OpenXR.
Similar thinking:
- You can have DirectX installed, but if you run an application that only supports OpenGL… well sure DirectX is installed but that doesn’t mean it’s being used.
- I can put some really awesome speakers in my car, but if I don’t wire them to my stereo system, they’re not being used.
I’m pretty sure people are having success with OCXR_WMR_ACC and DR2, you just need a config file change if I recall. This is being discussed on our Discord, in #open-composite-acc.
1 Like
I mean the OpenXR Developer Tools windows is open, stating the WIndows Mixed Reality Runtime that drives the Reverb is set to windows and not to SteamVR OpenXR, and shows your API running and reasonably DIRT VR is running this Windows OpenXR and not the Steam OpenXR
I’ll chk Discord
Please re-read my message so you can understand why this statement is 1000% incorrect.
Hopefully this helps:
The only thing that OpenXR Tools window is telling you is which OpenXR runtime you are using (that choice right of “OpenXR Loader”), but if your app is not using OpenXR in the first place, then none of this matters. Dirt Rally is using OpenVR, which goes to SteamVR no matter what and ends up back to WMR, but nothing of OpenXR is involved.
3 Likes
Related - I will also post this informative diagram I made in a few minutes to explain a bit more all of this, including OpenComposite-ACC:
6 Likes
I made a full MSFS VR guide for relatively high spec PC, but might help others with similar or lower specs too.
19 Likes
Great video that I highly recommend! Thanks @FlyWithNick8888!
3 Likes
I must have missed a lot of SteamVR improvements
Thanks for the in depth video. 
I don’t understand how he could possible get over 30 FPS with 160/100/100. We have practically identical systems. He has 3090 with 5900x, I have a 3080ti with 5800x, and I can’t push OpenXR Dev above 100 if both TOOLKIT and In-game render are at 100, let alone 160! It’s almost suspicious. I can get solid 30FPS in and out of cockpit with 100/100/100. That’s my limit. Is something wrong with my system??
These are my Toolkit Detailed FPS number:
app cpu 5845
app gpu 30434
lay cpu50
pre gpu 0
scl gpu 281
pst gpu111
ovl cpu 1941
ovl gpu 341
bias 12
vrs 110
I’m running 3080Ti with 5600x
Running 150/80 FSR/100 since last night and in most places getting 35-38fps (30-33 in NYC Activity as a test). Think I have a little headroom to bring the FSR up a little more. Will test further tonight.
These are my Detailed FPS numbers when I push Devtool to 150. Can anyone read these?
app cpu10000
app gpu37500
lay cpu 55
pre gpu 0
scl gpu 434
pst gpu 165
ocl cpu 5765
ocl gpu 263
bias 12
vrs 96
This is detailed here: Overlay | OpenXR Toolkit
But I don’t think it’s helpful. You are both seeing 30+ milliseconds in app GPU which indicates a LOT of GPU load from your game resolution and LOD settings
How do I get the “Detailed” option to show up for the Overlay like I see and read about other users showing?
You need to enable Experimental mode in the desktop app.
Note: the next version will have 3 options
- FPS
- Advanced (FPS with the app CPU/GPU too)
- Developer (all the stuff that only CptLucky8 and I care about but no one else should)
4 Likes
I had thought that enabling show expert settings on the Menu menu would do the trick, but obviously not. I will try enabling experimental settings thanks. Those extra developer details will be great for nerds like me 
I probably need to clean this up…
Experimental was designed for features we did not want everyone to see because they weren’t finished.
Expert was designed to hide advanced settings to not overwhelm with too many settings…
But there’s nothing in Experimental today except for this Detailed overlay. Probably should just remove Experimental and put everything under Expert…
1 Like