November 18, 200322 yr I just noticed that the start time FS indicates for when I am setting up a flight on the setup screen is 1 hour shy of the correct time for any changed location entered during setup. For example, when I launch the program and the default flight comes up on the screen at KSEA, the time is correct for PST. However, if I then move the start location to KSFO, which is in the very same time zone as KSEA, the program shows the time as 1 hour earlier than what PST should be. And if I move the start location to KJFK, the program shows the time as being 2 hours ahead of PST instead of 3 hours. Any thoughts as to what file may have gotten corrupted to cause this problem? My computer's clock is correct, and is set for PST. And I am certain this was not previously the case as I am sure I would have noticed it. Robert Chartoff
November 19, 200322 yr Hmm good question I remember having the same problem once. Maybe you should try FSrealtime (or what it's called). It will improve the way time is handled in FS significantly.-Daniel
November 19, 200322 yr You probably saved your default situation prior to november 1st. The time that was saved was daylight savings time. Go to the create a flight menu, set the time and date to now, and save your default flight again.A complete explanation can be found by searching for "savings time" [email protected] | 32gb RAM | EVGA GTX1080 8gb | Mostly P3Dv5 (also IL2:BoX, DCS, XP11)
November 19, 200322 yr Author I appear to have fixed the problem. Here's what I did:I created a new flight in the Pacific time zone on today's date - 11/19/03 - with a flight date of 10/15/03. (My object was to pick a date with daylight savings time.) I saved this as my default flight. This seemed to fix the Pacific time inconsistencies between KSEA and KSFO, but not those with East Coast time, which remained 2 hours ahead of Pacific time. I then created a new flight in the Pacific time zone on today's date - 11/19/03 - using today's date as the flight date. I then saved this flight as my default flight. After that, all time zones appear to be in synch (EST is 3 hours ahead of PST, etc.) and KSEA and KSFO show the same time. I hope this takes care of things until April, when I may have to reverse the process.Thanks for the input and I hope my experience may be helpful to others who encounter this problem. Robert Chartoff
Create an account or sign in to comment