Hi, I haven’t been flying for three weeks. During my hiatus, I got a new MSFS beta (I’m on 1.35.18.0 now) and a new SteamVR version (2.1.4, also tried the beta). I’m on the latest Nvidia driver now (546.17), the previous driver showed the same behavior (546.01, iirc).
When I launch MSFS while SteamVR is running, starting the sim takes much longer than usual. When it’s loaded, the user interface is very sluggish, there’s a delay of several seconds between any mouse movement or click and anything happening in the MSFS window (like highlighting a UI element when the mouse hovers over it). Windowed or fullscreen doesn’t make a difference. Only the MSFS window is affected, the rest of the system stays responsive.
When I quit SteamVR, the MSFS UI immediately becomes responsive. I launch SteamVR again, the UI becomes unresponsive. I can repeat this multiple times, same result every time.
I did not enter VR, this is happening in pancake mode on the desktop – with the sluggish UI, I’m not able to set up a flight.
Again: The mere presence of the SteamVR client is enough to render MSFS unusable on my system. I have not experienced an issue like this before today. Last time I used MSFS, which was on Halloween (10/31) everything was fine. There were no hardware changes to my system in the past three weeks.
I searched the forum for matching reports, but couldn’t find any. I would appreciate any advice.
What headset are you using? Does it run on Steam VR only? No direct OpenXR runtime available?
If you must stick to SteamVR - consider launching the sim first, without launching SteamVR upfront. With flight loaded, switch to VR in the sim, this will trigger the start of SteamVR
Some users reported that SteamVR starting this way works well.
Check if your SteamVR settings did not change, if you don’t have some extreme resoultion.
I had this problem in MSFS with my Quest 2, both with link cable and with Virtual Desktop. Tried changing a billion settings (including regedit and making a bat file) to optimize performance to no avail. When I got a tip to switch from SteamVR to VDXR runtime in Virtual Desktop. Now it is running like a champ wireless in Virtual Desktop. I believe Steam broke their VR in a recent update. Seems like it to me at least. You don’t mention Virtual Desktop, but I sure would give it a try if that is an option for you.
I’m using a Valve Index, so I fear I’m limited to SteamVR. I tried starting SteamVR only after starting the flight in the sim, but both SteamVR and MSFS CTD’ed within a couple of seconds, while I was interacting with the new SteamVR UI.
I hate that I can’t simply use a previous version of SteamVR.
I’ll see if Steam support has anything helpful to say.
When you switch to VR in sim for the first time, Steam VR should start automatically without any interaction with SteamVR UI. But I have zero experience with Index, so I might wrong.
I works like I described with Pimax Crystal (ifnInuse SteamVR, which I usually don’t).
Sorry, I wasn’t clear about this: I was interacting with UI elements within VR when I experienced the CTD. I started the flight, switched to VR in the sim, SteamVR got launched automatically. In VR, I had a “view” with UI stuff in front of me, which I could close, but also a large desktop view (showing the split MSFS window) to my left and when I tried to close that (not the application, only the view showing the desktop), both MSFS and SteamVR crashed.
I’m wondering why I’m the only person to experience issues like that. Perhaps the result of an unlucky combination of settings.
mmmkay, I kinda figured out how to get in the air without CTD’ing. So this is no longer a showstopper for me, it’s now just an annoyance. I hope Valve will fix the issue, they seem to be aware of problems with certain games in theater mode in VR.
SteamVR 2.1.7 (beta release from today) appears to resolve the issue for me.