Orion23

I'm aware that the FMS stuffs (VNAV) are featured in the future update, but how about the LNAV? Does the new update using the new Navdata format? I'm ok with the broken VNAV back in the XP11, however LNAV was the biggest issue for me back then.

I was able to reproduce the CTD and recorded a video. Seems like the CTD would happened if you choose to direct to a waypoint that 1)has discontinuity after it, 2) the same waypoint after the discontinuity.

Another CTD when I tried to direct flight to a waypoint. Flight was from VHHH - ZGHA, route was: BEKO2B BEKOL A461 YIN A461 LIG LIG2X CTD when I choose direct flight to LIG Log5.txt

Thanks for the follow up. Let me know if you need more logs and etc., I could re-do this flight and try to reproduce this bug again using non-persisitence mode. I also asked my friend to did the exact same route and direct to waypoint LANDU at the same time I did, no CTD for him.

Thanks for the follow up, what confused me about is how the aircrafts using the navdata, I thought both Zibo, Toliss and Challenger are using the default xplane navdata, which I got from the navigraph and put them into the custom data folder, and I also use the default scenery for the ZHCC which definity has RW12L/30R, so the problem is, where does the default aircraft read the navdata from? I'm gonna report this to the Laminar later today. Thank you again.

The default G1000 has the same problem.

I was able to reproduce the CTD problem. Same route from EKCH to EDDM with new airframe. CTD when I select direct fly to waypoint LANDU, I was able to made a screenshot when the game freezed before CTD. Log4.txt

When setting destination airport as ZHCC, as long as I click 'proc', a prompt would displayed indicated 'Procedures could not be loaded: Missing waypoint RW12L at ZHCC' I've tired to load the STAR and Appraoch in different aircrafts (Challenger 650, Zibo 738 and Toliss), they are working properly. Log.txt

I uplink the flight plan from the simbiref, route was: EKCH/22R SIMEG8C SIMEG M736 PEROM M736 BAKDO DCT TOPDI DCT SODRO T703 LULAR T105 LANDU LANDU2B EDDM/26R The first CTD happened when I choose direct LANDU, the detailed are in the log1. Second CTD happened during the secure checklist, after turning off the APU gen, third CTD happened when I resotred the flight (the flight that caused CTD during the APU gen turn off) by loading the latest state, step into the cockpit and CTD. Those logs are log2 and log3. Log1.txt Log2.txt Log3.txt

First time was fine, second time CTD. Condition: Loaded 1000ft AGL state, spawned in, clicked ATS disengage button on joystick, press A/P disconnect button on jostick, a little stutter and than CTD. Log.txt

LOL, careful with engine fire agent relase button, the clickbox is wrong, you could actually discharge the bottle without opening the cover by clicking the top left hand corner (located left side of ATS button), I found this out in a bad way and manged a single engine landing, spent an hour on the ground trying to refill the bottle cause I really felt I got some special connection with that specific airframe. lol

I did a go-around earier today, seems like FO would do some check list during the go-around, and the landing checklist will be pasued. However, after go-around I retract the landing gear by myself as well as the flaps, during the second approach the FO doesn't seems undertand I wanted to land, I contiuned with landing checklist and put the gear down, the FO was still in the go-around mode and help me retract my gear and set flaps to 20. Is this a bug or I should skip to the next checklist after go-around?