search

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.97k stars 1.04k forks source link

Flight Plan randomized #6091

Closed Shituation closed 2 years ago

Shituation commented 2 years ago

Aircraft Version

Stable

Build info

{
  "built": "2021-09-18T00:34:38+00:00",
  "ref": "v0.7.0",
  "sha": "e8ea73b3648d48437ca5df55e280a945fd11dab6",
  "actor": "Benjozork",
  "event_name": "manual"
}

Describe the bug

Been tired of MS embedded flight planner that didn't work too, so I made my plan with little navmap. Made a flight plan from SUMU to SABE (this is SABE approach segment): sumu to sabe navmap

Then loaded the plan on MSFS, but look at SABE approach: sumu to sabe

Then once in the plane, look at what de ND shows for flight plan:

sumu to sabe MCDU

This didn't happen with stock asobo's A320.

Expected behavior

To be able to make a flight plan and for it to be honored by the flight sim.

Steps to reproduce

  1. Use the attached .pln (flight plan) and load it into MSFS
  2. Look at the flight plan searching for inconsistencies
  3. Start the flight and check what is actually loaded on the pla (SUMU) to (SABE).zip ne

References (optional)

No response

Additional info (optional)

No response

Discord Username (optional)

No response

Benjozork commented 2 years ago

The image you showed is the VFR Map, not the ND.

Additionally, can you test this in the experimental version ?

Shituation commented 2 years ago

Its the same thing, the flight plan should be shown in the VFR map too. I made the screenshot like that because it was difficult to see the whole plan in the ND; but if you look closer you will see SABE in the ND on that screenshot and the plan being a scrambled line mess. EDIT: SABE is here because it was not that visible in the ND after all: image

Will try the experimental version and come back.

Shituation commented 2 years ago

The image you showed is the VFR Map, not the ND.

Additionally, can you test this in the experimental version ?

OK, tested with the experimental now. The bug is still there, and things got weird.

  1. Flight plan is the same (no modifications, made with little navigraph)
  2. Loaded the first time into MSFS and got this: sumu to sabe first load 3.Since this was weird I reloaded the FP once again sumu to sabe second load :
  3. On close inspection, what looked better was the same that happened before: sumu to sabe second load 2
  4. VFR shows something near to good... with a weird approach VFR almost good (weird approach) 6.Now on the plane, the ND is f*cked up again.... total mess
Benjozork commented 2 years ago

Can you send your .pln file ?

Shituation commented 2 years ago

Can you send your .pln file ?

Its attached on the OP as a ZIP

Shituation commented 2 years ago

From SABE to SUMU the result is the same. (SABE) to (SUMU).zip SABE TO SUMU ND

Kimbyeoungjang commented 2 years ago

I believe this is asobo fpm issue.

When I flight through same origin / destination airport via worldmap, every try, departure / arrival runway and type is changed randomly.

So I think there is some issue when import PLN file. I think that's why cFPM also have same issue

Shituation commented 2 years ago

I believe this is asobo fpm issue.

When I flight through same origin / destination airport via worldmap, every try, departure / arrival runway and type is changed randomly.

So I think there is some issue when import PLN file. I think that's why cFPM also have same issue

It could be... since the asobo fplanner is awful. Maybe it is as you say, MSFS is scrambling the flight plans when loading... nothing that we haven't seen in vainilla use..

tracernz commented 2 years ago

Try entering the flight plan through the MCDU rather than the MSFS planner on the experimental version, and it should be much better. Firstly the MSFS planner has limitations, and secondly loading the from the MS flight plan is slightly broken in experimental at the moment. The VFR map also won't always appear correctly due to the MSFS planner issues. The best source of truth is the ND + MCDU.

revargne commented 2 years ago

I have this issue without the MSFS planner. Tried entering the flight plan through MCDU and loading from simBrief.

The flight plan looks good until I enter the arrival. The arrival is always screwed up and I would have to fly funny loops and impossible angles.

Tested it a few hours with every version (stable/dev/experimental) but it makes no difference. At the moment I'm not able to create a usable flight plan in the fbw a320.

(In addition to that the experimental shows flight plan discontinuities where there are none)

Benjozork commented 2 years ago

I have this issue without the MSFS planner. Tried entering the flight plan through MCDU and loading from simBrief.

The flight plan looks good until I enter the arrival. The arrival is always screwed up and I would have to fly funny loops and impossible angles.

Tested it a few hours with every version (stable/dev/experimental) but it makes no difference. At the moment I'm not able to create a usable flight plan in the fbw a320.

(In addition to that the experimental shows flight plan discontinuities where there are none)

Please provide more information. Screenshots, routes, etc.

Also, I'm confused by your comment about discontinuities. What makes you say there should not be a discontinuity?

We can't help with no details at all about your issue.

revargne commented 2 years ago

Will provide some screenshots later this day. It's 12:40am here. Just the two routes I tried today: EDDH-EDDF EDDH-LSZF

For the latter one the route from simBrief is: EDDH/15 IDEKO7D IDEKO N850 NIE DCT EDEGA DCT OMOGI T721 RILAX RILAX2A LSZH/34

As soon as I enter the STAR RILAX2A the VIA AMIKI and a lot of crap waypoints are filled in. I tried to set NO VIA but this is ignored. Always AMIKI plus crap.

About the discontinuities: They appeared in the middle of a flight plan loaded from simBrief. I tried to fill the gap but in the end got something like: ... EDEGA F-PLAN DISCONTINUITY EDEGA ...

Entering the same waypoint again was my last try to fill the gap as no other attempt worked.

revargne commented 2 years ago

I've to look into the flight plan some more. It seems that only some arrivals producing a strange route.

The problem with the discontinuities is reproducdable in experimental. Same flight plan is working fine in stable and dev. When I open the last waypoint before the discontinuity it shows the correct airway to the next waypoint.

fplan .

Shituation commented 2 years ago

This is kind of funny... image

And yes.. flight plan gets random descontinuities for me too: image

Shituation commented 2 years ago

Using the new stable version 0.7.1

Flight plan loaded better now at least on the last session I played.

On the approach part, something weird happened. I was flying straight to VANAR. AP was connected, green line on target on the ND. Suddenly the green line disappeared and reappeared on a different angle. I had no mayor problems since the plane kept flying to VANAR.

(blue line was the flight plan original path) image

Shituation commented 2 years ago

Flight plan seems to be loaded better now (tried a couple of flights SUMU to SABE and vice versa), the only weird behavior that I experienced is the one from the post above and only on flights from SUMU to SABE and only on that part of the flight.

tracernz commented 2 years ago

Is this still an issue?

derl30n commented 2 years ago

Please retry with current master aka development version and re-open if still an issue.

Shituation commented 2 years ago

https://github.com/flybywiresim/a32nx/issues/7007#issue-1191028709