File a bug.

World objects on MAX and reflection middle for diddle. Don’t really want to start compromising on these after finally getting them up there with early 11.50 and vulkan

Even in 11.50 it works fine with OGL. I only have the issue when using Vulkan. I’ve done a clean install of the Oculus software just in case something got bunged up there but still have the issue. Once I restart Oculus and enable VR again it all works great. To me, it appears that the Oculus software is crashing during the load of X-Plane and thus X-Plane loses the display and then disables VR. Then I restart Oculus and enable VR and it’s happy. I’ve seen a couple other comments with people having very similar issues but never a peep from LR on ackowledgement, etc. I guess since there’s a workaround it’s not a high priority.

I had a similar issue using the Oculus Rift CV1 with an earlier Beta of 11.50. I reported the bug, but LR were unable to reproduce the issue in house. I didn’t have this issue when using a WMR VR headset with any of the 11.50 betas. I didn’t update my 11.41 to the beta, I did a clean install for 11.50. I have always wondered if the Oculus software is treating the two X-Plane installs differently. I haven’t tried the Oculus with the latest beta, I prefer to use the Reverb.

Hello,

So what to do?
Since B11 there was a surge or drop of FPS in heavily built-up areas, meaning when changing the view FPS drops to 12-17FPS and recovers to 50FPS 2 to 10 seconds later. Is my hardware faulty?

Thanks, Dan

As for VR with Rift S…it would be great if LR could fix the hang on exit issue when using VR. It’s a total pain to have to force kill X-Plane every time you exit.

Also, every time I go to start a flight I end up with my headset going black with an orange LED and the following in the log (and yes becoming is mispelled in your log as it shows below):

0:02:03.204 E/OVR: Session display lost, becmoing a zombie.
0:02:03.263 E/VR_BRIDGE: Shutting down hardware because the VR HAL is now in a zombie state.
0:02:03.466 I/OVR: Shutting Down VR Subsystem.

At that point I just restart the oculus software and reenable VR and everything works. Working with Jennifer I went back to 11.41 to test…everything works without any issues…then tried OGL on 11.50 and everything works without any issues…but with Vulkan it happens every time. Bug has been filed but never received an XPD number. So do not know if it’s even on anyone’s radar to look into.

I think that between plugins (which you can’t control and keep warning about) and expecting more “sliders right” than users systems can handle, you are doing great. As I tell my Pastor, you can’t please everybody, but he, like you, keep trying!

I have an i9 iMac with a Vega …48? – I just wanted to say that not only is metal kicking butt and taking names, when I ramp up settings or fly in a scenery heavy area and get 20-30fps, its waaaaaay smoother than earlier versions. I always got the sense that when it was in that range, it was rendering, but not necessarily displaying 20-30fps (like, imagine the frame being delayed and flushed out of the buffer and not making it to the screen…) this might be my imagination, or a result of like some internal time-stepping inside of the airport vehicle animations or something.

I don’t know what it is, but I’m just trying to say when it goes to 40-60, thats awesome, but even at 20-30 its waaay more playable. Thank you!

We don’t have any more perf optimization to do, but there’s always the chance there’s still a bug. Sidney’s looking into stutters related to AGP transfers, but in some cases we’ve had users say “it stutters” and when we gather a trace off their system, they’re trying to get X-Plane to just lift way more weight than it could possibly push in VR.