Glad it helps. Also I don't think there's a breadcrumb trail option but although you can't create a new fix other than clicking on the map, once you have a fix you can then drag it to where you think the aircraft is by your navigation, and it will always show the new coordinates in the tooltip as you drag it. That way you get a record of your actual track. So you create flight plan A for your planned track then switch to a new flight plan B to record progress. Does that make sense?
If some of the RR positions seem miles from the real locations then it might be due to the way they were set up. Not always accurately placed. For example the RR programme's Sydney NS range is shown north of the airport but in reality was south of it.
I still have no idea why navaids would show on FS9 and FSNav but not Plan G, unless the latter needs to know the folder paths which seems unlikely.
Last Edit: Oct 18, 2019 10:47:07 GMT -5 by Defender
Yes, it does make sense, thanks, Bill. On the stray waypoints I didn't explain it clearly enough. Plan G is picking up other waypoints entirely, one was in the US mid-west, which must share some kind of code with the RR ones, which it does not show at all. Hence there are massive zig-zags in the plan, which is therefore useless. FS Navigator is simply a better program in that respect, as far as I can see, although I suppose RR is some way from being typical scenery,
Indeed looks like a deficiency in Plan G. There are certainly many navaids world wide with the same identifier and possible the same frequency but not within range of each other. The only thing which I think can displace navaids is in the AT9xxxxxx files, airways and routes, where if you or any programme move any waypoint on a route, it moves the rest of that route's waypoints. That's possibly why you don't move stock navaids.
I will have another look at RR and see what's different from a normal AFCAD based navaid.
As others may have downloaded FS Navigator from the DC-3 Airways site I will just add something about an issue I came across which I have managed to solve. The database creation tool is in the Bin folder in the FS9 Modules/FSNavigator folder. The first time I ran it there was no problem. However, having changed one or two navaids I ran it again and it crashed on the Cal Classic Asia Pacific 1962 folder. When I deselected that it crashed on the Cal Classic Core folder. I then went into the Compatibility settings for the program and set it to run under Windows XP Service Pack 3. It then worked properly. There has been debate on the net about whether this is a legal copy of FS Navigator as some say that it has never been released as freeware. There has also been a suggestion that it would expire after 20 uses and demand a registration. It does not do this, and it is an excellent program.
Postscript. I am sorry to report that it does in fact expire after 20 Flight Sim sessions and as there is now no way of buying a registration that is it. A pity.
Last Edit: Oct 29, 2019 11:45:53 GMT -5 by connieguy
In addition to the core FSNav (version 4.70) I have a collection of SIDs and STARs for Alaska and also for parts of Europe and Kenya. My internet connection is a bit dodgy and slow at the moment but by next weekend I should be able to send them off to anyone who needs them.
I also bought a registration back in the day which still works.
The issue with the database creation tool has several work-arounds which I can also share.