RE: [Flightgear-devel] visibility being reset
Norman Vine wrote: Curtis L. Olson writes: 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 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. I see 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. :-( This patch reenables increasing and decreasing visibility with the 'z' and 'Z' keys :-) Would someone please commit this or it's functional equivalent Cheers Norman # new bindings in keyboard.xml key n=90 nameZ/name descDecrease Visibility/desc binding commanddecrease-visibility/command /binding /key . key n=122 namez/name descIncrease Visibility/desc binding commandincrease-visibility/command /binding /key fg_commands.diff Description: Binary data ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] visibility being reset
Norman Vine writes: Curiously the commandline flag '--visibility=' still works but changing the property '/environment/visibility' in the RunTime Property Tree Browser doesn't The command-line --visibility option no longer sets /environment/visibility directly. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] visibility being reset
David Megginson writes:
Norman Vine writes:
Curiously the commandline flag '--visibility=' still works but
changing the property '/environment/visibility' in the RunTime Property
Tree Browser doesn't
The command-line --visibility option no longer sets
/environment/visibility directly.
Hmm a cursory glance seems to indicate a fairly direct link,
so calling something that effectively does the following
when key('z')
{
fgDefaultWeatherValue (visibility-m,
fgGetDoubleValue(/environment/visibility)*0.9);
}
when key('Z')
{
fgDefaultWeatherValue (visibility-m,
fgGetDoubleValue(/environment/visibility)*1.1);
}
Should do the deed :-)
Cheers
Norman
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] visibility being reset
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 We need now to set the visibility in the weather dialog. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] visibility being reset
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 Citiescurt '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
Re: [Flightgear-devel] visibility being reset
Curtis L. Olson wrote: 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. :-( Boundry layer visibilitty? Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] visibility being reset
Erik Hofman writes: Curtis L. Olson wrote: 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. :-( Boundry layer visibilitty? The system interpolates between entries, but if data is missing, grabs it from the lower layers, so then that might be a reasonable thing to do ... Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Citiescurt '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
RE: [Flightgear-devel] visibility being reset
Curtis L. Olson writes: 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 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. I see 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. :-( Curiously the commandline flag '--visibility=' still works but changing the property '/environment/visibility' in the RunTime Property Tree Browser doesn't Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
