VFR Navlog

Wishlist
1

I would like to share with you an idea to implement since Navigraph now gives you the possibility of planning VFR flights.

I would like to have the possibility of having the Navlog at the end of the planning

even the possibility of drawing on the flight maps for notes

5 Likes
Navigraph Nav Log
Frequencies based on route and altitude
Cumulative flight plan distance
Show procedure constraints (Altitude, speed) directly on map
Enhanced flight planning
Print utility
2

With all the VFR possibilites now available it is a bit of a shame that a navlog function, like on Skyvector, not is implemented.

3

A Navlog would be great indeed, thanks for creating a topic! Feel free to vote for it yourself @Deltaflight84 .

Please stick to one feature request per topic! I have edited the title. In this case, your request seems to be covered by this already existing topic:

Feel free to add more details to that topic if you want to!

Kind Regards,
Malte

4

Adding my vote, a navlog is for me the last hurdle from making Charts my only planning tool for VFR piston/turboprop flying in the sim, and also for a good portion of IFR flying. Currently I still supplement it with SkyDemon and/or Skyvector, but a all-in-one with Charts would be great.

Wouldn’t even have to be too complex for my use; track true and mag, distance, level (selectable), average leg wind, leg time based on distance/TAS, and hey presto! Stuff like automatic wind correction angle/heading and GS calculation would just be a bonus, I’d be more than happy with some simple arithmetic.

2 Likes
5

VFR Planning - Altitudes - Wishlist - Navigraph

6

Casting my support for this. As a VFR IRL pilot this would greatly increase immersion.

7

I think this is a very needed feature, specially when flying in VR. I’m doing the navigraph academy course and it’s hard at times to figure out what the heading and distance are for the next leg. It is only displayed at the center of each leg, so you have to constantly be moving the map to see it. Ideally I’d have the map focused and zoomed on the next waypoint but then I can’t see the leg info.

Having a navlog showing all of the legs and their details in a succint manner would be better. If you do implement this, please also show the name and notes that we can add to each waypoint in the navlog.

What I do as a workaround in the meantime is import the flightplan into MSFS2024 or Sky4Sim, since they have their own navlogs. The problem is you lose the names and notes. I’ve used Little Navmap in the past and I know that the flightplan that it generates keeps the waypoint names once you import it into the sim, so it’s at least possible to do that.

This is the waypoint “Egg Lakes” from the course. See the waypoint info that Navigraph generates in the .pln files:

  • <ATCWaypoint id="4734N01042E">
    <ATCWaypointType>User</ATCWaypointType>
    <WorldPosition>N47° 34' 27.00",E10° 42' 52.00",+000000.00</WorldPosition>
</ATCWaypoint>

VS Little Navmap:

<ATCWaypoint id="Egg Lakes">
    <ATCWaypointType>User</ATCWaypointType>
    <WorldPosition>N47° 34' 27.00",E10° 42' 52.00",+004500.00</WorldPosition>
    <ICAO>
        <ICAOIdent>Egg Lakes</ICAOIdent>
    </ICAO>
</ATCWaypoint>

This is how the Little Navmap flightplan is shown in the builtin MSFS2024 navlog after you import it:

grafik
grafik960Ă—1323 165 KB

But it also works fine in the Sky4Sim navlog, since it also uses the flight plan .pln files.

@skysail If the dev team could release a quick fix for that in the mean time it would be great!

8

This is a current limitation in the 2024 PLN format that we cannot easily fix, unfortunately. We have it tracked internally. The 2020 format already supports names of custom waypoints - maybe that is possible to load as well?

9

I will try it today and report back, thanks!

10

I tried the 2020 pln format into MSFS2024 and it doesn’t properly load the custom waypoints, all that was imported was the airports.

I decided to check it in VSCode anyway and I don’t see the names of my custom waypoints there either (in the generated xml), so I’m a bit unsure of what you meant/if we’re talking about the same thing.

To be clear, I was asking for the names of the user waypoint names we create in the navigraph app to be included in the id attribute of the ATCWaypoint element, as well as in the value of ICAOIdent element in the exported pln file. That is how Little Navmap does it and they show up fine after importing the pln file into MSFS2024.

11

Yes, that was my understanding as well. This is what I would expect for a 2020 PLN file. Here is an example exported from the app:

ESSZESSA.pln (1.8 KB)

Please make sure that you have VFR flight rules selected as well!

12

Ah, I’ve figured it out. The user waypoints I created were for that flight only, not global. For some reason user waypoints with the flight scope do not get exported with their names (and I’ve also noticed that the ATCWaypointType element value is Intersection instead of User). This was using the 2020 pln format.

Waypoint with global scope:

<ATCWaypoint id="ELBE RIVER">
    <ATCWaypointType>User</ATCWaypointType>
    <WorldPosition>N53° 33' 17.00",E09° 40' 34.00",+000000.00</WorldPosition>
    <ICAO>
        <ICAOIdent>ELBE RIVER</ICAOIdent>
    </ICAO>
</ATCWaypoint>

Waypoint with flight scope:

<ATCWaypoint id="533050N0100227E">
    <ATCWaypointType>Intersection</ATCWaypointType>
    <WorldPosition>N53° 30' 50.00",E10° 2' 27.00",+000000.00</WorldPosition>
    <ICAO>
        <ICAOIdent>533050N0100227E</ICAOIdent>
    </ICAO>
</ATCWaypoint>

Also, with these global waypoints, it seems like MSFS2024 correctly imports the 2020 pln format, so I can work with that for the time being. I’ll write back if I run into any issues.