AlexLehman14

Hi all, I just purchased the TBM900 and was doing some trials around MMPR. In terms of FPL, I had only entered MMPR - MMPR that way I could select approaches if desired. After a go-around, I engaged the AP to HDG and ALT hold mode. Yaw Damper was active. I selected the RNAV for runway 22 on the Procedures menu and activated it. The CDI was in VOR 1 view. I entered a Direct to the initial approach fix, and accepted it. Aircraft remained in HDG lateral mode for about 3 seconds, then I cycled the CDI to display the GPS view instead of the VOR 1. Before displaying the GPS view Xplane crashed. This was repeated following the steps above, and Xplane crashed again at this airport and MMGL. When reviewing the TBM900_Log, the following error line was captured. See attached log for reference. 2020-07-03 23:05:34 TBM900[ap.c:2010]: assertion "!__builtin_choose_expr ( __builtin_types_compatible_p (__typeof__ (o), double), __isnan(o), __builtin_choose_expr ( __builtin_types_compatible_p (__typeof__ (o), float), __isnanf(o), __builtin_choose_expr ( __builtin_types_compatible_p (__typeof__ (o), long double), __isnanl(o), (__builtin_trap(),o))))" failed: After further testing a repeatable set of actions was seen to cause the issue. The HDG mode is active, NAV is not armed, and CDI is in the VOR display. We enter a direct to a GPS point, arm the NAV mode (which displays a VOR armed in the PFD), and then cycle the CDI to GPS (instead of VOR 1). Xplane crashes with the message above before reaching the GPS display. Something is incorrectly coded on the switching of NAV modes and activation from HDG to NAV based on the GPS. This is not observed if the CDI is set to GPS first, then the NAV autopilot mode is clicked. Aircraft switches from HDG to GPS mode without any issue. Thank you for your quick response. Alejandro Lehman Rubio TBM900_Log.txt