Norman Vine writes:
> Looks as if a recent change is always resetting the visibility
> to startup value. Haven't had time to see what is doing this
>
> This is with a this AM's CVS first update in a week or so
David recently revamped the weather subsystem to allow for specifying
conditions for multiple layers of the atmosphere. It's a little
complex and has a few kinks that still need to be worked out, but it's
pretty powerful and does a nice job.
The default gui ("Weather" -> "Weather Conditions") gives you 5
"aloft" layers and 3 "boundary" layers.
A the elevation of a "boundary" layer is specified relative to the
ground elevation so as you fly over changing terrain, the boundary
layer moves up and down relative to the ground elevation.
The "aloft" layers are specified relative to sea level.
For each layer you can specify temperature, dewpoint, wind,
turbulence, and visibility.
The environment manager figures out if you are in the boundary layers,
in the aloft layers, or some where in between, and does a reasonable
job of interpolating.
So the big problem at the moment is given that we can have up to 8
different visibility settings for 8 different layers, what do we bind
the "z/Z" keys to? Currently the are no longer bound to anything
useful. :-(
Curt.
--
Curtis Olson IVLab / HumanFIRST Program FlightGear Project
Twin Cities curt 'at' me.umn.edu curt 'at' flightgear.org
Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
