Got a very small problem. Well an enconvenience really.I have "use system time for free flight" checked, and the default 737 parked at Gate 10 at CYHZ ready to go as the default flight. DisablePreload=0 in the FSX.cfg file.When I start FSX and choose another field, CCQ3 for example, in the same time zone, the time is set back an hour. When I choose KBOS, a different time zone which is an hour behind, the time is set back the hour correctly.Any thoughts on correcting the local time shift?

Can't repeat your problem. Recommend that if you want to "use system time" set up your defualt flight to an airport in your time zone. When you start FSX, your local time should agree with clock time, and the GMT/UCT should also agree with actual UCT. Then use go to airport to go to CYHZ or CCQ3 and see what the local time and GMT show. Note that the time shift for daylight savings in FSX is not updated so don't do this on 3/11. (Well, you can do it but things will be off).scott s..

I use FS Real Time to fix all of the FSX time anomalies.http://www.3dsoftworks.net/products/fsrealtime/

IIRC FSUIPC also lets you sync your FSX time to the PC clock.Cheers,- jahman.

I have what may be the same problem and neither FSUIPC or FS Realtime fix it. My default flight loads to KTEB in the US Eastern time zone and the FS time agrees with the current local time and shows a five hour offset for UTC which is correct, If I now move the plane to KORD (or KMDW) in Chicago, which should be an hour earlier, the time does not change. If I move the plane to KSTL or KDFW, both of which are in the same time zone as Chicago, the local time is correctly set one hour earlier than KTEB. On my system, the only thing that I am aware of that's different about Chicago is that FS Dreamteam O'Hare is installed. I haven't tried uninstalling it, Can add-on scenery affect local time?

Edited February 27, 201214 yr by tjrush