While I was attempting a P3Dv4 flight from MIA-PHL today. I noticed that the distance to the next waypoint on the RCv4 screen was thousands of miles away. But according to my  PMDG CDU, It was less than a hundred miles away. I've not had this problem in the 10 years that I've been using RCv4. Has anyone else had this problem? And what's the fix for it?

Was the waypoint in question a named waypoint (5 characters) or a VOR (typically 3 characters)? Named waypoints are rarely duplicated. For example, there is only one waypoint in the entire world named “ZINGA” (just to pick a name at random). The same does not necessarily hold true for VORs or NDBS. “SAV” is the Identifier of the Savannah VOR in Georgia in the US, but there are 3 other VORs in the world with the identifier “SAV”, along with one standalone DME, and an NDB.

When an identifier appears in an FMS route that has several possible locations, the FMS often has enough processing intelligence to automatically pick the correct one (out of multiple possibilities) based on the preceding and following waypoints in the route. RC4 may not be so discerning. It may have picked the wrong one (if there is more than one).

What was the specific waypoint that caused the problem in RC4?

@Delta6295, what program did you use to generate the plan?

Make sure you keep the database updated in RC4 by running MakeRunways.exe.

16 hours ago, JRBarrett said:

Was the waypoint in question a named waypoint (5 characters) or a VOR (typically 3 characters)? Named waypoints are rarely duplicated. For example, there is only one waypoint in the entire world named “ZINGA” (just to pick a name at random). The same does not necessarily hold true for VORs or NDBS. “SAV” is the Identifier of the Savannah VOR in Georgia in the US, but there are 3 other VORs in the world with the identifier “SAV”, along with one standalone DME, and an NDB.

When an identifier appears in an FMS route that has several possible locations, the FMS often has enough processing intelligence to automatically pick the correct one (out of multiple possibilities) based on the preceding and following waypoints in the route. RC4 may not be so discerning. It may have picked the wrong one (if there is more than one).

What was the specific waypoint that caused the problem in RC4?

WOLFO RAMJT ETECK OZENA LANIE LURKS.  I looked this route up on Flight aware. On the flightplan they all show a short distance apart.

Ray, I ran MakeRunways.exe and I'm going to attempt another flight. I'll advise how it goes.

Here is another flight that I did from KPHL - KDTW. As you can see, the distances are significantly off. This flight was performed after I had run makerwys.exe

This flight plan was imported from Simbrief.

 

@Delta6295, your screenshots have not appeared. Just placeholders.