You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was performing a flight from Singapore to HongKong with the FBW A380 Dev version 8k, and at the gate, the fix info page was working fine ie. I entered a 25nm radius for MSA awareness, etc. However, when I was inflight (39000 ft), I wanted to use the fix info page but when I clicked it, the FMS went blank but the yellow curser was still visible. When I clicked on the F-Plan button below the FMS (or really any FMS button), the FMS came back to normal. In short, the fix info page worked fine at the gate but the screen went black when I pressed it in flight.
Expected behavior
The fix info page should show up like expected.
Steps to reproduce
Use the Dev version 8k
Go to around 39000 ft, maybe enter in a flight plan
Click the fix info page from the F-Plan page
References (optional)
No response
Additional info (optional)
No response
Discord Username (optional)
rithr#5323
The text was updated successfully, but these errors were encountered:
Simulator
2020
Aircraft Version
Development (8k)
Build info
Describe the bug
I was performing a flight from Singapore to HongKong with the FBW A380 Dev version 8k, and at the gate, the fix info page was working fine ie. I entered a 25nm radius for MSA awareness, etc. However, when I was inflight (39000 ft), I wanted to use the fix info page but when I clicked it, the FMS went blank but the yellow curser was still visible. When I clicked on the F-Plan button below the FMS (or really any FMS button), the FMS came back to normal. In short, the fix info page worked fine at the gate but the screen went black when I pressed it in flight.
Expected behavior
The fix info page should show up like expected.
Steps to reproduce
References (optional)
No response
Additional info (optional)
No response
Discord Username (optional)
rithr#5323
The text was updated successfully, but these errors were encountered: