I am writing this post due to frustration with Asobo/Microsoft after breaking MSFS2024 for VR users with SU 3. I cannot not use the PMDG 777 in VR. While the workaround mentioned in the forum gets me into a working cockpit the frame rate and stuttering is so bad you cannot use it. I created a ticket with PMDG and PMDG have stated they cannot do anything to resolve this isssue. It is an Asobo problem introduced with SU3.
Here is the latest feedback from PMDG
Hello Andrew
You actually need to take the issue up with Micrrosoft/Asobo as they are aware of this issue when it started in the SU3 Beta and claimed they would address it at some point. That did not happen in SU3 so I don’t know what they plan to do to fix it but it isn’t something we can fix .
Someone needs to take resposibilty for this. As like many other I have spent significant amounts of money on flight sim software and hardware.
I too would greatly appreciate a statement/guidance on that matter. Right now we have no idea whether this is a bug that Asobo will fix when they get to it, or whether this is the new simulator standard that all aircraft need to be updated to by the developers.
The default 747 and 787 have issues with LOD, the lettering on the instrument lights and on the knobs and switches disappear when you move your head in VR
Ok, that’s fair. I don’t fly those. I did run across one aircraft that had that problem - I forget which. I solved it by moving the camera forward very slightly. I’d forgotten about that. It was what one of the helo’s.
Hopefully PMDG and iniBuild are talking to Asobo… Fingers crossed for a Hotfix but given their history with 2020 and VR users . We may have to wait for SU4.
From every indication I have seen the devs have been largely left to sort out on their own. Ini are working on a patch for the 350….which is great except really it seems they should not have to.
PMDG haven’t clarified whether they are working on anything yet although they have been very clear they see this as:
Something very much sprung on them at the last second before release.
An actual bug in the implementation that should be fixed.
Weeks of work on their end.
I think it’s a reasonable conclusion to draw that the fact this only occurs in VR and not flat makes it an Asobo bug. Now there is likely some technical nuance there but from a customer perspective it’s pretty clear cut.
Additionally the silence is deafening and speaks to the apparent disregard for VR users. This was not a problem throughout the SU3 beta and then dropped in the last days before release. Poor form all around really and extends a middle finger to a set of users who have spent a good chunk of change in many cases to experience MSFS in VR, that doesn’t make us more important by any means but it seems we remain an afterthought.
Does it no go away if you move the camera very slightly forward? The only aircraft I ran into that problem on worked that way. Might be a work-around while they figure it out.
yes. this is my assumption. if you listen to Jörg on the gamescon in Cologne, their plan was long term, getting msfs2024 up to the expected level by SU4, not earlier.
as SU3 did take 3 months, it will be not before November for SU4.
The 777 and A350 are completely unflyable. This is not just a matter of minor glitches or slight functionality issues, the entire cockpit is inoperable. None of the buttons respond to any input, making the aircraft entirely unplayable.
Asobo/MS, Jorg & Martial have always failed to properly listen to VR users, case in point the 2020 Shutdown Bug that they introduced is deemed not important enough to fix plus the disgraceful way they released SU7 with known severe toolbar issues, only to half fix them months later and never return it to its previous better state, plus countless other issue over the years.
I wouldn’t be surprised if Jerome (the VR coder who was finally brought in to help, as he introduced foveated rendering amongst other things in the recent past) has been moved onto other areas or gone completely, just the same way they disbanded the “VR Team” years ago when it was very clear that VR needed a ton of work. Just like it does still to this day, nothing really surprises me anymore, I’m just annoyed, frustrated and amazed that Jorg allows his team to be so ignorant towards VR users.
plus the disgraceful way they released SU7 with known severe toolbar issues, only to half fix them months later and never return it to its previous better state, plus countless other issue over the years.