11 hours ago, Watsi said:

But you don't download a .pln file manually from SimBrief, right? You just push the REQUEST button on the INI page?

Yeah, I suppose you're right...for some reason I missed that Request button in the FMC, but will try using that now.

1 hour ago, otip84 said:

Yeah, I suppose you're right...for some reason I missed that Request button in the FMC, but will try using that now.

Here's a how to: https://docs.flybywiresim.com/fbw-a32nx/feature-guides/simbrief/

...this actually could be the reason for the crz mode problem. Our pln import kinda works, but has its issues. Direct SimBrief import via MCDU is the better way.

(and pls remember to unsync the MCDU with MSFS in the EFB settings before!!!)

Edited July 11, 20241 yr by Watsi

Hi Watsi,

 

You could well be right. I did not know of the process you describe. I have now read the relevant pages on the FBW Documentation and I must admit I find it very complicated, daunting. I will leave it to others to use. I just enjoy flying so will continue to over write the altitude in INIT, while this works 🙂

I do have a fear that in the search for realism the plane will become too difficult for the casual flyer like myself.

Thanks for your attention.

1 hour ago, Andy675 said:

I have now read the relevant pages on the FBW Documentation and I must admit I find it very complicated, daunting

A large section of that you don't really need to worry about. If you want to clear the Cruise bug you just need to do this:

1. On the EFB, follow the instructions in Watsi's link to enter in your Simbrief ID
2. Set the option to not sync the MCDU and MSFS (it may well be off my default). That makes sure the MCDU flight plan doesn't also become the MSFS flight plan.

That is all the setup you need. To import the simbrief plan:

1. On the MCDU press INIT, and then "flight plane request"

That's it. All the wind stuff etc isn't something you have to do until you get more comfortable. You are still going to have to enter in the STARS/SIDS but that is normal for any Simbrief import.

 

50 minutes ago, BrammyH said:

A large section of that you don't really need to worry about. If you want to clear the Cruise bug you just need to do this:

1. On the EFB, follow the instructions in Watsi's link to enter in your Simbrief ID
2. Set the option to not sync the MCDU and MSFS (it may well be off my default). That makes sure the MCDU flight plan doesn't also become the MSFS flight plan.

 

 

Thanks, sigh of relief .....

Just made my first flight using 'ATSU'. Total success. 

Thank you to all your replies, and those that said 'user error' you were very correct.

 

I seem to remember using this method in FSX and the Aerosoft A320, so it is a tad embarrassing!.

Thanks for making it plain and simple, @BrammyH. Our documentations have to mention all the 'ifs' and 'whens'. That looks a bit complicated in the first place, but it isn't.

Once you have set up everything, this method is actually much quicker and easier than downloading files manually from simbrief.

Edited July 11, 20241 yr by Watsi

3 hours ago, Watsi said:

Thanks for making it plain and simple, @BrammyH. Our documentations have to mention all the 'ifs' and 'whens'. That looks a bit complicated in the first place, but it isn't.

Once you have set up everything, this method is actually much quicker and easier than downloading files manually from simbrief.

Hi Watsi,

 

If using the world map to flight plan what is the correct setting in the EFB.  I still cannot get things working properly like they used to and now using the Stable version.  Would like to go back to development at some point.  Thanks

46 minutes ago, totalstu said:

Hi Watsi,

 

If using the world map to flight plan what is the correct setting in the EFB.  I still cannot get things working properly like they used to and now using the Stable version.  Would like to go back to development at some point.  Thanks

Three options:

1. You can configure the MCDU sync in the EFB to 'none'. This means the MCDU/FMS and the sim don't know anything from each other. This would also mean you have to program the MCDU by hand (flightplan, etc.)
2. You can configure the MCDU sync in the EFB to 'load only'. This means that whatever flightplan you did in the world map will be imported to the MCDU/FMS. Whatever you're doing different in the MCDU (change of flightplan for example) will NOT be ported to MFSF (ATC won't know it).
3. You can configure the MCDU sync in the EFB to 'save'. This means that whatever flightplan you did in the world map will be imported to the MCDU/FMS. And whatever change you'll do in the MCDU will be ported to MSFS.

For SimBrief pilots, I suggest to always leave this setting to 'none'. For everybody else: be aware that the transfer from MSFS flightplans to the A32NX MCDU is not fully reliable.

More about this: https://docs.flybywiresim.com/fbw-a32nx/feature-guides/flypados3/settings/#sim-options

5 hours ago, Watsi said:

Three options:

1. You can configure the MCDU sync in the EFB to 'none'. This means the MCDU/FMS and the sim don't know anything from each other. This would also mean you have to program the MCDU by hand (flightplan, etc.)
2. You can configure the MCDU sync in the EFB to 'load only'. This means that whatever flightplan you did in the world map will be imported to the MCDU/FMS. Whatever you're doing different in the MCDU (change of flightplan for example) will NOT be ported to MFSF (ATC won't know it).
3. You can configure the MCDU sync in the EFB to 'save'. This means that whatever flightplan you did in the world map will be imported to the MCDU/FMS. And whatever change you'll do in the MCDU will be ported to MSFS.

For SimBrief pilots, I suggest to always leave this setting to 'none'. For everybody else: be aware that the transfer from MSFS flightplans to the A32NX MCDU is not fully reliable.

More about this: https://docs.flybywiresim.com/fbw-a32nx/feature-guides/flypados3/settings/#sim-options

Hi Watsi,

 

Thanks for that.  I do have an issue i alluded to earlier like on page 2.  Maybe i should create a new post rather than add to this but I've already posted about it here.  I have the EFB set to 'Load Only'.  I use the world map to create the flight plan.  Once the aircraft is powered on and i check the the flight plan in the FMS it does not show departing runway, T/C, T/D, arriving runway, etc.  This only happens using development.  Stable works properly.  Dev used to work properly up until like June 24 when I think some update occurred and changed things.  I've tried with an empty community folder but still same. Here are some pics, but not as many as my last post with pics.  

Flight Plan:

FLT in FMS:

If i scroll through the above you will not see altitude levels, T/C. T/D, etc. 

Here is the same plan from Stable:

And scrolling through you see altitude levels, T/C, T/D, etc.

 

Any thoughts as to what may be going on?

Thanks as always.

Well as said, pln / world map import into the A32NX FMS has its issues. Even more since we implemented FMS V2 a few weeks ago.

World map pln import isn't a high priority on our side, as it is a 'pain in the word_not_allowed' to implement it correctly. We may also decide one day to completely giving up this feature and remove the MSFS < > MCDU synchronization. Right now, I can't tell when or if these issues are going to be fixed.
I would suggest to get familiar with more sophisticated flight planning tools like SimBrief (which is for free), if you want to fly the dev version. Or you have to fill in all the data by hand into the MCDU for the time being.

Edited July 12, 20241 yr by Watsi

3 hours ago, Watsi said:

Well as said, pln / world map import into the A32NX FMS has its issues. Even more since we implemented FMS V2 a few weeks ago.

World map pln import isn't a high priority on our side, as it is a 'pain in the word_not_allowed' to implement it correctly. We may also decide one day to completely giving up this feature and remove the MSFS < > MCDU synchronization. Right now, I can't tell when or if these issues are going to be fixed.
I would suggest to get familiar with more sophisticated flight planning tools like SimBrief (which is for free), if you want to fly the dev version. Or you have to fill in all the data by hand into the MCDU for the time being.

OK, I created the plan in Simbrief and imported. EFB at 'Load Only'. I then added departing runaway and sid, arriving runway and star.  This is what i see in the Flt Plan.

So basically no altitudes but for 8000 at SEGOD and no T/C and T/D.  What am I missing and/or what did I do incorrectly?

Thanks

46 minutes ago, totalstu said:

EFB at 'Load Only'.

If you are using SimBrief for starters you want the EFB set to "save" and not "load". Load is trying to take the World Map flight plan.

With Simbrief import "none" is the only setting!!

Cause "Save" is also load.

Load  = one way: MSFS > MCDU

Save = two ways: MSFS < > MCDU

None = MSFS |nothing|  MCDU

56 minutes ago, BrammyH said:

If you are using SimBrief for starters you want the EFB set to "save" and not "load". Load is trying to take the World Map flight plan.

I changed it to 'Save' and then imported and same issue.  Hmm.......  Here is what i see:

So still no Altitude levels, etc.

Edited July 12, 20241 yr by totalstu