Import Flight Plan from ATC Disable
-
Can we have an option to disable auto-import of the flight plan from ATC? Even if I only used "SEND TO ATC" (for MSFS ATC use), it still tries to auto-import the flight plan. The feature does not work currently, and when it fails, you’re only presented the option to delete your current flight plan (which was manually inputted). In addition, upon import failure, both CDUs are also disabled with error "X-SIDE USE-NO ACCESS".
The work-around I found was to power cycle the pilot and co-pilot avionics to get the CDUs working again. However, at random intervals (seems to be related to ATC handoffs) it will try to auto-import the flight plan, causing the CDUs to fail again.
In retrospect, I feel flight plan imports should always be a “pull” feature, never a “push”.
-
I would like to have this option as well. The current implementation is just not working well. It made flying IFR impossible as ATC will take over the flight plan and cause really strange issues. Like selecting a waypoint and then delete will delete the next one instead of the current one. Also add waypoint after do not work properly. If you dont use EFB send to ATC or request IFR from ATC it still works well. And to be honest I was happy without the import featrue anyways....
-
Can we have an option to disable auto-import of the flight plan from ATC? Even if I only used "SEND TO ATC" (for MSFS ATC use), it still tries to auto-import the flight plan. The feature does not work currently, and when it fails, you’re only presented the option to delete your current flight plan (which was manually inputted). In addition, upon import failure, both CDUs are also disabled with error "X-SIDE USE-NO ACCESS".
The work-around I found was to power cycle the pilot and co-pilot avionics to get the CDUs working again. However, at random intervals (seems to be related to ATC handoffs) it will try to auto-import the flight plan, causing the CDUs to fail again.
In retrospect, I feel flight plan imports should always be a “pull” feature, never a “push”.
@intjmastermind what's your method to power cycle the CDUs? I thought I tried this and it didn't fix the broken CDUs for me, I'm curious what you did exactly. Not sure if two fuses had to be off at the same time or what.
-
@intjmastermind what's your method to power cycle the CDUs? I thought I tried this and it didn't fix the broken CDUs for me, I'm curious what you did exactly. Not sure if two fuses had to be off at the same time or what.
@Marionettework I turned off the pilot and copilot avionics from the bank of four switches on the center pedestal, and turned them back on.
-
The simple answer is: I wish I could disable it. This is caused by the fact that the flight planning and ATC system are linked in MSFS. In other words, the originally recommended code library for flight planning “shares space” with the ATC system. Any change to the flight plan is a change to the ATC flight plan, and vice versa. Although you may not have seen the “importing flight plan” message before v1.2, it was still occurring in the background, and had a high probability of corrupting the flight plan.
In theory, there is no reason why we cannot get the flight plan import system to work correctly. I have included enough debugging information that we should be able to troubleshoot any problems. Unfortunately, there are just a lot of edge-cases. If you’re willing to work with me, let’s start with the “X-SIDE USE” problem. I’ve never seen that behavior before while testing the import system, and I’m not sure what would cause it. Does anyone have any screenshots of what this looks like when the import “fails”?
-
