Wish list

[tim arnot]

I'll certainly look at that  :)

[Fenric]

Wow, Tim, you're quick too.  :laugh:

In testing out Plan-G over the weekend, I had come up with a good half-dozen feature requests - all of which have previously been asked and acknowledged in the forum here.  That one - optionally printing origin and destination airfield information - I had missed in another post.

So, I'm going to push my luck with this one....

In real-life cross country flights, I've made it a habit to "listen ahead" to airfields to gauge any activity that I might need to be aware of.  After I would plot my intended course, I would list out local tower and traffic frequencies and tune in as I approached.

For example, flying direct from EGLD/Denham to EGBE/Coventry passes very near to EGWN/Halton and then to EGBT/Turweston.  If I were making this flight, I would note their multicom frequencies and listen in on COM2.

So I was thinking for Plan-G that - similar to the bearing markers earlier - it would be helpful to drag EGLD and EGBT onto an existing flight path and have their airfield information added to the queue for printing.  (Or right-click on the airfields and add via context menu, etc.)  Not adding them to the flight plan, but as a reference while printing - a side note.

[ega]

Many thanks you for all your excellent work and dor sharing it!

A couple of suggestions:
1) A view a la FSNAV style with only the important nav data: airports, VOR, NDB and jetways. This would me most useful in flights with large aircraft.
2) If possible, please insert in the ribbon a switch that cycles between the  user aicraft display sync being free or lock. This would avoid to go to Options/FSDisplay.

Again, congratulations for this outstanding work and THANK YOU!

Regards

Edmundo

[tim arnot]

Would be nice to have Ants Australian airports as an im port as well.  Thanks for the great download on OZX fields.

The OZx download includes any of Ant's airports that are not already on the map