The command-line time options appear to be broken in the latest CVS
(Cygwin/Win2k). When I specify --start-date-gmt, --start-date-lat,
or --time-offset, the time is still set to the current GMT.
They worked in
FGFS 0.7.8 and I'm not sure exactly where along the line they stopped
working.
Can anyone else confirm this problem?
Paul,
Can you try this again with the latest cvs?
Thanks,
Curt.
Hi Curt,
I tried the latest CVS as of 2100 EST this evening, 2/11/2002. Some things
are fixed, others still behave strangely. The time I used for testing was
2/12/2002 at sunrise at KIAG (0717 EST, 1217 UTC), heading 090, altitude
1000 MSL. Specifically:
Options: HUD displays: Sun:
----
---
--start-date-gmt=2002:02:12:12:17:00 2/12/2002 12:17:00correct
(sunrise)
(this is UTC)
--start-date-gmt=2002:02:12:12:17:00
--time-offset=+00:15:00 1/1/1970 0:15:00 IT'S
DARK!!
--start-date-lat=2002:02:12:07:17:00 2/12/2002 07:17:00IT'S
DARK!!
--start-date-lat=2002:02:12:07:17:00
--time-offset=+00:15:00 1/1/1970 0:15:00 IT'S
DARK!!
--start-date-sys has same results as --start-date-lat.
Conclusions:
1. --start-date-gmt works fine without --time-offset.
2. --start-date-sys and -lat do not work properly, they work the same
as -gmt.
3. --time-offset works fine by itself.
4. --time-offset with --start-date-anything sets the date to 1/1/1970.
Hope this helps track down the problem.
Regards,
Paul
Paul R. Deppe
Veridian Engineering (formerly Calspan)
Flight Aerospace Research Group
150 North Airport Drive
Buffalo, NY 14225
(716) 631-6898
(716) 631-6990 FAX
[EMAIL PROTECTED]
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel