[Philipp] Random CTD when editing FPL in flight (w/ xsquawkbox)

[charly]

Hi Philipp,

I've had 2 CTD in similar conditions:

- online filght (xsquawkbox)

- leveled flight with A/P on

- try adding to add wpt on route => CTD

(note: once it was after a G/A, second when I've been given a STAR starting from a wpt not on fpl).

I forgot to save the logs for the first one. I did for the second, together with a screenshot: I was trying to add XIRBI before LFMN.

Log.txtcrash_log.txt

This looks like a random one. Sometimes I can edit fpl in flight w/o crashing.

If you tell me xsquawkbox could be the reason of the crash, I'll try to replicate after deactivating it (but as I do only enjoy flying online...)

BTW, I also found a reliable way to CTD: select a TO fix on the FPL page with no destination airport would cause a 100% CTD. Won't call that a bug as it's not within "standard use", but any CTD would be nice to prevent.

Thks for support,

Charles

Win7 - X-Plane 9.7 - CRJ 1.41 - VASFMC_NATIVE_1201

Edited January 28, 2012 by charly

[philipp]

Thanks for the report. These issues have been fixed in 1.4.2, which I hope to pump out shortly.

Philipp

[charly]

Thks Philipp! Should you need some more Beta-testers...

Charly

[charly]

Bug closed on 1.4.2! Thank you Philipp! At least w/o xsquawkbox. I'll try with next time.

Did a "FMS stress test" tonight: LFLB-LFMN with tenths of DCT, STAR changes, FPL editing... no crash.

Just noticed a strange behavior:

- inbound LFMN on an ABDIL6R arrival

- STAR ABD6R selected on FMS, but with no approach/RWY & TRANS selected, as I was intending to go for the famous VORa&VPT 04L @ Nice. As it does not exist in Navigraph data, I did add manually MUS & RIVRU before LFMN.

- as I was somewhere between MUS & RIVRU but outside of the track (it's no direct in between these), I changed my mind for an ILS (picture below will tell you why )

- So I selected ILS04L with TRANS MUS onto the FMS

- Worked fine, BUT the name of the fix it created close before my current position: LFLB (home airport). Indeed, it was not. (btw, can't guess if it was a fix created @ current pos to "initialize" a new track or any other fix just with wrong name).

I'll try to replicate. But hey, Philipp, it's a MINOR issue. No hurry.

Thks again!

Charles

Edited January 31, 2012 by charly

[Japo32]

Good!