Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sun shading seems to be later than reality #1125

Closed
malaise opened this issue Apr 27, 2024 · 11 comments
Closed

Sun shading seems to be later than reality #1125

malaise opened this issue Apr 27, 2024 · 11 comments
Assignees
Labels
Milestone

Comments

@malaise
Copy link

malaise commented Apr 27, 2024

LNM is connected to XP11, which is in real time.
It is 18:15 local time CEST and 16:15 GMT, so we are far from the sunset.
Still, LNM shows that we are in the night.
Night

@malaise
Copy link
Author

malaise commented Apr 27, 2024

Well, this seems to be fixed after starting a new flight (without restarting XP11)
So this is probably a defect in XP11
NightOk

@albar965
Copy link
Owner

I'll check but I've not seen a problem so far.

LNM will use current UTC but switch to simulator date and time as soon as it is connected and aircraft is loaded. Maybe this was the issue?

@malaise
Copy link
Author

malaise commented May 1, 2024

Well this is quite reproducible
Night1
I close and restart LNM with no success.
And yes, I checked that XP11 was set to follow real time.

@malaise
Copy link
Author

malaise commented May 1, 2024

And some minutes later this is correct!
NightOk

@albar965
Copy link
Owner

albar965 commented May 1, 2024

Still cannot reproduce it, sry.

Starting LNM with View -> Sun Shading Time -> Simulator time. Shading is correct.
Start X-Plane with real time tracking and LNM connects. Shading does not change and is still correct.

I'll keep an eye on it.

@albar965 albar965 self-assigned this May 1, 2024
@albar965 albar965 added the bug label May 1, 2024
@albar965 albar965 added this to the Release 3.0.7 milestone May 1, 2024
@malaise
Copy link
Author

malaise commented May 2, 2024

Me too.
For the general scenario: I can clarify that I start LNM and then XP11 in the morning, I don't stop them, and I observe the problem in the evening.
I will try to identify if the lag is present at the beginning of if it develops progressively.

@albar965
Copy link
Owner

albar965 commented May 2, 2024

Thanks for the hint @malaise . I'll check if there is something going wrong over time. I'm already suspecting Marble not updating properly.

@malaise
Copy link
Author

malaise commented May 5, 2024

This evening the problem occurred again (despite I restarted XP11 at noon).
LNM shading was approx 2-3 hours later that expected. Unfortunately I didn't capture the issue.
But I restarted LNM and the shift was even worth, approx 6hours (capture attached).
Restart

@malaise
Copy link
Author

malaise commented May 5, 2024

I disconnect LNM from XP11 and the shading becomes correct.
I reconnect it and the shading is wrong gain (as the attachment above).

@albar965
Copy link
Owner

albar965 commented May 5, 2024

I'll check this but for now I'd like to finish another task.

@albar965
Copy link
Owner

Attempt to fix but could never reproduce it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants