As the title says, I have not found a good explenation, maybe somebody can point me to that link?
I keep getting “USER” waypoints on the A320 and GA planes when I activate approach.
1 Like
A USER waypoint is a freely defined, self-created waypoint with GPS data, which is not included in official maps.
Such USER waypoint can be created during all phases of a flight, if required.
Normally, however, this is not needed during an approach.
3 Likes
OK, so when the G1000 automatically creates these waypoints during approach is that normal? Because I have not created any “USER” waypoints my self.
Same here…thanks for asking. They getting added on the TBM all the time and always seem to make flights longer. At first, I thought the purpose was to smooth out sharp / hairpin turns but now I have no idea.
Well, user points are a real thing, but the way Asobo uses them is NOT. They have these weird approaches using imaginary curved lines sometimes connected via user waypoints that don’t exist in real life.
Ok because I know how to use a real G1000, and used to create my own waypoints for various reasons but the problem here is that they are not limited to Garmin models, even the MCDU and FMC creates “USER” waypoints…
Ok let’s see when that gets fixed…
1 Like
Any time there is an error/name conflict/conflict with a waypoint that comes from user input, so also all ‘arrivals’ and ILS/RNAV aproaches, because of the discrepancies between MSFS data, navigraph updates and mods, and what MSFS then does not know what to display as waypoint name, it will revert to the coordinates only and designates the waypoint ‘user’. And this apart from actual ‘user’ waypoints.
1 Like
See this post and video that may help
Matt from Working Title here.
Waypoints with the label USR or USER are generally non-ICAO leg terminations generated by the stock sim flight plan system. In other words, in nav data, procedure legs are very often described in relative terms: fly course 245 until 6NM from OBK, for example. The ends of these legs (the terminators) are not specific ICAO nav points, and thus don’t have a predetermined name in the nav data. It is up to the GPS/FMS to name these.
Right now, the sim flight plan system names these relative or non-precision non-ICAO fixes with the label USR or USER, which is not correct. Generally units follow the ARINC 424 standard for naming conventions of these (although not always, for example, heading/course to altitude fixes get a name like (1200) on the ProLine 21). Additionally, the stock flight plan system drops or miscalculates the terminations for a number of relative leg types, so not only do users see these strange fixes, they also see them in the wrong locations as compared to the procedure chart. This leads users to believe that the stock NavBlue navdata is junk, when actually it’s quite good, it just isn’t interpreted properly by the stock plan system.
We built our own flight plan manager outside of the sim for the WT CJ4 to avoid these issues, and as such even with stock navdata you’ll find that you’re almost always matching the chart.
-Matt
5 Likes
Matt, thank you for an eloquent explanation of this. Do you have any idea if WT team has plans to extend this system to the Garmin units outside of the ProLine 21 implementation?
User waypoints=BROKEN AUTOPILOT
One reason for spaghetti approaches I noticed when I had to compare this with a Jeppesen chart, the automated MSFS tracing incorporated half of a hold pattern in an approach pattern.
This MSFS automation is flawed, so better to use Little Nav Map to create your approach manually, don’t even use Little Nav Map inserts, trace the - expected - approach.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.