The just released Sky Dolly v0.17.5 provides an important fix for a regression introduced by Sky Dolly v0.17.1: Sky Dolly would attempt to create a network connection (using IPv4) instead of a local shared memory-based connection (via a pipe).
This would work in most cases (albeit not with optimal performance: memory-to-memory interprocess communication is more lightweight than the (local) TCP/IP stack), and hence this regression went unnoticed for quite some time (that is, it worked flawlessly on my Windows 10 setup).
But once I got detailed bug reports from community members such as Oliver J. (thank you so much!) the culprit was quickly found and fixed!
Technical details may also be found in the issue 159 that I have created based on the feedback. In the spirit of full disclosure
Meanwhile other community members share how they do flight analysis, by extracting the data from the Sky Dolly logbook (which is an SQLite database really) and processing it further.
For instance DocDressler wrote:
"I am extracting the data using Python. The plot is then done with GNUplot.
This picture shows a flown pattern with a Diamond DV 20:
The following picture is a close-up of the flare phase:
"(end translated & paraphrased quote - images shared with kind permission of the author DocDressler)
This is only possible thanks to the very structured and open Sky Dolly logbook format that can easily be queried with SQL.
And it always amazes me in what ways people are using Sky Dolly - thanks a lot for all your feedback and support!
Happy flying!