As in the title.
Are they just Asobo make-believe or what?
…and what purpose do they serve?
Thanks for any explanation.
2 Likes
Someone created a smiliar topic.
Pretty much. Somehow their GPS does some unsolicited interpolation of the flight path and I think it also relates to waypoints being in a procedure that are not in the MSFS database, creating the need for a “USER” waypoint.
Can’t find the thread, but maybe you can with some searching.
1 Like
Basically, Asobo do some some unrealistic manipulation of the flight plan. Call it creative license. Untill they realise it’s completely wrong, and fix it, there’s not much you can do.
2 Likes
I looked but no real info. Thanks for commenting though.
1 Like
Thanks. I thought as much but it’s always good to know that others have a similar opinion.
2 Likes
Thanks for that.
Appreciated
Workaround:
TL;DR: it’s basically entering the transition/IAF as the next waypoint of your flightplan and input the approach afterwards into the approach menu.
2 Likes
To me, it looks like Asobo has added the User waypoints in order to create a smoother flight path…especially in the A320.
Yeah, seems that way. Pity it’s completely unrealistic, and if AP lateral nav control was up to scratch, probably not needed either.
2 Likes
It’s a pity the database doesn’t follow the real approach plates. I thought the whole point, as sold anyway, was that the flight plans should do just that with Navblu providing regular updates.
Thanks. I do that sometimes and it does generally work but real aircraft don’t work that way. Still, there you go.
1 Like
IIRC, there was a post on FBW’s Discord that in order for that to work correctly, the whole AP code would have to be re-written on their side if Asobo doesn’t find a fix (which might also include re-writing the AP).
I expect this to be a workaround for quite a while.
1 Like
Asobo does a lot of strange things and what this is is a malfunction in the flight planning, what is happening is it’s a gap between waypoints and it doesn’t know how to tell you there is a discontinuity.
Normally it should say “DISCONTINUITY” on the screen of the computer but instead it’s this gay USR waypoint, LOL
Another Asobo bug is what it is…
i haven’t tried it yet but if you treat it like a discontinuity and enter the waypoint name before it or after it, it probably will get rid of it, not 100% sure on this i have not tried it, but if that don’t work then you need to wait for Asobo to fix it, and who knows how long that will take…
just another defect in the software as usual…
It doesn’t surprise me.
Fortunately, this has been fixed on the FBW A320 MCDU by the FBW team.
I don’t think Microsobo will ever fix IFR problems in their stock planes because apparently most people fly ‘low and slow’ or VFR. Its not worth the resource commitment.
Microsobo can’t even get the AI traffic to vacate the runway in time to avoid go-arounds. They have though at least acknowledged that there is a problem with AI traffic.
I think USER is the point where you were when you entered the approach into the flight plan. By the time you’ve finished, you’ve moved, so the plane turns back.
I find usually that if you hit Active Pause, enter the approach, then un-pause, the sim sees you’re still at USER, which is what it expects, and carries on normally.
Another way I’ve found is to press DIR and choose the transition point from the list before the plane turns. I use Active Pause if I get into a fumble.
I haven’t seen the video linked by @judgedrebb, for all I know it may say the same thing. I’ll check it out later.
1 Like
Unfortunately, this has NOT been fixed not sure what aircraft your using of if that has anything to do with it, however i fly the 787-10 and the Cessna Longitude, and this USR waypoint problem still exist…
It is totally annoying and you can’t delete it while your in flight or before for that matter…
Most of the time it happens on approach or just before it, so what i do is delete the flight plan and then Create a direct to (Airport) and select my runway and then activate ILS approach to get my ILS.
This is the only way, and when you got bad visibility, and can’t even see the runway or airport until your 500 feet this is annoying.
They need to fix this stupid BUG, this is a big deal, and ruins your flight experience…
Even if you use a 3rd party flight planning and load it in the MSFS 2020 system it still creates this USR waypoint, this is totally messed up, this didn’t exist before and of course when they updated the simulator for something else it cause this problem what ever they did.
As i always said when ever they go to fix a BUG, they create another one that didn’t exist before.
It’s like working with a lemon software fix one part another part falls apart.
Donny
I’m referring to the FBW A320 exp version.
My comments do not refer to the stock FS2020 aircraft.
Unfortunate for Xbox users.
Oh i see, well i’m PC user not Xbox lol
Donny
One reason for the USR waypoint is when a change is made to fly DIRECT-TO someplace else, the FMS has to figure out how to get to where you want to go. It it can only create and display the updated flight plan starting from where the aircraft is now. How can the current position be added into the FMS? It creates a waypoint and calls it USR. If it couldn’t create the USR waypoint, it would only be able to create a new flight path from some other waypoint which really isn’t DIRECT-TO.
Another use is for identifying landmarks that aren’t in an FMS or there is a character limitation. For example, the “Statue of Liberty” isn’t in the navigation database. But users want to fly to it or fly around it. MSFS has graciously added a lot of POIs into its navigation database. When a pilot adds the “Statue of Liberty” to the flight plan, it is entered into a FMS as a POI with latitude and longitude information. If the FMS doesn’t have “Statue of Liberty” in its navigation database, it does have the latitude and longitude information. So it adds the POI as USR figuring the pilot wants to go there.
Not having the USR capability would cripple the GPS.