I've uploaded your screenshots as attachments to this bug.
This is probably related to bug #834737, or at least to my observation in the comments of the bug report: https://bugs.launchpad.net/stellarium/+bug/834737
The original issue with Laomedeia may be caused by using an osculating orbit instead of proper elements.
Anyway, to reproduce this bug:
1. Turn on orbits.
2. Zoom in on a planet that has moon orbits enabled _without selecting the planet_ (because that will show only its orbit).
3. Either change the date/time or increase time speed.
I think that the bug will be evident even without changing the time - if Stellarium runs long enough for the satellites or the parent planet to significantly change position. Someone should let Stellarium run for a few hours with orbits enabled. :)
I think that this is a problem with Stellarium's orbit rendering code. It was simply not made with planetary satellites in mind. Enabling orbits for every possible satellite was a hasty move.
I've uploaded your screenshots as attachments to this bug.
This is probably related to bug #834737, or at least to my observation in the comments of the bug report: /bugs.launchpad .net/stellarium /+bug/834737
https:/
The original issue with Laomedeia may be caused by using an osculating orbit instead of proper elements.
Anyway, to reproduce this bug:
1. Turn on orbits.
2. Zoom in on a planet that has moon orbits enabled _without selecting the planet_ (because that will show only its orbit).
3. Either change the date/time or increase time speed.
I think that the bug will be evident even without changing the time - if Stellarium runs long enough for the satellites or the parent planet to significantly change position. Someone should let Stellarium run for a few hours with orbits enabled. :)
I think that this is a problem with Stellarium's orbit rendering code. It was simply not made with planetary satellites in mind. Enabling orbits for every possible satellite was a hasty move.