Jim Wilson wrote:
That didn't work. If I add this bit of code right before the fgRenderFrame()
call in the main loop it works.
// PLEASE! This is NOT a patch. Don't add to CVS.
Pfew, Lucky I read far enough into your message ...
:-)
Erik
___
Flight
Norman Vine <[EMAIL PROTECTED]> said:
> Jim Wilson writes:
> >
> > Starting with --start-date-lat=2002:07:01:20:00:00 (default airport), I'm
> > seeing a sudden change in lighting after about a minute or so, attached is the
> > log output. I'm not sure if this is significant, but the actually s
Jim Wilson writes:
>
> Starting with --start-date-lat=2002:07:01:20:00:00 (default airport), I'm
> seeing a sudden change in lighting after about a minute or so, attached is the
> log output. I'm not sure if this is significant, but the actually sky
> location of the sun graphic doesn't seem to
Erik Hofman <[EMAIL PROTECTED]> wrote:
> Martin Spott wrote:
>> This is exactly the behaviour I encounter when for example starting at
>> dusk (in the c310u3a-3d at KHAF this time). When FG starts, the panel
>> is a bit dark (because it's already pretty dark outside) but it still
>> shows a clear
Martin Spott wrote:
"Jim Wilson" <[EMAIL PROTECTED]> wrote:
Starting with --start-date-lat=2002:07:01:20:00:00 (default airport), I'm
seeing a sudden change in lighting after about a minute or so,
This is exactly the behaviour I encounter when for example starting at
dusk (in the c310u3a-3d at
"Jim Wilson" <[EMAIL PROTECTED]> wrote:
> Starting with --start-date-lat=2002:07:01:20:00:00 (default airport), I'm
> seeing a sudden change in lighting after about a minute or so,
This is exactly the behaviour I encounter when for example starting at
dusk (in the c310u3a-3d at KHAF this time). W
"Curtis L. Olson" <[EMAIL PROTECTED]> said:
> > Did you probabliy mix up other options ? I usually run FlightGear with
> > --start-date-lat=2002:04:11:11:11:11 and enjoy a nice morning. After
>
> I just checked in some changes that may or may not help your
> situation.
>
Hi Curt,
Starting with
Martin Spott writes:
> "Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
> > I am just commiting an additional command line option to specify a
> > starting time of day in the sense of:
>
> Did you probabliy mix up other options ? I usually run FlightGear with
> --start-date-lat=2002:04:11:11:11:11 and
"Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
> I am just commiting an additional command line option to specify a
> starting time of day in the sense of:
Did you probabliy mix up other options ? I usually run FlightGear with
--start-date-lat=2002:04:11:11:11:11 and enjoy a nice morning. After
the
[EMAIL PROTECTED] writes:
> Am Dienstag, 16. September 2003 00:56 schrieb Curtis L. Olson:
> > I am just commiting an additional command line option to specify a
> > starting time of day in the sense of:
> >
> > --timeofday=dawn
> > --timeofday=dusk
> > --timeofday=noon
> > --timeofday=midn
Curtis L. Olson writes:
>
> I am just commiting an additional command line option to specify a
> starting time of day in the sense of:
>
> --timeofday=dawn
> --timeofday=dusk
> --timeofday=noon
> --timeofday=midnight
Neat but no need to do this iteratively or to call the geodetic routine
Am Dienstag, 16. September 2003 00:56 schrieb Curtis L. Olson:
> I am just commiting an additional command line option to specify a
> starting time of day in the sense of:
>
> --timeofday=dawn
> --timeofday=dusk
> --timeofday=noon
> --timeofday=midnight
>
> The next step will be to wrap thi
12 matches
Mail list logo
