Hi all,
I understand the both point of view about wildfire and "gaming" issues.
but I think that changing wildfire-on-crash property is not a good
solution because it is registered, but it is also a problem if an
aircraft designer wants to create his own crash animation.
I'm quite "surprised" not to see someone purpose an other solution which
is only to override wildfire.ignite() function in a single aircraft, as
we are used to do for brakes, or starting engines. If one aircraft
designer does not want any wildfire with its aircraft for any reason, it
is quite simple to add in a Nasal script inside the aircraft config
files something like:
wildfire.ignite = func {}
or for "gaming" purposes:
var save_wildfire_ignite = wildfire.ignite;
wildfire.ignite = func (position) { my_own_crash_animation(position); }
then every local settings are conserved, no other aircraft should be
affected, and any other animation than wildfire could be played, even
the official wildfire animation using save_wildfire_ignite()).
an other solution could be to save the property state at startup, then
restore it at the end of th session (but need to manage reset).
best regards
seb
Detlef Faber a écrit :
> Am Sonntag, den 15.02.2009, 09:45 +0100 schrieb Detlef Faber:
>> Am Samstag, den 14.02.2009, 23:15 +0100 schrieb gerard robin:
>>> On samedi 14 février 2009, Melchior FRANZ wrote:
>>>> * Gerard Robin -- Saturday 14 February 2009:
>>>>> Log Message:
>>>>> withdraw the "game coat"
>>>>>
>>>>> + <environment>
>>>>> + <wildfire>
>>>>> + <fire-on-crash type="bool" >false</fire-on-crash>
>>>>> + </wildfire>
>>>>> + </environment>
>>>> AIRCRAFT MUST *NOT* CHANGE SYSTEM SETTING!
>>>>
>>>> This setting disqualifies the F8 for inclusion in a release.
>>>> Oh, well. Why do I always have to complain?! Maybe everyone
>>>> else doesn't care about cleanliness and a sane concept,
>>>> anyway. Sigh ...
>>>>
>>>> m.
>>> And what about some specific aircraft feature regarding the crash
>>> processing.
>>>
>> Than it would of course be acceptable, but the Crusader doesn't show any
>> specific behaviour.
>
> ... at least on land, on water it doesn't burn, and still doesn't burn if one
> manages to slide onto the shore.
> The Water Reactions are unaffected by the wildfire feature.
>>> In that case why don't you prohibit anything like, wake effect with the
>>> Catalina, jet blaster with turbine and so one.....
>>>
>>
>>> I disagree with you and anybody here about it.
>>>
>>> That is specific to the model
>>>
>>> You should have discussed it here before implementing that feature.
>>>
>> The wildfire feature has been around some time now and as far as I know,
>> nobody has complained. It can be turned off by the user and I'm sure a
>> lot of users (like me) like it.
>>
>> If you wish a discussion, post to the list and don't hinder the users of
>> your Aircraft to use a feature FlightGear offers.
>>
>>>
>>>
>>
>> ------------------------------------------------------------------------------
>> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
>> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
>> -Strategies to boost innovation and cut costs with open source participation
>> -Receive a $600 discount off the registration fee with the source code: SFAD
>> http://p.sf.net/sfu/XcvMzF8H
>> _______________________________________________
>> Flightgear-devel mailing list
>> Flightgear-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
