SteamVR has never had an option there to switch away from SteamVR to another runtime. You would have to change it from within the other runtime.

SteamVR has a regular OpenXR runtime, just like the others. OpenVR is just a separate APi altogether.

Besides, I'm not sure if the Vive Pro supports any other OpenXR runtimes. It's a native SteamVR headset, and you wouldn't have get any benefit from switching, like you would with another headset like Oculus or WMR that would get chained to their own native compositor through SteamVR.

You may be right mate. Based on the latest 2.5 update it sounded to me like they were going to implement a separate industry standard OpenXR api. I may have read too much into that, lol!

With my Quest 3 and Quest Pro headsets I don't see any other OpenXR api's either. With Link/Air Link there already is an Oculus OpenXR runtime option in the meta-link PC app so maybe this isn't necessary anyway. Thanks for your reply mate and cheers.

I had to install the viveport software for vive pro before the openxr runtimes would appear in steamvr settings. It made a huge difference for ATS2, as they have also updated to openxr.

Originally posted by Budderick:

I had to install the viveport software for vive pro before the openxr runtimes would appear in steamvr settings. It made a huge difference for ATS2, as they have also updated to openxr.

I never needed to do this with my +4.5yo Vive Pro1. Maybe because it's a native SteamVR headset (last one Vive made). I've always gotten the option to use SteamVR as the openxr runtime with my VP1. No other separate openxr runtime option. I'm guessing that Valve is just tweaking its SteamVR openxr runtime. In any case, it all seems to work fine with apps like msfs2020 that need openxr.