Michael,

One of my av/spyware detectors will warn me when I run a new build of Plan-G (or any new program) if its name/date/version/checksum/etc isn't in their "cloud-based database."  (I'm on the beta team, so I see new versions from time-to-time.)

So I take a moment to consider what I'm doing and if I feel confident enough I permit the new build to run.  Soon enough, I'm not warned about that version.

I would also guess that since Plan-G isn't "installed" as your typical Windows application - there's no Start Menu / Desktop Icon / Add/Remove Programs Entry - that SONAR may use that to judge Plan-G to be suspicious.

The preceding are just my observations and thoughts - YMMV.

Serge,

You're spot on correct!

George,

Hover your mouse over the feathers and you should see the associated ILS xmitter information in a popup - airport ICAO, frequency, ID, bearing, G/S, etc.

Hi Tony,

Have you set Plan-G's pointer to your Scenery.Cfg file?  It's under Options | Locations?

I'm a Vista 64 user and I didn't know until a few weeks ago that my correct Scenery.Cfg file is at C:\ProgramData\Microsoft\FSX.  Until then I had selected the Scenery.Cfg file in my FSX root.

HTH,

--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.

[feature request removed as it had been already asked and answered.]  ;D

Ta for the tool!

I'd like to add my voice to the growing crowd of cheers.  I've only toyed with Plan-G a few times, but it's infinitely better than the FSX planner, easy to use, and perfect for us low-n-slow flyers. 

Thanks for a wonderful application, and much success with your continued development!