When I run Plan G V3, my PC runs very slow for a while. The task manager shows both cores fully occupued, and then everything stops working and I have to re-boot.

Nothing like this happened with the previous version, which I  thought was excellent. What has happened to casue this in V3? Can something be done about it, or should I just revert to V2 until I get a better PC. The current one is Core 2 duo at 2.4 GHz with 6 G of Ram and XP pro.

Thanks

VH-DUX

Thanks Tim,


More learning and more fun


VH-DUX

Magnificent!

Thanks Tim, this is the sort of diagnosis that keeps us enjoying our virtual flying and not getting taken off into technical labyrinths. I will pass this on the both the VATPAC forum and the scenery developer.


Merry Christmas

VH-DUX

Yesterday I nearly hit a hill called Mt Macedon, near Melbourne, Victoria, Australia.

I was using the MEF information out of Plan G by moving the mouse pointer along my flight plan line as I went, and adjusting as I needed.

That was until I found Mt Macedon looming up before me, and clearly much higher than I was, despite being 200 feet above the MEF from Plan G.

So, where do the Plan G MEF numbers come from and who decides if they are right or not. I can report that they are not right at Mt Macedon.

Otherwise a wonderful resource and one I wouldn't be without.


VH-DUX

Recently, I found myself lost near Melbourne, Victoria, Australia, because Plan G had given me a heading that appears to me to have added the magnetic variation of the area rather than subtracting it.

I put this to the VATPAC forum, and others agree with me.

The hop in question is Tooraddin to Lilydale, and Plan G advises 355 True/007 Magnetic. FSX and I hold the opinion that the Mag heading should be 342, and when I fly this it works for me.

Is this something Plan G does only in the southern hemisphere, or only in Australia? In any case, does anyone know how to fix it?

Thanks for a great tool

VH-DUX