I finally loaded v3.35 to give it a try on my NEQ6 Pro - four evenings in total over a couple of weeks. The short answer? I'm back on v3.27.
Here's a couple of related threads that this post would have been equally at home in:
http://www.iceinspace.com.au/forum/s...d.php?t=109561
http://www.iceinspace.com.au/forum/s...d.php?t=106489
Specifically, I noticed the same poor GoTo accuracy after 3-star alignment. Slews to the target were accurate until the final step, when the mount "jumped" off the target by around 1 degree as I watched through the Red Dot Finder. That final part of the slew was quite fast, hence me describing it as a "jump". I'm not sure what causes that.
The oddest thing about it is that the first two times I used v3.35, it seemed alright - average accuracy was a little worse than v3.27 perhaps, but not so bad. The last two times the accuracy problem became more apparent, which then caused me to look more closely hence noticing that last step "jump". The only difference between the sessions was which alignment stars I used (due to the latter two sessions being later in the evening).
I was back on v3.27 tonight for a late-evening session, but not completely without problems (and, no, I don't mean the pesky clouds that Weatherzone got completely wrong). I'd forgotten that v3.27 can be pretty sparse with its alignment star recommendations at times (v3.35 seems to have a richer database in that respect, at least that's my impression). I got 'alignment failed' after poor SynScan star selection and had to pretty much pick my own stars to get 3-star alignment success, although it got a bit better near midnight - better stars to choose from, I think. (BTW, I did around 6 3-star alignments through the session, including one complete reboot).
My summary thoughts, for what they're worth: 3-star alignment is still sensitive to which alignment stars you choose or are recommended by SynScan, so at some times (of the year/evening) star selection may be poor leading to poor GoTo accuracy or 'alignment failed'. SynScan v3.35, while not immune to star selection and general accuracy issues arising, seems to have a better database and/or star selection algortithm (I think), but has that bug of jumping off the target, which makes things worse overall.
I noticed that the database loaded with SynScan v3.35 is 3.28, while the database loaded with SunScan v3.27 is 3.27. This begs the question, what is the database loaded with SynScan v3.28? Maybe it's worth using that version purely for the updated database?
