Forgot to mention that I am using the latest version of SD.
Ray

If storage or memory space is an issue, logging a position at a fixed time interval isn't the most efficient procedure. It would be best to take a position reading every second and then make a determination whether to store the point or discard it based on the momentary turn rate.

So if I were flying in a straight line, SD would acquire a fix every second but, based on my straight course, decide not to store each successive point because it doesn't add any new information (a straight line only requires two points to define it unambiguously). When I am in a tight turn, SD would store every acquired point because each deviates significantly from the straight line course. You could take the current rate of turn and, based on that, decide on the momentary frequency at which you log points. Since that frequency is bound to change over a flight (it would be storing a lot of points during portions that you turn and only few points during straight and level flight) you would also have to store the acquisition time together with each point.

-- Chris.

I think this has been improved in the forthcoming 2.4.3 version. Can you check it and report back once it's been released?

Wilco

Ray

Same issue for me, with 2.4.3. The breadcrumbs on SkyDemon don't show the same detail as Google Earth (using the exported SkyDemon log). My circuits don't look very rectangular on SkyDemon, but look almost perfect (surprisingly!) on Google Earth.

Tim

Here is an overhead join for Shoreham using version 2.4.3 Plan on PC. It seems to have the same 50 pence piece quality as before.

Ray

(edited for error in version number)

50p pieces have curved edges.

Just to let you know, we've changed the code for drawing track logs so it dynamically reduces the precision of the drawn lines in line with the map scale, so you should always see the full smoothness available as you zoom in, in future versions.

Many thanks

Works much better in v2.4.5 - thanks Tim and team


Ray