I can confirm I’m having the same issue in VR, especially when departing from CYUL (Montreal) with a complex aircraft like pmdg 777 or ifly 737.
Since SU-3, I experience a massive FPS drop, almost down 50%, but only when the built-in Foveated Rendering in MSFS is enabled.
If I disable MSFS’s native Foveated Rendering and use the one from OpenXR Toolkit instead, my performance returns to a level similar to SU-2 with Foveated Rendering enabled.
I just re-installed the beta. Disabled Foveated Rendering in MSFS enabled it in OpenXR Toolkit and yes that’s it. You found it..
I’ll continue with the beta for now it’s useable again.
Thanks very much for sharing…
Disabling foveated rendering returns some fps, but not all. From 12 to 20 fps at TFFJ. But something like MK Studios EIDW Dublin is perfectly fine.
Nothing has changed in 1.5.15.0. I’m a little concerned that this thread hasn’t been marked as ‘bug-logged’ yet. VR isn’t really usable in this state.
Bad performance of World Update XI Canadian airport CYDA, for a small airport.
Do you have the same issue if you follow the OP’s steps to reproduce it?•
Provide extra information to complete the original description of the issue:
•
I’m very disappointed with the progress of the different betas. For me, it’s more of an Alpha than a beta. Indeed, it’s impossible to play in VR in the current state of the simulation. When I’m at a third-party airport, the FPS drop is so drastic. Looking at buildings, I get a 20-25 FPS drop. When I move away from the terminals, the FPS recovers. I recently upgraded from an RTX 4090 to an RTX 5090. , the msfs2024 game need to change the name ! on: wait wait wait 2026…
•
Still seeing drastic performance drops at some handcrafted airports in VR, such as YBRK and YGLA.
Other handcrafted airports such as YMLT and YCBG are fine.
Otherwise very smooth performance, and no noticeable stuttering in 1.5.15
7800x3D, 4090, ,32gb DDR5, BS Beyond VR
Can you tell us please if they wanna fix this bug or they give a ■■■■ about it? We cant even try this beta correctly with this bug
Initially when MSFS2020 was introduced, there was a VR development team in Asobo. Seemingly, this team was disbanded and VR responsibility (as a “platform”) was dispersed among the other teams. This resulted in stoping any VR development.
Unexpectedly in MSFS2024 SU2 Foveated Rendering was cleverly, but not issue-free (instancing) introduced. This was only possible by a skilled VR developer in Asobo team.
Now, in SU3 beta, we are observing severe VR/LOD issues. Does it mean that the skilled VR developer who implemented FR (MSFS2024 is one of very few games with native FR support) is no longer with Asobo? This would be a bad news for the VR flyers.
Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes
Provide extra information to complete the original description of the issue:
• Hand crafted airports have very significant FPS hits in VR, essentially making the airports non-usable. Disabling FFV in the sim helped with a ‘couple’ of frames but not to the point of any significance. I am not able to do any flight activity at hand crafted airports in its current state.
•Nvidia 4090 zotac amp
•32gb DD5 ram
•Intel I7 14900K
If relevant, provide additional screenshots/video:
•
Additional context
It appears, at least for me, that the issue is confined to Asobo handcrafted airports and not 3rd party ones. I downloaded the KMDW to see if I would have the same issue and I did not. I’ve tried several of the Asobo ones though(KDFW, KLAX, KATL) all of them experience the heavy FPS hits immediately after loading in. Not sure if other folks are fine with 3rd party customized airports but would like to know out of curiosity.
Yes I’m experiencing this also even on a brand new scenery for Doha d today by Ini Builds.
I have the absolute best specs you can get. 5090. Top of the line, CPU and Pimax VR headset.
Even on medium graphic settings in VR it’s still glitching hard when you are around the airport. If you’re at a stock standard non-custom airport it’s fine.
There are still no signs that a fix to this issue is being worked on.
For VR, it’s crucial to have a constant FPS. With SU1 and the first few SU2 beta builds, it was possible to achieve a constant locked FPS at 1/2 or 1/3 refresh rate everywhere with motion reprojection.
VR is unusable in its current state.