Presumably yes, however there seem to be a good number of long running issues on here that you would think the same.
Given as they clearly would have known about this before shipping it anyway……
Thanks for the post Mathijs,
Always great to hear directly from a developer, much appreciated.
That is what we believe to be the case at this moment. The change that causes this problem was inserted at the very last minute, days before the release, so it really feels like an unwanted effect. Even their partners, Inibuild, were not informed and have the same issues as we (and many others), and you would expect that to be avoided in a well-planned release.
Mathijs Kok
PMDG
3 Likes
While this work around allows you to flight in VR … The frame rate sucks and its more frustrating than its worth. I have a super hi-end system 9950X3D + 5090 + Pimax Super. There needs to be a permanent fix not a work around that does not work.
2 Likes
I doubt this was in VR. 2D no issue when running FG.
Andrew
Well, I guess my FS2024 is unplayable until the next update. This sucks. I’m seeing the same with my Aero. Sim is unusable in VR.
Ray
1 Like
Any hope for a hotfix? With just 30 votes showing at the top, confidence is low hah? 
Ray
IMO this should be fixed by MS / Asobo.
1 Like
This year, next year, sometime, never
This needs a quick fix! It’s very critical to VR users!
I have no idea how their project management goes. And I believe they just release it and everyone is enjoying their holiday. Leave us in the bleak.
As we still have no idea if Microsoft considers this a bug (and thus will fix it), we are now looking at a fix from our side. We find it unacceptable that our product is not usable.
Mathijs Kok
PMDG
2 Likes
VR LoD curve issue [SU3 / 1.5.27.0] is bug-logged so I guess they do.
1 Like
My 5 Cent as Pmdg Customer: should be Action from MS or Asobo. If worse comes to worse i go back t to msfs2000
Thank you for this report. We’ve moved your topic into the User Support Hub.
The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.
If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.
If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.
All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.
In cases of third party issues, the developer contacts the MSFS SDK group and the issues are dealt with there.
Had recently returned to 2024 VR but this was so avoidable and a huge disappointment.
Back to Elite Dangerous for now which is fantastic using the Reverb G2 
2 Likes
We agree. But these are our customers, and we just feel bad leaving them in the cold. No promises, but at least we are looking at the issue now.
2 Likes
The collision meshes in 2024 VR are a flaming hot mess on all the editions I’ve tried.
This wasn’t the case in early 2020 versions. But the problem seemed to creep in more and more on every 2020 SU release. Every airplane update just stated started getting worse.
Then 2024 hits and it’s like derp, 3D objects require some kind of 3D ability to map correctly?
It’s like they got rid of VR QA testing or something.
Thank you! I really appreciate you guys.
Ray
I thought the update would fix VR. My 777 in VR is still displaying the same symptoms.