Hi Thorsten,
Using z/Z to adjust visibility is something from the earliest days of the
simulator project, before METAR weather, probably before clouds, and the
sky dome. I don't personally mind if the z/Z key bindings go away.
What I do care about though is that FlightGear continues to be useable as a
flight training tool. An instructor working with a student may wish to set
a specific visibility, specific cloud layers, specific winds, specific
turbulence, all as part of a training scenario designed to instruct or
challenge or catch a student off guard.
We've always been able to set the individual weather parameters, either
through the built in weather dialog box, or by setting raw property values.
Setting raw property values allows nasal script control over the weather
(as I'm sure you well know) :-) but it also allows external control of the
weather, for instance by some external gui tool, or by some tool that wants
to setup equivalent visual conditions across multiple FlightGear PC's
running in sync.
So whatever we do, we can't override the ability to get low level granular
control of the weather parameters, and not just so that advanced weather
can manipulate them exclusively, also so that external tools can manipulate
them without advanced weather getting in the way or overriding the settings.
BTW, your email name is configured as "Renk Thorsten" so if you do find
yourself being called by your last name, it may be a simple
misunderstanding deriving from that. My dad calls all his neighbors by
their last name out of friendliness and respect, so it could also be that
too. :-)
Thanks,
Curt.
On Thu, Feb 28, 2013 at 3:31 AM, Renk Thorsten wrote:
> > You asked for ideas for a more descriptive text - I've gone one better
> > and
> > added descriptive texts to the gui. My design aim was to provide the
> > average
> > user with some indication of which option he should choose and in which
> > circumstance. It's only a shallow redesign. It would be nice, I think, to
> > allow max vis range to be as low as 10kms, and also if this could be
> > driven
> > by z/Z. However, these items are beyond the scope of what I set out to
> > do.
>
> Thanks.
>
> I can do the first item easily (I do think 10 km max visibility are a bit
> on the low side, but it doesn't hurt anyone..).
>
> As for z/Z - can we reach a decision first what to do with this? James and
> Stuart seemed to be considering to drop this key binding, and I would
> actually prefer that as well. Is there a compelling reason to manage
> visibility by key? For me, this resembles more an arcade game strategy
> than a realistic simulation.
>
> (If we keep z/Z, it'd be nice if anyone can give me a pointer how to link
> it with the max. visibility or just do it, because I don't know how it's
> done...)
>
> * Thorsten
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
--
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
