David Kegley

I can confirm that I am experiencing what appears to be the same VR-specific issue. It has occurred on two separate flights, with a complete computer reboot between them. When the problem begins, entire groups of cockpit controls highlight blue simultaneously. The mouse remains active, but it operates multiple controls at once—or controls other than the one being pointed at. At the same time, virtually all cockpit lights and annunciators illuminate as though the cockpit light-test function had been activated. I am also seeing displaced cockpit geometry. The most obvious example appears to be a windshield-wiper control knob or dial floating over the windshield rather than remaining attached to its panel. This sounds very similar to the floating knob mentioned in the original report. The problem only occurs in VR. Pressing Ctrl+Tab to leave VR immediately restores the cockpit to normal, and the aircraft remains completely flyable in 2D with no relevant warnings or system errors. If I re-enter VR, the broken lighting, highlighting, geometry and mouse interaction return. The failure occurred on approximately the same timeline during both attempts—about 10 minutes after takeoff. I initially noticed it while configuring the arrival and runway in the FMS during climb-out. However, I now suspect the FMS activity may be coincidental and that the actual trigger may be time spent airborne. On my second attempt, I completed the aircraft setup considerably faster, but the problem still appeared at approximately the same point after takeoff. I have not been able to reproduce it while the aircraft is on the ground, regardless of how much time I spend setting up the aircraft. Both tests used the same SimBrief-planned KDEN–KDFW flight and departure: • Headset: Pimax Crystal Light • VR software/OpenXR runtime: Pimax Play • CPU: AMD Ryzen 9 7950X3D • GPU: NVIDIA RTX 4090 • RAM: 64 GB • Simulator: MSFS 2024 • Simulator versions tested: SU6 and SU7 beta • A380 version: Marketplace release-day v1.0.0 • Flight-planning integration: Navigraph One occurrence was under SU7 beta and the other under SU6, with a computer reboot between tests. The behavior was effectively identical in both simulator versions, so it does not appear to be confined to the SU7 beta. Attempting to restart or reload the flight after the corruption appears has also resulted in a crash to desktop. After completely restarting the simulator, the A380 works normally in VR again for approximately 10 minutes after takeoff, after which the same problem returns. Unfortunately, I will not have an opportunity to record a video immediately, but I wanted to add an independent confirmation because the issue is repeatable and currently prevents completing a flight in VR. I would be happy to provide any additional settings or configuration information that may help isolate it.