Tried to plan a flight, MYNN to KMCO with "ZQA BR65V ZFP BR62V VRB BAIRN2" taken from FlightAware. Everything is set up and looks okay on the map (I'm now using cycle 1101 and have rebuilt the databases again), I click on the build button, FSBuild gives the exported to message, GateKeeper starts up fine, but I see the following:
All coordinates between airports are N0 E0. I tried to reproduce, but couldn't at first. Quickly figured it out, it works fine without "Build from Route waypoint Table/Grid" checked. But check it and you'll get the capture problem. I've always used that setting, because I regularly delete waypoints from the grid that are too close to the departure airport for example (I use the default ATC).
Edit: I'm about to get underway (with a good flightplan, so build without the above option) and the PMDG 737 FMC says the first waypoint (ZQA) is 7462 NM away?! Is that to N0 E0? Even though it is the Nassau VOR/DME. Could there be a glitch in the Navdata that's causing this?
Edit: in the FMC I deleted ZQA and put PEACH on top, the second waypoint. The FMC says that is 7448 NM away and complains about insufficient fuel, LOL! I've checked the .rte file and it looks okay to the untrained eye (though it does say "Generated by Fsbuild 2.3
Last edit: switched to the QW757, loaded the flightplan, no problems and unusual distances. Showed fine on the default GPS receiver as well both times by the way. So I'm thinking there are two unrelated bugs? One with the "Build from Route waypoint Table/Grid" option and one with the PMDG .rte file.
I'm having the exact same problem as that picture depicts. I have the most current version (2418). I tried indexing and the problem remained. I can't really re-install because I purchased fsbuild years ago and now I have no clue where the original install files are. Is there something I can do to get rid of this problem??
EDIT- Also another problem I'm having is that when I try to insert a new waypoint in the flight plan, it inserts it directly after the departing airport, and the coordinates for that waypoint are all zero'd out. I'm really not sure why it would be doing this or what I can do to fix it.