> Sorry, I was unclear.
> The computation of wind-from-down-fps can not be disabled at all, it is
> independent of the feature can_disable_environment.
Thanks for clarifying - that makes sense. Sorry for the confusion then.
* Thorsten
Am 04.08.2011 08:57, schrieb thorsten.i.r...@jyu.fi:
>> Please note, the check for
>> features.can_disable_environment == 1 is gone now. It doesn't make any
>> sense there.
>
> In a current GIT, none of the checks make any sense, because current GIT
> always has all the features. On the other hand,
> We don't normally maintain 2 versions: we leave the last stable as is,
> and
> only work on the Git version. If it's too much work, or too confusing I
> would suggest you abandon the version intended to be distributed via
> Forums, since that is not how we usually conduct our business.
That's pr
Thorsten wrote
> -Original Message-
> From:.i.r...@jyu.fi [mailto:thorsten.i.r...@jyu.fi]
> Sent: 04 August 2011 07:57
> To: FlightGear developers discussions
> Subject: [Flightgear-devel] Local Weather - backward compatibility
>
> > Pl
> Please note, the check for
> features.can_disable_environment == 1 is gone now. It doesn't make any
> sense there.
In a current GIT, none of the checks make any sense, because current GIT
always has all the features. On the other hand, the purpose of the
compat_layer.nas is to provide compatibil
5 matches
Mail list logo
