arrex

No rush 🙂

I would suggest to gate the expost to an option in file->Export options .... Default ATC doesn't digest them.... at least the 1st one; so I am talking normal export .pln, not formats of addon products.... Currently i solved by not using the departure at all (PS: for landing runway, that's not a problem)

Hi, Also from the manual "The departure and arrival runways as well as the related waypoints are exported as custom waypoints (or coordinates) in some flight plan formats like MSFS PLN, X-Plane FMS and others.". What is it "MSFS PLN"? Does it refer to MSFS 2020 only or also older PLN format (FSX and P3D?). Because I noticed that export in FSX also has these waypoints added.... which gives some problem is using the default ATC system.... Is this intended or a bug? And if it is intended, what's the rationale behind? Can the export be excluded? In particolar I believe the one creating the biggest problems with ATC is the 1st one, at the runway head. That's because it's too close to the starting airport reference point. The risk is (depending where the ARP is wrt this point) that the ATC system does not detect properly the passage through this waypoint and starts to vector you soon to "go back" to the airport and pass it

Hi, probably stupid remark: why LNM still uses the nomenclature of "Victor" and "jet" routes? AFAIK, this is something limited to the FAA and already obsolete btw... the rest of the program seems more adherent to ICAO standard (see for example regulations of class D airspaces). So, shouldn't these routes be called simply "high" and "low" altitude?

I understand. From what I see the research should be limited to few regions: EI, EG, CY, RJ, P, K2, PH, P.... if that can help. Anyway, displaying all data on what it is most plausble, it's probably the best option. Currently my strategy is to enable them in the Navigraph db, entering the route in the flight plan, and later revert to FSX DB, so that they are exported as custom waypoints....

Thanks for clarification. 2 points i would like to highlight: 1. Currently the NAT is not printed if entry/exit navaids are not found. Is it possible to modify this behavior, such a way that it is displayed for the part that is found? For example, let's assume the exit point is the only missing; the NAT then get only displayed in the part that it is found and the last segment is omitted 2. I noticed that sometimes the wrong waypoints are used. For example right now the entry point of NAT_Y is ELSIR/CY the track is currently Waypoints Ident/Region: ELSIR/CY, 5050/CY, 5140/CY, 5230/CY, 5220/EI, DINIM/EI CY/ELSIR does not exist in my database and normally the track should not to be displayed (following the logic of point 1)... but LNM looks ELSIR in the whole DB and finds it in and airport in Canada (west coast) CYVP/CY, where ELSIR is a terminal waypoint... Similarly, now I have a PACOTS ending at KALNA/VI (india), even if it should end in KALNA/RJ (Japan). My scenery does not have KALNA/RJ and LNM falls back on the other KALNA it finds.... this i guess it's a bug, although not sure how easy is to correct as I am not sure how DB are used in MSFS and Xplane.

Thanks. Had the idea to switch LNM into navigraph mode, then plan a flight touching every waypoint at the entry and exit points, and then export the flight plan. It will contain all coordinates and waypoint names, from which I can easily add the code to make a BGL.... Yet i am not sure which points to include.... it looks like NAT is between Gander and Shanwick oceanic FIRS. So I would get the points at the edge of them.... but i see Santa maria and New york oceanic are also potentially part of the NAT system.... and maybe more. Plus i don't know anything of PACOTS and definitely never heard anything of AUSOTS....

Hi, I often get errors in after downloading the tracks; apparently some points are not present in the default FSX DB, which is logical (old and obsolete DB). Funny, this seems only to happen with the enter-exit points, not with the intermediate ones. My question is: is there somewhere a list of the waypoints (and their coordinates)? I would like to create an integrative scenery that adds these points for older simulator. Also how are waypoints defined in the NATS dowloads? ID and Region?

Excellent! Seems to work. Correctly separates airports navaids (both intersections and NDB) from global navaids! Thanks a lot!

maybe overwritten or forgot to "save"? Happens me a lot... aging is a bad beast for me too 😄

At least we know it's not a bug 😄

Did some tests: is this present in the 3.0.3RC1? Because to me it's not working... i.e. it's exporting without <ICAOAirport> intersections that are internally correctly recognized as belonging to an airport... (confirmed in the "information" tab)....

That's true.... but then I have to specify the route manually, which is not so straight-forward... i thought that option was to import by services like simbrief (but then you need to use the most updated airacs....)

Oh, good luck with adding the function 🙂 Good idea to select only the portion i want to assign to airways and do auto-calculation. It works indeed. A bit clumsy, but does the job. Oh, I see.... never used route description method.... do it manually is a mess and from external planners online implies to use Navigraph DB, which I am not.

That should be correct. I will test it as soon as ver. 3.0.3 arrives 😉 Note that ICAOAIRPORT is only present when the relative record is not empty (i.e. in terminal waypoint). It will work for FSX and P3D (which is basically FSX). ICAORegion should never be present in USER waypoint (i.e. the one you create), no? As these WP are not present in FS database, I am not sure what would happen to add that record is missing. Most likely nothing (FS will fall back on the coordinate). Will test it too. Thanks for all this!

Dears, just pure curiosity (no new feature request here). I noticed that if i do an autoroute, LNM will fill also the column of airways, and they get properly exported in the simulator later. Is there any trick to do it also for manually created plans? Also a curiosity: from what i noticed, they type of flightplan created (high altitude, low altitude, vor-vor or direct) seems to follow this logic: 1. IFR > ~18000 --> that flag is set to "high altitude" 2. IFR < ~18000 --> that flag is set to "low altitude" 3. VFR --> that flag is set to "direct" Did I get it correctly?

Hi Alex, from what I could check, the second inconsistency (user waypoint) does nothing. If I add the missing code, i cannot see any difference anywhere in the sim. For the first case instead, there is a small problem: in the default GPS function (ie. what it is drawn with the function "fs9gps"), the flight plan line should show also the name of the waypoint (and it's symbol). But it does not. So the line "bends" at an empty position. Probably because it doe not find the waypoint in the database and hence does not know what to show in the map. Funny it's only in the drawing in the GPS; the list of waypoints, the flight plan log in the kneeboard etc are corretly filled. I didn't try yet for terminal ndb, but I suppose the same as terminal waypoints apply. I would expect here in the kneeboard that the terminal NDB doesn't have the frequency shown. (again, untested)

Hi, i noticed two inconsistencies between a flight plan generated by the internal FSX planner and the one from LNM. The first one relates to how TERMINAL (not route) waypoints are saved, i.e. the waypoints appearing in blue and saved in airport records. That how FSX saves them: <ATCWaypoint id="D186U"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N55° 13' 54.01",E37° 59' 12.00",+000000.00</WorldPosition> <ICAO> <ICAORegion>UU</ICAORegion> <ICAOIdent>D186U</ICAOIdent> <ICAOAirport>UUDD</ICAOAirport> </ICAO> </ATCWaypoint> LNM does not export the ICAOAirport tag. Results the waypoint on loading in FSX is not linked to the database entry and it's name is not shown on the map. I guess (but i didn't actually check) that this also applies to TERMINAL NDB. Similarly in User waypoints. . That how FSX saves them: <ATCWaypoint id="IF24"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N48° 49' 15.05",E2° 36' 22.34",+000000.00</WorldPosition> <ICAO> <ICAOIdent>IF24</ICAOIdent> </ICAO> </ATCWaypoint> Again LNM does not same the "icao" part. I cannot really see a use for this case, but it's indeed inconsistent with FSX format.

Hi, I have a doubt: what is reason why MORA grid can be displayed if we enable in some form the Navigraph DB? Is there another alternative data source from it? If not, that function should probably be selectable independently on which is your DB choice, as it is anyway something strictly connected to Navigraph....

yes, no problem with it. I just wondered if i was missing some existing functions. I repeat: my message was not a feature request.

Hi Alex, checked few corrections: Navaids replacement, altitudes in airspaces and rating of airports. All works as it should for the moment! Great job!

Well.... very difficult not.... it's more difficult than a straight line, but you can easily achieve decent approximations... you just need to know the technique to do it 🙂

Dears, Just a tutorial-like curiosity (not a feature request). Is there a way insert in a plan an arc-dme? Cannot find any better way than putting a circle on the vor manually and then dragging the route on multiple points manually on this visual guide.....

BTW, the wind on noaa (and metar in general) is true, not mag. Is LNM taking this into consideration? Earlier today taking off from Sydney i was expecting a certain runway, but i was given another.... and the magdec of 13 at YSSY degrees would explain the problem....

Fs9 (in offline mode) and fsx as a testbench for bugs... No i know there is no historical weather, was wondering if you can pause downloads somehow....