On reflection I was probably a bit rash in my last post however this forum doesn't seem to permit editing/deletion of posts.

There's no question that Tim has put a huge amount of effort into developing this - and is hopefully reaping the rewards as a result. I purchased Skydemon and Skyplan and have recommended it to several others including Neutron.

However I think what Neutron is pointing out, and I have to agree with, is that whilst Skydemon is undoubtedly impressive in the graphics dept, there are a number of errors, omissions and simplifications. (the mag track being one such example) which the developers don't seem to appreciate. Ive listed a few others which Ive identified. Hopefully these will be taken on board constructively and addressed accordingly.

1. Time en route doesn't seem to take into account reduced speeds whilst climbing.

2. No intelligence to work out TAS based on IAS etc.

3. Use of Scottish Info frequencies isn't always correct - especially 119.875 for lower level FIS.

4. Lack of sufficient towns in sparsely populated areas

5. Towns in totally wrong place (eg Kirkcaldy) or in water. Whats wrong, the location or the coast line ?

Magnetic track is a fairly pointless piece of information, and isn't one we've ever heard a request for in the PLOG. What instrument in particular do you have that wants to know magnetic track?

are you sure



i planed a route from Thame (near EGTB) to Long Crendon.

The Track is 000 Deg and the Heading (M) is 2 Deg.



Adding a wind 270/90 the Heading (M) is 272 Deg, which seems right to me

________________________________________________________________________
Galaxy Tab Plus 7 inch, NavsGo GO7100 as of March11

There seems to be no Mag Track printed out on the PLOGs - just True Track and a wind derived Mag Heading. As Mag Track is the primary course information used by all the aircraft nav instruments, may I ask why it has been omitted? The only way at present to derive the Mag Track is to create a PLOG with a zero wind component.





neutron