Ever since the switch from Daylight Savings Time to Standard Time last weekend, my copy of FS9 has not adjusted properly.Anyone else experiencing this problem?Some people have mentioned that their scenery re-indexed, as did mine, but I cannot get my FS local time to synch properly with FS GMT.I've read about the utilities that are out there to fix the timezone problems, and I've tried them, but still no luck in getting FS to understand Standard Time is now in effect.Bare with me as I give you an example and perhaps some of you that think your clock is OK can check this out and find that you also have a problem you'd didn't realize was there.I'm located in the Pacific Time Zone, which is currently -8 hours behind GMT. My FS time setting shows the difference as -7 hours. If I start the sim in one location, observe the time, then change airports and check the time settings again, I get correct results in some zones, but incorrect results in other zones.Here is an example using the www.timeanddate.com site as a base reference. I start the sim, create a flight and from the create menu, choose a world location, set the time to the current GMT (2200 for the current test), then review the local time from the same menu. The results are posted below:Location________Local________GMT_____World Clock___DifferenceLos Angeles_____1500________2200_______1400___________+1London__________2200________2200_______2200___________ 0Boston__________1800________2200_______1900___________+1Buenos Aires____1900________2200_______1900___________ 0Rome____________2300________2200_______2300___________ 0Cairo___________0000________2200_______0000___________ 0Hong Kong_______0500________2200_______0600___________-1Honolulu________1200________2200_______1200___________ 0Chicago_________1700________2200_______1600___________+1Testing to see if the problem is connected to the O/S, I ran this test on Win/ME and on WinXP getting the same results.While Daylight Savings Time was active, I never had an issue with GMT time versus local time.Anyone have any idea what's going on?Bruce

Yes Bruce, I too am having this problem. There is another thread on the this site that talks about this problem. That thread has a workaround which I found did not work for me in FS9. FS Realtime does not fix this problem yet either. So we wait to see if MS has a fix or the guys over at FSRealtime can get around this thing also.Bob Johnson

Thanks for the feedback Bob.I'm still trying new ideas to get past this problem.Basically, if all the timezones were off, it would be an easy fix to just change the system time. But because the diffences are quite numerous, long distance flights are going to run into some problems.Makes me wonder how this bug affects AI aircraft since they run on GMT time. Some areas are going to see takeoffs and landings at the wrong time.Bruce

Your need two flights set up, one based on daylight time and one based on regular time. Twice a year you need to change your default so it matches. In addition FS doesn't seem to pick up the change on the exact day.Start Fsim and from the create a flight screen (if you by pass this screen, hit Esc and end flight) change the date to Nov.1, DO NOT adjust the hours only the date, hit OK and then Fly now and let it load. Now check the time and it should be right, save the flight and check the box to make it your default flight. Exit Fsim and then restart and let it load, check the time and it will probably be off. I believe this is because it's still Oct. and Fsim won't synch. up til Nov.1st. If you go to the select a flight menu and pick your new default flight and start it the time will be OK, although the date is off. It should synch up come Nov.1st.Until Nov.1st you will have to either use the correct date and have the time off or select the new flight and have the time right and the date off. I'm waiting til the 1st. to see if it synchs up, I think it will. With FS2K2 I had two flights, one named 0defrt (regular time) and one named 0defdt (daylight time) that I changed back and forth as my defaults, and I seem to remember that Fsim didn't pick up the time change until the end of the month.Kurt M

Kurt,Thanks alot! That did the trick.Leave it to Microsoft to bugger up something as simple as Daylight Savings Time!

Kurt,Thanks for that scenerio, but there just has to be a better fix from either MS or the FSRealtime guys. I fly all over the world and can't use the same default setup each time.Microsoft, since you guys told me at the AVSIM conference that you follow these forums please put a fix up on your site for this problem. It really is mucking things up both with scenery and AI.ThanksBob JohnsonDenver,CO

Hello!Just a thought, but since GMT isn't adjusted for DST, and you are -8 hours behind GMT during daylight savings time; you are now only -7 hours behind GMT during daylight standard time after 'falling' back one hour.Make sense?

Actually Pacific Time (in this case) is 8hrs behind GMT in the winter, and 8 hrs behind British Summer Time (the daylight savings equivalent) in the summer. Fall back date between US and Europe always coincides, but Spring Forward is often a week or two different (just to confuse things even further!!).So really, PDT is -9 hrs from GMT, PST is -8.Take it from a Brit living in California!!