I can only take solace in the fact it does affect such high profile aircraft so the issue will get more visibility (*chuckles*) whether from a developer reporting on the SDK forum or from users who haven’t been in the SU3 beta.
2 Likes
There are a number of lod issues on in the cockpit, as you say just leaning forward just a little is enough to show the issues
Yeah, I know, but I don’t really care about a screw head displayed in more details, the airspeed is a different story though…
Bug report here to vote: H125 Airspeed Indicator Shows 0 in Default VR View
SU3 release A321. Gear up at ready for takeoff with missing texture. Move back a bit, and gear goes down, texture appears.
1 Like
Well the FlightFX Citation X also now suffers lights disappearing from the autopilot panel due to this issue. You have to lean in to see what autopilot functions you have turned on or off. This could have been a great release for VR fixes and in the end they borked it and then released it to the masses anyway.
4 Likes
You should move this to the general bug reporting categorie, so the thread stays intact. It’s an absolute shame they just ignored the feedback on this one. This is game breaking for VR users. Considering how long it takes them to release sim updates, I will be off the simulator for three months until this is fixed. What a shame. Shame on you Microsoft.
5 Likes
I’m not sure what the normal procedure is here, I was going to recreate the bug thread in the main virtual reality forum once I had time to try the SU3 release build for myself.
If any mod reads this feel free to move this thread to the main virtual reality forum or I can just make another.
Also seeing this issue in Fenix A32x, PMDG 777 and Citation X. Disappointing that SU3 was released with this bug still present, hakes some of these aircraft unusable.
I’m seeing this effect on most planes I fly in.
It is certainly a bug, but Asobo are ignoring it. If this thread is closed without any resolution and all our votes are lost, it would show how little regard Asobo have for VR despite their original promises of VR being treated as a full platform.
As requested above, could a Community Manager PLEASE move this out of SU3 beta, and feedback-log it (or preferably bug-log it, as it is certainly reproducible).
1 Like
Totally unacceptable that this issue wasn’t even logged let alone fixed in the beta, care to explain please moderators? You’re here to forward on these issues not ignore them.
3 Likes
A new thread for this bug has been created in the main Virtual Reality bug reporting forum here:
I have taken the time to record some raw footage from my Meta Quest 3 showing the issues in some aircraft which shows the issue much better than a static screenshot would.
3 Likes
Unfortunately the votes from the current thread have not yet been merged with those on the new thread.
Someone in a position of power please action this.
Closed, as this issue is still occurring in the SU3 release, and the OP has created a new topic for it:
Please continue to provide feedback in that topic. - Thanks!