Durk Talsma wrote:
> On Monday 16 October 2006 22:39, Donn Washburn wrote:
>> I just checked it against my memory and I found it to be 1 hour off.
>> It was 2PM local and if I hit the "Clock Time" button shows fgfs =
>> "local 13:28") it is currently 15:29 , hit Noon and it shows 12:59
>> Afternoon shows 15:42 (would be wrong)and Dusk shows 18:32 (would be
>> correct) finally hit Evening and it shows 19:26 (real time ##:34)
>> Turns out Afternoon and Evening display the wrong minutes. Sorry about
>> the possible errors in my quoting time. A fast run down shows that all
>> of the times do not hold the minutes correctly. The light/dark does
>> work correctly. Current System time is 15:38 fgfs show Afternoon as 15:42.
>
> Hi Donn,
>
> Just a few questions / thoughts: Which operating system are you running? The
> reason I'm asking is that I am aware of the fact that there might be a
> problem with the way the windows version of flightgear handles daylight
> saving time. I always found that windows time was one hour off when using the
> --time-match=[real|local|system] commandline options. This may explain the
> one hour difference between real and simulated time you're observing. On my
> linux system this has always worked correctly.
>
> Secondly, going through the time code recently, I noticed that the sunset /
> sunrise / noon times are calculated by calculating the exact solar time at
> the current user position. Although physically correct, we humans have
> decided that this type of time is quite useless in real life, and devided the
> planet into a more managable 24 time-zone system. Although this suits us, the
> consequence is that the difference between true solar time and local timezone
> time can be fairly high. I don't think that FlightGear currently takes the
> difference between solar time and human time zone information into account
> when it comes to noon/dawn/dusk calculations, but I could be wrong here.
>
> Hope this helps,
> Durk
>
SuSE 10.1 Linux (no windows here except on the house). I run a cron job
that
sets the system time to tick.uh.edu ( a local time server ). FGFS is run in
KDE 3.5.4. The toolbar clock shows the same time as my "Atomic" radio
clock.
I am not concerned about a per second time but it would be nice when you
hit Noon it would set the sun cycle to Noon and then adjust to the
system time. If it is the Airport location that determines the time in
24 or 12 hour time - no problem! However, it does seem if the real time
is 12:00 PM (noon) the time should not show FGFS 12:20 (an example only)
By the way the angle of the sun seems correct.
--
73 de Donn Washburn
307 Savoy Street Email: " [EMAIL PROTECTED] "
Sugar Land, TX 77478 LL# 1.281.242.3256
Ham Callsign N5XWB HAMs : " [EMAIL PROTECTED] "
VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg
BMW MOA #: 4146 - Ambassador
" http://counter.li.org " #279316
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Flightgear-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-users
