Closed malaise closed 1 month ago
Well, this seems to be fixed after starting a new flight (without restarting XP11)
So this is probably a defect in XP11
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?
Well this is quite reproducible
I close and restart LNM with no success.
And yes, I checked that XP11 was set to follow real time.
And some minutes later this is correct!
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.
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.
Thanks for the hint @malaise . I'll check if there is something going wrong over time. I'm already suspecting Marble not updating properly.
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).
I disconnect LNM from XP11 and the shading becomes correct. I reconnect it and the shading is wrong gain (as the attachment above).
I'll check this but for now I'd like to finish another task.
Attempt to fix but could never reproduce it.
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](https://github.com/albar965/littlenavmap/assets/588474/89a7b19e-5ca8-4d4f-9ccf-f197181cef52)