Hello, using the dev version, on my past few flights I find that the aircraft is not loading most of my flight plan, it only loads the STAR and I have to manually enter the rest.  This is using a Simbrief flight plan.  Simbrief is linked to my FBW install.

My procedure is to load the simbrief plan in MSFS (for ATC) and then in the aircraft use the ATSU, go I to INIT, use INIT DATA REQ, then go to the INIT page enter the flight number.  All other data appears properly except most of my flight plan.  

Any thoughts on what might be going on here?  This issue would span a few dev versions.

Thanks 

I had this a week or so ago but  never found  the cause, i switched to the experimental version  importing directly from simbrief into the MCDU and no issues since.

3 hours ago, regis9 said:

Hello, using the dev version, on my past few flights I find that the aircraft is not loading most of my flight plan, it only loads the STAR and I have to manually enter the rest.  This is using a Simbrief flight plan.  Simbrief is linked to my FBW install.

My procedure is to load the simbrief plan in MSFS (for ATC) and then in the aircraft use the ATSU, go I to INIT, use INIT DATA REQ, then go to the INIT page enter the flight number.  All other data appears properly except most of my flight plan.  

Any thoughts on what might be going on here?  This issue would span a few dev versions.

Thanks 

Try this (Experimental Version) 

Set up the simbrief link with the flypad and (i think also within the MCDU) with your login information (this is done one time)

Set up your flight within simbrief as normal

Do not load the the simbrief plan in MSFS first. Just start at the gate cold and dark

After getting power to the box (MCDU) and while you're doing the alignment import the simbrief flightplan 

Do the AOC init import

Then the Weight and Balance within the AOC section & Fuel via the flypad

Then import the actual Simbrief flightplan and waypoints from the INIT A page  

See the following  for a step by step 

SimBrief Integration - FlyByWire Simulations Documentation

Once you have done the import of the actual flight plan in the INIT pages then set up and review  the Runways + the relevant SID/STAR for your flight and remove disconnects where applicable. (Note MANUAL DISCONNECTS (AKA "Expect vectors to next waypoint") cannot yet be removed as far as i can tell) 

MAKE SURE AI ASSIST FOR ATC IS TURNED OFF OR THE CLEARANCE REQUEST WILL NOT BE AVAILABLE IN THE ATC OPTIONS.

THEN request clearance from ATC in the ATC menu so your flight gets recognized by the in game ATC.. In 90% of the case ATC will Follow the flight plan no issue (Keep in mind my flights are typically within the 400-600nm range). The only thing you would have to do after that is to request your flight levels shortly after departure because Clearance will only give you an initial departure altitude. In my experience ATC will only change the arrival runway if the weather changes at your destination or in very rare occasions there is a parallel runway and that one is active. But even in the parallel runway situation you can just request your desired runway and matching approach in the atc menu if you didn't get it initially because the winds still allow it.

Ill try to find a video that outlines at least setting up the MCDU part with simbrief integration. 

 

 

 

Edited February 21, 20224 yr by Maxis

Thanks for that detailed explanation.  I'm guessing this is all related to ongoing development of the aircraft as I didn't have this issue in the development version previously then it cropped up, but I'll give the experimental version a go.

I have gotten to the point I just enter everything manually from a simbrief printout.  Most the time If I import I get multiple oddities that take just as long to fix than just entering it by hand. I do this for the CRJ and CS777.  But after a hiatus the new FBW has changed significantly over the last 3 months.  The fuel load thing really threw me.  

9 hours ago, Maxis said:

(Note MANUAL DISCONNECTS (AKA "Expect vectors to next waypoint") cannot yet be removed as far as i can tell) 

They can in the experimental version. 

@Maxis I do it the same way with a slight difference.

I also import the Flightplan in the worldmap .

Because of that, when i enter the plane the flightplan is allready there. To avoid problems with the Simbrief import, i put a random Destination into the MCDU. This way the plan in the MCDU gets cleared exept for departure and arrival.

After that done i do it like you described. This way has the Advantage that you also get the clearence to your cruise lvl from atc. Also the TOD allways is spot on. Works quite well.

Also you have to modify the flight number on the Init page. I put in only numbers, no letters. So if m flight number is EZY1234, i put only 1234.this way i don't have double csllsigns with ATC.

19 hours ago, Maxis said:

Note MANUAL DISCONNECTS (AKA "Expect vectors to next waypoint") cannot yet be removed as far as i can tell

 

10 hours ago, Bdub22 said:

They can in the experimental version. 

They can in the Development version as well. In either version, one just has to CLR the "Manual" waypoint first, then CLR the "Discontinuity" waypoint.

...jim

 

They are not intended to be removed if they are after an manual

LOWI to EHRD Setup and take off with FS2Crew (LIVE)

 

1 hour ago, JimBrown said:

 

They can in the Development version as well. In either version, one just has to CLR the "Manual" waypoint first, then CLR the "Discontinuity" waypoint.

...jim

 

You then just deleted a part of your STAR approach. Manual isn't supposed to be deleted. It is used to indicate that within the STAR ATC is supposed to vector you to the next point. So if you guys are deleting Manual in order to delete the discontinuity then yeah.. The discontinuity isn't deletable

Edited February 22, 20224 yr by Maxis

2 hours ago, Maxis said:

You then just deleted a part of your STAR approach. Manual isn't supposed to be deleted. It is used to indicate that within the STAR ATC is supposed to vector you to the next point. So if you guys are deleting Manual in order to delete the discontinuity then yeah.. The discontinuity isn't deletable

I didn't say you should. 😉 Just mentioning that the ability to delete the manual/discontinuity waypoints is there.

...jim

 

I don't load the flight plan to msfs, just use init request function at mcdu and all route loading succesfully at both dev and exp version. 

hmm i really wonder as i do exactly the same steps as in the video but then flightplan is not loading for me either....

21 hours ago, RTK1972 said:

but then flightplan is not loading for me either....

hmm, too, as I just loaded a flight OPIS-VQPR and the exp mod (as of now just minutes ago) did not import the waypoints. had to select my RNAV15 approach and now fly direct to the STAR...

EDIT do I have to correct me? Checked simbrief and it seems like there ARE just no waypoints generated along the route to Paro?

Edited February 24, 20224 yr by DAD