Hello all,
Apologies for what might be something of a daft question here, but I'm new here and to the wonderful world of flight-planning generally, so please be gentle ;)
I just used Plan-G V2.x (and also tried in V3.x) to put together an East -> West trans-Atlantic flight plan. All was good and it looked great, so I saved at as a .PLG first and then exported it as a .PLN for use direct in FSX.
When I came to review it in FSX's own clunky flight-planner, I noticed it had one of my waypoints (the NIBOG EG) intersection way out in the North Sea, rather than off the West coast of Ireland.
Now, I'm guessing that FSX's database has it in the wrong location, but doesn't Plan-G build its database from FSX in the first place? I got around this glitch by rerouting via NURSI which is in the correct location, but is there a way to fix FSX's apparent error?
Cheers, Rik.
Apologies for what might be something of a daft question here, but I'm new here and to the wonderful world of flight-planning generally, so please be gentle ;)
I just used Plan-G V2.x (and also tried in V3.x) to put together an East -> West trans-Atlantic flight plan. All was good and it looked great, so I saved at as a .PLG first and then exported it as a .PLN for use direct in FSX.
When I came to review it in FSX's own clunky flight-planner, I noticed it had one of my waypoints (the NIBOG EG) intersection way out in the North Sea, rather than off the West coast of Ireland.
Now, I'm guessing that FSX's database has it in the wrong location, but doesn't Plan-G build its database from FSX in the first place? I got around this glitch by rerouting via NURSI which is in the correct location, but is there a way to fix FSX's apparent error?
Cheers, Rik.