Open user2684 opened 10 years ago
From Dco:
With a "basic" aircraft, I mean with no plugin, it works. There is no problem with A380 from Peter Hager For X737 EADT with X737FMC plugin the xcontrol plugin doesn't work but there is no crash (message FMS not ready)
Made some progress by generating a map file for tracking the crash and disabling optimization. The issue needs to be replicated
The issue is due to displayed_index in mfdpage_fms_t::refresh_template turning to a negative value without a specific reason: [2014-08-10 15:03:37] [debug] mfdpage: refreshing joystick display (fms.status) [2014-08-10 15:03:37] [verbose] fms: we are flying to entry LFPK (1) [2014-08-10 15:03:37] [verbose] fms: current displayed entry index is -1
Added a condition, if displayed_index is negative, fms.status prints a INV_DISP error message
User Alessandro61 reporting this issue is still there with A320 Neo Jar
From Dco:
Running the plugin either on 10.25 or 10.30b6 makes X-plane crash. Running windows 8.1 and make the test with the Peter Hager A321.
I load the flight plan and suddenly x-plane crash when navigating within the pages of the X52 or when looking at the legs in the FMC