Well, randomness is not truely random in computers, but still it would be odd to _always_ move in the same direction. I guess an invisible protection zone can be arbitrarily defined to bound the star to it to ensure it doesn't stray too far off.
What strikes me is the factt that not only goes dithering in one and the same direction during a job. It appears to remain the same during the whole night.
Thanks, I just pushed a fix for the not-so-random dither and used different algorithm and add a bounded area. Please try the nightly build or wait for next release.
The following user(s) said Thank You: nMAC, Alfred
Backlash... could it be the cause? Even with 10 pixels movement?
My results are mixed. Sometimes it goes always in the same direction. And suddenly,then it change directions.
I have to test the new build.
Odd, indeed. But what can I say, it always moves in the same direction here as evidenced by the pictures I posted. I should have a chance to test the new build tonight. Backlash is not an issue with this mount.
Just ended tonight's session. Certainly useless to target nebulae at full moon but I wanted to test the new build. I updated nightlies just before I started the session. Here is the result of two 6-lights jobs. I don't see much improvement.
That was done using KStars bleeding 2018-06-25. Just a few minutes ago version 2018-06-26 arrived. So I assume I used one that did not provide the dither "random" fix?
commit 6e4d0c918463b34bc3dc202a1ef28432c08de4fd
Author: Jasem Mutlaq <mutlaqja@ikarustech.com>
Date: Mon Jun 2520:46:452018 +0300
Fix random dithering not being not so random, plus limit it to 25 pixels box
So it was committed Jun 25, at 20:46 +0300. Was your build built before or after that?
I just checked the builds and found that the build failed on Ubuntu 16.04, so I patched in a fix and now it builds fine. So if you're using 16.04, please update again.