Open C-Schaffhausen opened 2 days ago
Also tried non RF SID BEKOL5A, which also failed in a similar way
Video support https://youtu.be/LwfETs9C2p8
Disabled VHHH scenery but kept the latest navdata, same bug https://youtu.be/Zz9GMp4zqFQ
Thanks for the detailed reports! Will check this out and see what’s happening.
Another test flight with nothing in the Community folder, except FBW A380 and A380 texture. Same issue. https://youtu.be/Y9ytO6h03oY
Interestingly it flies absolutely fine in the A32NX (BEKO1X).
Interestingly it flies absolutely fine in the A32NX (BEKO1X).
Interesting, did your A380 have the same issue though?
Interestingly it flies absolutely fine in the A32NX (BEKO1X).
fix(fcu-api): fix KOHLSMANN_SET and custom baro set events #9617
I'm not sure how this is relevant? Can you explain?
I'm not sure how this is relevant? Can you explain? fix(fcu-api): fix KOHLSMANN_SET and custom baro set events #9617
How are the above relevant posts relevant?
Aircraft Version
Development
Build info
Describe the bug
FS2020
I flew the A380 in FS2020 on the BEKOL1X departure out of VHHH which contain an RF segment after PORPA, the ND keep indicating the next waypoint is PORPA at 0.8NM even though the aircraft was over PORPA, and it also lost its LNAV capability, HDG mode works. I tried turning FD off and ON again and directing to other waypoints, but none worked.
Expected behavior
I expect the aircraft to follow the RF leg and the LNAV capability should not be affected. Next waypoint indication should jump to the next logical waypoint/next DIR waypoint when commanded
Steps to reproduce
References (optional)
No response
Additional info (optional)
No response
Discord Username (optional)
C.Schaffhausen