flybywiresim / aircraft

The A32NX & A380X Project are community driven open source projects to create free Airbus aircraft in Microsoft Flight Simulator that are as close to reality as possible.
https://flybywiresim.com
GNU General Public License v3.0
4.98k stars 1.04k forks source link

No Flight Plan in MCDU after completing INIT-A #7432

Closed Sankalp1465 closed 6 months ago

Sankalp1465 commented 2 years ago

Aircraft Version

Experimental

Build info

{
    "built": "2022-08-21T10:27:14+00:00",
    "ref": "refs/heads/experimental",
    "sha": "35db0fc99a5eb234223c82e3e3a71f185b86f80a",
    "actor": "2hwk",
    "event_name": "manual",
    "pretty_release_name": "experimental:35db0fc9"
}

Describe the bug

I was flying from VIDP TO RJAA (I know this one is out of aircraft range but the bug happens me with me in every flight) and had not set any destination in MSFS I turned on batteries and external power Imported simbrief briefing in FlyPad refueled the aircraft and got to the MCDU configuration and completed INIT-A but no Flight Plan was there in F-PLN section. This happens with me just in A32NX not in default A320 neo.

Expected behavior

To get the Flight Plan in F-PLN section of MCDU

Steps to reproduce

  1. Go to simbrief and create a flight plan from VIDP to RJAA and use runway 29 for takeoff and RJTT as alternate.
  2. Open MSFS don't set an arrival just choose gate 224 of VIDP.
  3. Follow the procedures and get into MCDU Configuration.
  4. Complete INIT-A.
  5. When you will check the F-PLN it will be blank

References (optional)

Screenshot 2022-08-22 174723 Screenshot 2022-08-22 174749

Additional info (optional)

It happens with me every time no matter what airport or route it is.

Discord Username (optional)

iamsankalp1465#6570

K603AO750rus commented 2 years ago

Hello! I have this problem! I can't think of a solution. Tell me how you managed to cope with it?

tracernz commented 2 years ago

Firstly, only the latest version of MSFS is supported at any given time... using older versions by some means will cause this kind of breakage due to API incompatibility.

If this is not the issue, the best thing to do is check in the debugger if you're able... firstly I think you need to enable dev mode in the MSFS settings, recreate the fault, then open Chrome (other web browsers may not work), and navigate to http://127.0.0.1:19999... Click VCockpit08 - A320_Neo_CDU [coui://html_UI/Pages/VCockpit/Core/VCockpit.html], click the "console" tab and check for red errors, ignoring 404s.

MubasheerSidd commented 2 years ago

I'm having the same Issue with headwind a330

archer884 commented 2 years ago

So, I'm flying the latest version of the game and the latest version of the plane, and I just had what seems to me like the same issue. When I followed the instructions above, it mentions an "unhandled promise rejection." "Cannot access uninitialized variable."

Line 422 in waypoint.js

image

Update: I downloaded the plane via the installer (although I am on the dev branch now) and this works fine.

juliansebline commented 1 year ago

Up on this

Alphazor007 commented 1 year ago

Firstly, only the latest version of MSFS is supported at any given time... using older versions by some means will cause this kind of breakage due to API incompatibility.

If this is not the issue, the best thing to do is check in the debugger if you're able... firstly I think you need to enable dev mode in the MSFS settings, recreate the fault, then open Chrome (other web browsers may not work), and navigate to http://127.0.0.1:19999... Click VCockpit08 - A320_Neo_CDU [coui://html_UI/Pages/VCockpit/Core/VCockpit.html], click the "console" tab and check for red errors, ignoring 404s.

This id the error that i am getting from the Debugger

image

Do you have any solution for this?

Benjozork commented 1 year ago

Firstly, only the latest version of MSFS is supported at any given time... using older versions by some means will cause this kind of breakage due to API incompatibility. If this is not the issue, the best thing to do is check in the debugger if you're able... firstly I think you need to enable dev mode in the MSFS settings, recreate the fault, then open Chrome (other web browsers may not work), and navigate to http://127.0.0.1:19999... Click VCockpit08 - A320_Neo_CDU [coui://html_UI/Pages/VCockpit/Core/VCockpit.html], click the "console" tab and check for red errors, ignoring 404s.

This id the error that i am getting from the Debugger

image

Do you have any solution for this?

This is a simbridge error unrelated to this ticket. Please clearly state which issue you're having, and provide the version of your simulator and aircraft.

Maximilian-Reuter commented 6 months ago

this seems to be stale