Duplicate waypoints broken with G3000 in latest update?

I’m unable to properly select a duplicate waypoint with the G3000 (TBM930) ever since the Dec 22nd update. I’ve confirmed this problem reproduces without the WorkingTitle mod installed.

To reproduce:

  1. Set up a flight from KRNM to KCNO in the world map
  2. Bring up the flight plan in the MFD and add an enroute waypoint
  3. Enter OCN for the waypoint name. Notice how the MFD warns duplicates are found
  4. Hit enter

Result: An empty waypoint is added to the flight plan

Expected result: The screen to disambiguate the waypoint

Is anyone else seeing this? It completely breaks being able to enter waypoints :frowning: I’ve tried this multiple times with different flight plans and waypoints and it happens every time.

Same for me. With the latest G3000 update it still happens. Blank waypoint shows up on PFD screen and plane follows the route but it is not shown on MFD.

I think we need to wait another update from Working Title group.

Kind regards.

1 Like

Hi guys,
I guess, this is more a data issue then a G3000 issue. I have tested the same with our data (Navigraph) and here it works as expected:

Enter OC - “duplicates found” - which is correct because there are a lot of OC* waypoints:
image

… when I enter N the “duplicates found” removed and I see the OCN waypoint in the flightplan:
image

image

But what I have also figured out, that the “duplicates found” message will not removed everytime when the unique waypoint is found, but thats cosmetic I guess. The important part, to add this waypoint in the flightplan works here

Using AIRAC 2013 revision 7, sim 1.12.13.0 and the default TBM930 (G3000) - no mod installed.

Cheers,
Richard

1 Like

Richard, does it reproduce for you without the Navigraph data installed?

I don’t believe this has anything to do with Working Title’s mod. I can reproduce this with and without it installed.

1 Like

Good catch, then I feel really sorry about this because if it’s an ASOBO side nav data problem we need to wait MORE I guess.

Question to you : Does correct route shows up on navigation display with Navigraph AIRAC data ?

Kind regards.

I canceled my subscription to Navigraph, I’m not sure if their data is still available/present for FS2020 after cancelation. I think it is and I have it installed, but still had the issue. I’ll confirm later today.

I gave this a try with a renewed annual Navigraph data subscription and 2013 rev 7 installed:

I set up a route from KRNM to KCNO in the world map. Then I brought up the FMS (note that this time I do have the WorkingTitle mod installed but this reproduces either way):

Then hit Add Enroute Waypoint and enter “OCN”:

After hitting “Enter” this is what I see:

The navigation route on the MFD isn’t correct, it does not include OCN as a waypoint:

I then tried to add the remaining waypoints t for the SANP19 TEC route, “DANAH”, “POXKU” and “PDZ” and they did add properly:

I also tried just typing in “OC” to see what happened and that actually correctly brings up the disambiguation screen and I could pick one and add it properly.

So this really does seem like it’s a waypoint data issue not a G3000 issue and I’m just unlucky and have found multiple waypoints that don’t show up correctly. What I can’t figure out is why you were able to enter OCN properly @NAVData :frowning: Is there some way I can verify in the data I have that the waypoint is correct?

1 Like

Hi @missamo … you have posted the AIRAC version, thanks. May I ask which client beta version do you use? Beta version 19?
Cheers
Richard

PS: will try your examples later and will come back to you here

I had version 15, but tried again just now with 19 and no luck.

… and you have removed the cycle first, then you have updated your client and then you have installed the cycle again. Is this correc? Can you confirm this recommanded steps?

When yes, please can you upload your content.xml file?

Cheers,
Richard

Hi again @missamo
I have tried it now, but the same result - it´s working with the default data also (removed our data before). So my assumption is not correct sorry. Possible a scenery, which results in this issue?
image

Cheers,
Richard

1 Like

Yes, that’s how I did it. I followed the upgrade instructions from the beta forum. Uninstall the data, uninstall the old client, install the new client, install the new data.

Where do I find the content.xml file?

It’s not just this waypoint and I have no custom scenery in the area. It’s other waypoints too that have this problem.

Airac 2014, already tried to remove navigraph database, with default it’s working correctly.

Same problem for me, G3000 mod from working-title Capture.PNG

Ok, I am not crazy. Same issue still there after the 1/8/2020 MSFS update. Thats not so great. Makes it impossible to fly on pilotedge

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.