I couldn't find if this has ever been discussed before but here goes...Lately, I've been flying around the times of dawn and dusk. Out of curiosity, I would look up destination/departure sunrise/sunset times to try to time my flights to maximize the visual experience (REX 2 Overdrive and ENB series Shader). However, I found the FSX, a lot of times, especially at this time of the year, has the sun's position, in some cases, an hour away from where it should be (I fly real time and have compared it to where I live, and FSX is wrong). Any fixes for this?

FSX was developed when daylight savings time was from the 1st Sunday in April until the last Sunday in October. GWBush changed that, so MSFS is out about a week in the fall and 3 week in the spring.

FSX was developed when daylight savings time was from the 1st Sunday in April until the last Sunday in October. GWBush changed that, so MSFS is out about a week in the fall and 3 week in the spring.

Yes. So setting the time 1 hour earlier in sim will give a more accurate depiction during the "difference" of old and new DST

I am working on a set of replacements for the default "timezone.bgl" in FSX, which as stated does not use current DST dates and only covers the US and Western Europe. The first set, for North America is in the library and I am currently testing Europe/Middle East which will be released next. There are also some boundary changes, for example the EST portion of Indiana now follows DST.As far as the sun, I have done some comparisons using the planetarium freeware program "Cartes du Ciel v3.4" and FSX sunrise/sunset times and azimuth of the sun seem pretty good. Haven't checked out the moon at all though.scott s..

FS Real Time is in the library, has been around for a long time. I know it changes a lot of time zones, not sure about sun position.

FSRealTime uses Dennis Thompson's TimeZone3 files available here on the AVSIM library. Fixes mostly everything, but again, they were made before the DST change. So you'll still have the 1 hour error in the spring and fall.Interested in your files Scott. Changing those .bgl files is a LOT of work!! :)

Those timezones files are in FS9 format. FS9 has no way to set start/end dates for DST. As a result, he used a file switcher to replace files for STD time with files for DST by reading the system date (or I guess you can set your own date). There's an ini file which specifies the dates for DST so you can edit that to get what you want.FSX has default time zones aranged by longitude, but for some reason ACES set the GMT timezone from 15W to 15E, instead of from 7.5W to 7.5E so all the default time zones are 7.5 degrees off from correct location (before accounting for local variations from nominal time zone). Default FSX supplies a file timezone.bgl in sceneryBasescenery that provides local zone boundaries and DST for US and Western Europe. In testing I'm finding what appear so far to be bugs in how FSX handles timezone data compiled with bglcomp (primarily, how FSX handes timezone priority settings). Also the default timezone.bgl has many duplicate records in it, making me wonder if ACES realized they had a problem and had to create the duplicates until they could get the file to work as desired.As far as the sun, I expect that it is based on GMT so to check it you should compute the GMT of your local sunrise or sunset and set that in the time and season and then observe the sun in the running sim.From my testing the way FSX handles time is first it has a "setup" phase, where it determines local time from the system or saved flight, and then computes GMT from saved flight position and internal timezone. Once GMT is computed the sim enters "running" phase and GMT is maintained while local time is recomputed "on the fly" based on position and timezone.scott s..