[Fixed 1.6] CTD when pressing NAV button

[Kari]

Never had this happen before but it just happened 3 times in a row. If I pressed NAV the sim would stutter, resume like everything is fine, then hard crash a few seconds later. This is the route I was on KLAX DOTSS2 CNERY DCT BLH DCT SALOM DCT EWM DCT FUSCO DCT DILLO LAIKS3 KAUS with a departure from runway 25L at LAX and I already had ILS 18L programmed for AUS. The first two crashes I was on the ground; the first was directly before starting the engines and the second was directly after. The 3rd time was just after raising the gear and flaps, somewhere airborne below 1000 feet. For the 2nd and 3rd crashes, I just reloaded the sim into the state my aircraft was in before the crash.

 

Also, not sure if it would affect anything, but the first two crashes I pressed the button bound to the NAV command on my Honeycomb Bravo, the 3rd I pressed the digital button on the glareshield in the sim.

CL650_Log.txt Log.txt

Edited April 15, 2022 by oisin650

[Kari]

I gave up for a while last night but I'm trying the exact same route again today and, at least for now, NAV is working. I saw there was some other similar crashes and I'm thinking that I *possibly* had a discontinuity between DILLO that was loaded with flight plan uplink and DILLO that the STAR loaded. I'm also not sure if I accidentally had my nav sources on VOR/LOC and if that could've been an issue.

Edited April 13, 2022 by Kari

[Pils]

1 minute ago, Kari said:

I gave up for a while last night but I'm trying the exact same route again today and, at least for now, NAV is working. I saw there was some other similar crashes and I'm thinking that I *possibly* had a discontinuity between DILLO that was loaded with flight plan uplink and DILLO that the STAR loaded. I'm also not sure if I accidentally had my nav sources on VOR/LOC and if that could've been an issue.

Thanks for trying. I suspect this may be one of the crashes already fixed but it’ll be looked at regardless.

[ois650]

Sounds very familiar. I concur with Pils, this has been fixed in the beta build. We'll park it for now anyway. Thanks for your report.