Although the Microsoft SDK does not mention anything, Pete Dowson (FSUIPC fame) has found that at offset 3366 the 1 byte location is allocated by Microsoft for "engine fires" using bits 2^0 to 2^3 to indicate a fire in engine 1-4 respectively.

This fact would seem to me to "open the door" for someone rather clever with XML to write an engine fire gauge that triggers effects files (smoke or lights) creating visual smoke and maybe limited flames, and also impact engine operation.

Just a matter of manually positioning the effects emitters in the correct places for individual one to four engine aircraft.

The matching "fire suppression" gauge would then (possibly) terminate the "fire" by writing the necessary value to the appropriate bit, kill the smoke/fire (effects file), and maybe leave some negative impact on the affected engine(s) (dead or crippled) and or related systems.

Anyone up to the task?


best,

......................john

Quote:


I think what John's referring to is a way to have them AUTOMATICALLY create an engine fire, at random or predesigned points.  Adding a simple smoke entry that creates this effect is simple.  Doing what John's suggesting is something that would require a little XML tweaking and gauge knowledge.

As of yet, I'm PRETTY sure there hasn't been any work done for this.  However, a little trip to FFDS might not hurt, as well as downloading one or two of the SDKs on the subject.  I'm not really interested, but it seems like a good idea . . .