#30 X-plane crashing after loading a FP

[Anonymous]

Originally created by: user2684

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

[Anonymous]

Originally posted by: user2684

• Does it crash everytime you load that flight plan or just the last time you run it?
  Yes it crashes every time I load that flight plan,
• Does it crash when pressing a button or just after loading the plan?
  It crashes when I try some action after loading the FP. Twice it crashes when I opened the legs page at the aircraft FMC. It crashes also when after loading the FP I try to change the page at the X52 device. For me it occurs as soon an action is required

[Anonymous]

Originally posted by: user2684

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)

[Anonymous]

Originally posted by: user2684

Made some progress by generating a map file for tracking the crash and disabling optimization. The issue needs to be replicated

[Anonymous]

Originally posted by: user2684

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

[Anonymous]

Ticket changed by: user2684

• status: open --> closed

[Anonymous]

Originally posted by: user2684

Added a condition, if displayed_index is negative, fms.status prints a INV_DISP error message

[Anonymous]

Ticket changed by: user2684

• status: closed --> open

[Anonymous]

Originally posted by: user2684

User Alessandro61 reporting this issue is still there with A320 Neo Jar