Splitting out this issue from https://sourceforge.net/p/flightgear/codetickets/2499/ because they are not related.
Local time does not show up with MiG-15bis or Tu-144D:
https://sourceforge.net/p/flightgear/codetickets/_discuss/thread/c6e45671ef/2fa4/attachment/210110-125105.jpg
But is working with UFO and c172p:
https://sourceforge.net/p/flightgear/codetickets/_discuss/thread/c6e45671ef/215c/attachment/210110-125544.jpg
It turned out that this does not depend on locale or launcher.
Diff:
I found the cause: time dialog uses generic clock instrument
/instrumentation/clock/local-short-stringThe fix would be to use some property that does not use aircraft-dependent code and not rely on instruments.
Last edit: Anonymous 2021-01-12
+1 it should use /sim/time, as aircraft can override the instrumentation section to disable the clock.
The problem is that there is only
/sim/time/gmt-stringbut no/sim/time/local-stringI don't think I've fully understood what is going on here: the time arguments the launcher sets are:
--start-date-gmt (if the 'gmt' box is ticked)
--start-date-sys (if it's not ticked)
So I'd recommend to test without the launcher, passing those arguments, and see if you get the same bug? But, I could also use someone explaining a bit more what's going on :D
Ah wait, I read a bit more: this is no longer about the launcher at all ... ok.
So, we need something similar to the generic clock instrument, but independant of it, for the time dialog to rely on : is that correct?
Adding a /sim/time/local-string should be easy, will take a look :)
Working on this now.
Fixed on 2020.3, will be included in 2020.3.6, and will also merge to next of course.
Thank you, it works here!