Bug 409784

Summary: difference in position (observation, KStars)
Product: [Applications] kstars Reporter: Bernhard Schiffner <bernhard.schiffner>
Component: generalAssignee: Jasem Mutlaq <mutlaqja>
Status: RESOLVED FIXED    
Severity: grave CC: bernhard.schiffner, luca.leombruni
Priority: NOR    
Version First Reported In: 3.3.2   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 3.3.3
Sentry Crash Report:
Attachments: "fake Jupiter?"

Description Bernhard Schiffner 2019-07-14 09:23:25 UTC 
SUMMARY
Very noticable difference in position of celestial bodies (Moon / Jupiter) between eye and KStars.

OBSERVED RESULT
On 2019-07-13 was a nice encounter of Moon and Jupiter visible. Jupiter was (guessed) 1° west and south of the moon.
I watched this 22:30 local time in Alcudia/Mallorca/Spain. At this time both of them were more or less in the meridian.

But KStars indicates Jupiter (much more) to the EAST of the moon.

I took photos & screenshots.
I'am until now not able to determine, which of them was shown in the right place by KStars.

SOFTWARE/OS VERSIONS
actual KDE Neon

Can I help with further information?

Bernhard
Comment 1 Bernhard Schiffner 2019-07-14 09:29:10 UTC 
Created attachment 121510 [details]
"fake Jupiter?"

Not the best photo but you can grasp the size of the problem ...
Comment 2 Bernhard Schiffner 2019-07-14 10:39:54 UTC 
Jupiter is shown wrong with an azimuth difference of about 6° east

2019-07-13 22:32 CEST (UTC+2) / Azimuth
Moon:
KStars: 166° 5', azimuth "measured" by photo+google.maps next day: 167° 38'
Jupiter:
KStars: 160° 19', "seen" (1 moonsize west of moon) at 166° 55'
Comment 3 Jasem Mutlaq 2019-07-15 05:50:22 UTC 
KStars language is English?
Comment 4 Bernhard Schiffner 2019-07-15 07:49:33 UTC 
(In reply to Jasem Mutlaq from comment #3)
> KStars language is English?

... German (Moon->Mond etc.)
Comment 5 Jasem Mutlaq 2019-07-15 15:46:38 UTC 
Please check KStars nightly release and see if it fixes you issue.
Comment 6 Bernhard Schiffner 2019-07-15 20:50:09 UTC 
Problem is fixed in the actual git. (tagged 3.3.3)
Thanks for this fast fix!

Out of curiosity: was it fixed by commit 1b8050f4?

Bernhard
(I own you a beer or any other drink if we meet us once.)
Comment 8 Jasem Mutlaq 2019-07-17 10:08:34 UTC 
*** Bug 409890 has been marked as a duplicate of this bug. ***