Asobo are you listening to VR Users after SU3?

Discussion Hub General Discussion
, , , , ,
1

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.

1 Like
2

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.

1 Like
3

I agree. Asobo/MS’s silence on this matter is deafening .

4

So this issue only occurs when combining this specific plane and VR?

5

This seems like an issue with that plane. I have no issues like that with any of the planes I’ve tried since SU3 - which is quite a few.

1 Like
6

Nope, this issue affects many, see VR LoD curve issue [SU3 / 1.5.27.0] , also vanilla MS/Asobo aircraft.

7

Which Vanilla aircraft, because I don’t have the problem, but there’s a fair few I don’t fly.

8

You clicked the link in my post, right?

Plus the H125, R66 and Bell 407, at least.

10

Those all work fine for me. I actually just went through and was trying them out after the new release that kinda bombed. The 135.

Edit: Working fine… By that I mean the frame rate etc. The 407 doesn’t fly very well.

11

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

12

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.

13

Same thing is happening with the iniBuilds A350. Very disappointed with this update and as usual /crickets from the devs.

1 Like
14

the stock silence from Asobo is so loud that it hurts in the ears.

will this be the situation until SU4 then!

15

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.

16

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:

  1. Something very much sprung on them at the last second before release.
  2. An actual bug in the implementation that should be fixed.
  3. 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.

1 Like
17

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.