It turns out that the value of the "time_zone" field in the configuration file is interpreted as a TZ system variable value, not as the commonly used human-readable "UTC+offset" values.
Basically, the "offset" is interpreted as the number of hours that should be _added_ to local time to get UTC.
You can try entering some human-readable time zone name as recognised by the tz utility: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
You can try "America/Chicago", perhaps? I am not sure if the time zone names used by tz on Unix/Linux will be recognized on Windows.
Stellarium's user manual most definitely needs to be updated...
It turns out that the value of the "time_zone" field in the configuration file is interpreted as a TZ system variable value, not as the commonly used human-readable "UTC+offset" values.
See here for an explanation of why "UTC-6" doesn't have the expected result: www.gnu. org/s/libc/ manual/ html_node/ TZ-Variable. html
http://
Basically, the "offset" is interpreted as the number of hours that should be _added_ to local time to get UTC.
You can try entering some human-readable time zone name as recognised by the tz utility: en.wikipedia. org/wiki/ List_of_ tz_database_ time_zones
http://
You can try "America/Chicago", perhaps? I am not sure if the time zone names used by tz on Unix/Linux will be recognized on Windows.
Stellarium's user manual most definitely needs to be updated...