Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion for Improvement of IVAP Flight Plan Export #1130

Open
dunham94 opened this issue May 29, 2024 · 14 comments
Open

Suggestion for Improvement of IVAP Flight Plan Export #1130

dunham94 opened this issue May 29, 2024 · 14 comments

Comments

@dunham94
Copy link

dunham94 commented May 29, 2024

Dear Developers,

I would like to suggest an improvement to the IVAP flight plan export functionality. Currently, when exporting a flight plan with a defined route, the route is not displayed in the "Route" section of the exported file, only the departure and arrival airports are shown.

I suggest two options to solve this issue:

Automatically include the route: When exporting the flight plan to IVAP, the route defined in the flight plan is automatically included in the "Route" section of the exported file.

Create a tutorial: Create an explanatory tutorial detailing how to view the route in the exported file for IVAP, after defining it in the flight plan.

I believe that these improvements will make the tool easier to use and make it even more useful for virtual pilots.

Screenshot_1

Sincerely,
Skywolfe

@albar965
Copy link
Owner

Cannot confirm this. Route appears fully in the dialog window and the exported file.

Example of a complex test scenario with SID, STAR and user defined waypoint:

[FLIGHTPLAN]
ID=Callsign
RULES=I
FLIGHTTYPE=Flight type
NUMBER=1
ACTYPE=D228
WAKECAT=Wake
EQUIPMENT=Equipment
TRANSPONDER=Transponder
DEPICAO=KYKM
DEPTIME=0951
SPEEDTYPE=N
SPEED=0100
LEVELTYPE=F
LEVEL=220
ROUTE=WENAS7.PERTT MIVSE DCT FOGIG DCT EAT DCT 4741N12051W DCT DROGA DCT KRUZR DCT GLASR DCT TUNNL DCT 4804N12114W DCT 4805N12118W DCT 4805N12121W DCT 4807N12128W DCT 4808N12121W DCT 4807N12116W DCT 4806N12109W DCT ROZSE DCT 6S9 DCT DIABO J503 FOLDY PIGLU5.YDC
DESTICAO=CYLW
EET=0358
ALTICAO=CYYF
ALTICAO2=CZGF
OTHER=Remarks
ENDURANCE=0458
POB=99

Alex

@dunham94
Copy link
Author

dunham94 commented Aug 7, 2024

But im not seen the UW, the Airway , need to export, how can i export the AIRWAY ? ... because im flying with B737 and need UW and i cant export

@albar965
Copy link
Owner

albar965 commented Aug 7, 2024

But im not seen the UW, the Airway , need to export, how can i export the AIRWAY ? ... because im flying with B737 and need UW and i cant export

What is UW?
Airways are included. Below J541:

[FLIGHTPLAN]
ID=Callsign
RULES=I
FLIGHTTYPE=Flight type
NUMBER=1
ACTYPE=D228
WAKECAT=Wake
EQUIPMENT=Equipment
TRANSPONDER=Transponder
DEPICAO=PAJN
DEPTIME=1542
SPEEDTYPE=N
SPEED=0214
LEVELTYPE=F
LEVEL=240
ROUTE=JNU6.SSR SSR J541 YAK DCT MALAS DCT WRNGL DCT
DESTICAO=PAGK
EET=0207
ALTICAO=PAVD
ALTICAO2=
OTHER=Remarks
ENDURANCE=0307
POB=99

@dunham94
Copy link
Author

dunham94 commented Aug 7, 2024

how do i export the airway, i don't know how to set it to be recognized and exported. could you make a route for me

SBRJ - SBSP , putting the airway as you did this way ?

@albar965
Copy link
Owner

albar965 commented Aug 7, 2024

how do i export the airway, i don't know how to set it to be recognized and exported. could you make a route for me

SBRJ - SBSP , putting the airway as you did this way ?

You cannot add airways manually. Use the LNM flight plan calculation: https://www.littlenavmap.org/manuals/littlenavmap/release/latest/en/ROUTECALC.html
Add departure and destination airport. Then open the calc dialog (image), adjust settings and calculate.

Alex

@dunham94
Copy link
Author

dunham94 commented Aug 7, 2024

Sorry but I disagree, I WOULD NOT LIKE TO DO AUTOMATIC CALCULATION, I would like to export MANUAL, because this calculation is COMPLETELY WRONG, where the airway to SBRJ is UZ171 and still does not provide the airway, just said two fixed, as the assumption as you said to do.

image

@albar965
Copy link
Owner

albar965 commented Aug 7, 2024

Sorry but I disagree, I WOULD NOT LIKE TO DO AUTOMATIC CALCULATION, I would like to export MANUAL, because this calculation is COMPLETELY WRONG, where the airway to SBRJ is UZ171 and still does not provide the airway, just said two fixed, as the assumption as you said to do.

First: No need to YELL. Second: The calculation is not "COMPLETELY WRONG". This is utter BS.
Maybe you use the wrong or outdated navdata or your aircraft cannot climb fast enough to meet the airway restrictions.

@dunham94
Copy link
Author

dunham94 commented Aug 7, 2024

When I turned it up, I wasn't shouting, I was emphasizing the words.

Got it, the automatic calculation is based on the aircraft, got it, I'll try to redo it calmly, thanks for the tips!

@albar965
Copy link
Owner

albar965 commented Aug 7, 2024

Upper case is generally considered shouting. Use stars like *enphasize* instead.

@dunham94
Copy link
Author

dunham94 commented Aug 7, 2024

I'm making my flight plan like this

  • Origin
  • destination
  • right-click and go to "show departure procedures"
  • I choose the departure
  • I go to the destination airport
  • right click and go to "show arrival procedures"
  • Choose arrival

And when I put it to export, it doesn't give me the airway, I'd like to know how do I select the airway!

@dunham94
Copy link
Author

dunham94 commented Aug 7, 2024

You cannot add airways manually. Use the LNM flight plan calculation: https://www.littlenavmap.org/manuals/littlenavmap/release/latest/en/ROUTECALC.html Add departure and destination airport. Then open the calc dialog (image), adjust settings and calculate.

Alex

When you said that, I tried to do it and it still didn't give me the airfield I need, which is the UZ45, because the cards I'm going to use will be

  • EVKO3A.NAXOP and Arrive using STAR IBDA1A

Consequently, the airfield will be UZ45 and LNM didn't give it to me automatically.

@albar965
Copy link
Owner

albar965 commented Aug 7, 2024

The airway is used by the calculation but requires at least 26000 ft cruise altitude.

Below you can see that the route goes via UZ45 to IBDAL in the flight plan table.
image

But for some reason LNM drops the airway in the route description in this very special case where a STAR and a SID are connected by only one leg. Otherwise it works well.

So instead of EVKO3A.NAXOP UZ45 IBDA1A I get EVKO3A.NAXOP IBDA1A which is not right and a bug.

Yes, its wrong but not "completely wong". 😉

Thanks for reporting. I took note of this and will fix for the next update 3.0.10.

In the meantime simply add the airway manually in the export dialog. Should not happen often.

Alex

@dunham94
Copy link
Author

dunham94 commented Aug 8, 2024

LOL , I'm glad it helped you find an error , one question, how did you know that it's only possible above 26,000 ? You said at the end

" In the meantime simply add the airway manually in the export dialog. Should not happen often."

Just what I don't want LOL !
I would like an automated way, because LNM is already completely beautiful, I've been using it since the launch of MSFS, I don't even use simbrief! For me there is only this error, of not exporting the airway, otherwise it is impeccable software.


If you can also, I have a performance problem with LNM, there is too much information and even in the "low" information bar I get low performance.

CPU : RYZEN 5 5600G
GPU : RTX 3060 GALAXY
RAM : 16GB

I don't know what it could be!

@albar965
Copy link
Owner

albar965 commented Aug 8, 2024

LOL , I'm glad it helped you find an error , one question, how did you know that it's only possible above 26,000 ? You said at the end

Hover the mouse above the airway with the airway lines display enabled.
image

BTW: Here is the "normal" case with multiple legs between SID and STAR and this adds the airways and is ok:
image
I guess you rarely have to correct this manually. Anyway, I consider this a bug which will be fixed with the next release.

If you can also, I have a performance problem with LNM, there is too much information and even in the "low" information bar I get low performance.

LNM runs well on much slower computers. My development and my flying computer are stone age compared to yours. 🙃

Go to menu Map and select Normal detail. Disable all stuff you don't need in menu View. When flying I usually switch off all navaids and even airports to have only the flight plan and its related navaids visible.

Also exclude the LNM settings and database folder C:\Users\YOURUSERNAME\AppData\Roaming\ABarthel from anti-virus scanning. Maybe even the installation folder.

Alex

albar965 added a commit that referenced this issue Aug 8, 2024
This affected plans that have only one leg between departure and arrival.
As a result airway was dropped on saving, exporting and route description.
Example: `SBRJ EVKO3A.NAXOP UZ45 IBDA1A SBSP` resulted in `SBRJ EVKO3A.NAXOP IBDA1A SBSP`
#1130
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants