- Messages
- 28
- Country
I made some flight plans using KMDT airport. They were set to local DST time for the season. If I started FS at one minute after the hour (0700) all planes scheduled between 0701 & 0730 hours would takeoff approximately on schedule.
When the clock continues past the half-hour the time changes, by jumping ahead, to 0830 hours. All flights between 0731 & 0830 hours, do not execute. As the day wears on the clock bounces back & forth till finally most of the flights are executed.
I also noticed when using 4x time acceleration, the time does not increment forward to the next minute after 59 seconds. The clock displays the second count as: 59, 60, 00, 01 etc.
see pic.
It continues counting till 30 seconds & then increments to the next minute. During normal 1x speed, the clock counts time past the half-hour till it reaches the sixty count & then jumps an hour ahead.
I remember reading the time zones were never implemented correctly by Scott S., causing problems with schedules running in DST. So I figured to wait till DST ended.
Considering I compiled these FPs using local (summer) DST, I changed the time zone to [UTC -5] EST for KMDT, saved & recompiled the FPs for the new EST. AIFP now displays the correct times for the new schedules. One hour prior to DST time.
Now the clock will still change time erratically, in the same manner, but most of the flights will execute even when the clock jumps time. It still will not do a normal time count though.
Any help in resolving this will be greatly appreciated....
When the clock continues past the half-hour the time changes, by jumping ahead, to 0830 hours. All flights between 0731 & 0830 hours, do not execute. As the day wears on the clock bounces back & forth till finally most of the flights are executed.
I also noticed when using 4x time acceleration, the time does not increment forward to the next minute after 59 seconds. The clock displays the second count as: 59, 60, 00, 01 etc.
see pic.
It continues counting till 30 seconds & then increments to the next minute. During normal 1x speed, the clock counts time past the half-hour till it reaches the sixty count & then jumps an hour ahead.
I remember reading the time zones were never implemented correctly by Scott S., causing problems with schedules running in DST. So I figured to wait till DST ended.
Considering I compiled these FPs using local (summer) DST, I changed the time zone to [UTC -5] EST for KMDT, saved & recompiled the FPs for the new EST. AIFP now displays the correct times for the new schedules. One hour prior to DST time.
Now the clock will still change time erratically, in the same manner, but most of the flights will execute even when the clock jumps time. It still will not do a normal time count though.
Any help in resolving this will be greatly appreciated....