This Release doesnt working yet " SBRJ EVKO3A.NAXOP UZ45 IBDA1A SBSP "

[dunham94]

Fixed issue with dropped airway information. This affected plans that have only one leg between departure and arrival. As a result an airway was dropped on saving, exporting and using it in the flight plan route description. Example: SBRJ EVKO3A.NAXOP UZ45 IBDA1A SBSP resulted in SBRJ EVKO3A.NAXOP IBDA1A SBSP.

This Release doesnt working yet !

I just tested the new Release and it still bugs when I press Calculate. I did the following:

• I set the altitude to 27,000 FT
• I clicked on "edit route description"
• I wrote ''SBRJ SBSP"
• I created a flight plan
• I set the departure chart for SBRJ - EVKO1F.NAXOP.
• Then in SBSP, I set the Arrival to "STAR OGTA1A.IBDAL."
• I clicked on the button "show flight plan calculation window"
• I pressed calculate
• Airway still doesn't appear

I still don't know what the error could be.

[albar965]

No problems here:

And I could clearly reproduce your report before with 3.0.9.

Calculation was set to use 100 percent airways (slider to the left). Database is X-Plane 12 and cycle 2409.

I'll check if this is affected by settings or maybe OS. Can you send me an issue report? Menu Tools and then follow instructions in the dialog window. Maybe this is broken because of a certain configuration option you use.

[albar965]

Calculation:

[Eyderoe]

yep ,airway have some wrong still.
cycle :2312 ver:3.0.10rc1 setting: all navigraph
cant get a route from ZULS-RKZ ~ SUBSU-VQPR

[dunham94]

Mine try :

didnt show the Airway
Its with bug yet !

[albar965]

didnt show the Airway
Its with bug yet !

Did you check the flight plan table? It's shown as I highlighted in my screenshots. Also, the airway label on the flight plan line on the map is optional. You have to enable this first in options -> map labels.

Your flight plan in the table is also different to the first one reported. Anyway, this is working too here:

For now stick to SBRJ EVKO3A.NAXOP UZ45 IBDA1A SBSP.

Please expand the flight plan table. Important information like the airways are not visible on your screenshot. Disable unneeded information since it is too cluttered to see something.

If it still does not work: Give me the exact steps you do to reproduce the issue. Every button your click and every menu item you select. Show me a screenshot with the full flight plan table and the program window title.

[albar965]

yep ,airway have some wrong still.
cycle :2312 ver:3.0.10rc1 setting: all navigraph
cant get a route from ZULS-RKZ ~ SUBSU-VQPR

The calculation will no always give perfect results. There was a lot of tweaking going on.

[dunham94]

Dude !!
I've been racking my brain over this for hours and I can't figure it out! You'd be a lifesaver if you could make a video showing me how you do it. I've tried exactly what you told me, but it's not working.

• First, I'm not seeing the option > map label
• I'm not going to do the route directly like you did, I closed it up to LNM and nothing, I can't do it!

[dunham94]

tela-gravada_GxSOJUvQ.mp4

Take a look at the way I'm doing it, it's very strange!

[albar965]

Take a look at the way I'm doing it, it's very strange!

What is your intention? You want it to use UZ171 instead of UZ42? This won't happen because the other route is shorter and can use more airway segments.

I still cannot see the airways in your flight plan table. Are they missing or is LNM using unexpected ones?

Make sure this is set to see airway labels on the map:

Also: Why do you calculate for selected? This is not needed. Simply start the calculation and and it will calculate a plan between departure and destination without the need to select anything.

[dunham94]

tentativa_2_resized.mp4

redo as you said, adjusting the options, it still remains in the error, it does not set UZ45. It still remains in the bug

[albar965]

tentativa_2_resized.mp4
redo as you said, adjusting the options, it still remains in the error, it does not set UZ45. It still remains in the bug

Thanks for the videos.

The routing algorithm won't use UZ45 since this route is longer. Still, it uses an airway as expected.
You can partially change this by using the slider but not in this case.

I'd not consider this an error if it uses another than the expected or official airway.

[Eyderoe]

sorry I may not express clearly due to old data
I mean :
ZULS (SID to IKUBI)
to
VQPR (STAR from SUSBU)
cant create a route

[albar965]

redo as you said, adjusting the options, it still remains in the error, it does not set UZ45. It still remains in the bug

Moreover the MSFS airway system is quite a mess as it is coded in the BGL files. You'll always get better results using the Navigraph update. Sorry, I cannot fix this.

[albar965]

sorry I may not express clearly due to old data
I mean :
ZULS (SID to IKUBI)
to
VQPR (STAR from SUSBU)
cant create a route

There are no close airways between IKUBI and SUSBU. The route calculation does not use such a huge detour.

[albar965]

Gents:
If route calculation does not work your can build your plan manually. Simply enter departure, destination, waypoints and airways in the flight plan route description and create the flight plan.
This is a bit work but not too much for such small routes:

[Eyderoe]

thanks for answer
may i ask why cant create such route
due to same reason that no close airways ?

[albar965]

may i ask why cant create such route

In general you have to manually create one if the auto route does not work in such cases.
You also use an older AIRAC cycle. Maybe airways changed.

[Eyderoe]

thanks

[6639835]

No problems here: And I could clearly reproduce your report before with 3.0.9.

Calculation was set to use 100 percent airways (slider to the left). Database is X-Plane 12 and cycle 2409.

I'll check if this is affected by settings or maybe OS. Can you send me an issue report? Menu Tools and then follow instructions in the dialog window. Maybe this is broken because of a certain configuration option you use.

Why your line is like this haha, it's like translucent

[albar965]

Why your line is like this haha, it's like translucent

You can change this in LNM options: