• Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning old domain name stealing credentials

  • Special Server Maintenance

    Just when you think you have everything running some what better...

    You get a message from the Hosting company. Short story they need to move us to a new server. I have been working with them to plan a good date for all concerned. Here is what we have come up with as a schedule.

    1. November 4th 17:00 -5UTC shut off the forums and start backup proceedures. During this time there will be no access to the forums or the Resource Section.
    2. November 5th Continue with Backups and download same until complete.
    3. November 6th 7:00 turn over server to hosting company to move system to new server
    4. November 7th - 8th restore backups and upgrade forum software.

    If all goes well we should be back online on November 8th.

    To keep you updated we will post updates on AVSIM forums.

    Thank you for your support.

xml gauge for engine exhaust flames

tommieboy

SOH-CM-2025
I am looking for simple xml gauge that can trigger engine exhaust flames (to run continuously) above a specific throttle setting. Currently I have the engine exhaust flames set under the Lights section of the aircraft.cfg as Type 9, LOGO. I had a simple xml gauge for FS9 that I always used for this purpose, but if seems that I lost that one when I transitioned over to FSX Steam.

Thanks,

Tommy
 
Exhaust flames up to 80%

<Gauge Name="Exhaust Flames 1-engine" Version="1.0">
<Element>
<Select>
<Value>
(A:GENERAL ENG1 THROTTLE LEVER POSITION,percent) 80 > if{ (>K:SMOKE_ON) } els{ (>K:SMOKE_OFF) }
</Value>
</Select>
</Element>
</Gauge>

Thanks go to Bert Pieke for this gauge.
Regards,
Gary
Email me if you need details for adding flames to two engines using a two-lever quadrant.
garydanvers@xtra.co.nz
 
Hi Gary,

I already have my engine smoke effects triggered by the SMOKE_ON / SMOKE_OFF variables so that is currently working fine. Thus I'm thinking that the exhaust flames will need to be trigger by different gauge that is capable of triggering one on the Light entries as that is where the exhaust flames are currently assigned to. In my case Type 9, LOGO.

Thanks,

Tommy
 
Try this one Tommy, it's for a single engine using [lights].

Regards,
Gary

<Gauge Name="EngineExhaustLights-1eng" Version="1.0">
<Update Frequency="6"/>
<Element>
<Select>
<Value>
} (A:GENERAL ENG1 THROTTLE LEVER POSITION,percent) 80 >
if{ (A:LIGHT WING,bool) !
if{ (>K:TOGGLE_WING_LIGHTS) } }
els{ (A:LIGHT WING,bool)
if{ (>K:TOGGLE_WING_LIGHTS) } }
</Value>
</Select>
</Element>
</Gauge>
 
Last edited:
Try this one Tommy, it's for a single engine using [lights].

Regards,
Gary

<Gauge Name="EngineExhaustLights-1eng" Version="1.0">
<Update Frequency="6"/>
<Element>
<Select>
<Value>
} (A:GENERAL ENG1 THROTTLE LEVER POSITION,percent) 80 >
if{ (A:LIGHT WING,bool) !
if{ (>K:TOGGLE_WING_LIGHTS) } }
els{ (A:LIGHT WING,bool)
if{ (>K:TOGGLE_WING_LIGHTS) } }
</Value>
</Select>
</Element>
</Gauge>

Thanks Gary......

That looks vaguely familiar to me, and I'm pretty sure that is what I'm looking for.

Tommy
 
Gary,

I made some minor changes to the code to correspond the LOGO light assignment in my aircraft.cfg, and it works like a charm!

Thanks so much!

:encouragement:

Tommy
 
<Gauge Name="Exhaust Flames 1-engine" Version="1.0">
<Element>
<Select>
<Value>
(A:GENERAL ENG1 THROTTLE LEVER POSITION,percent) 80 > if{ (>K:SMOKE_ON) } els{ (>K:SMOKE_OFF) }
</Value>
</Select>
</Element>
</Gauge>

Thanks go to Bert Pieke for this gauge.
Regards,
Gary
Email me if you need details for adding flames to two engines using a two-lever quadrant.
garydanvers@xtra.co.nz

Just as a reminder:
Such code induces the infamous "continuous event" issue, causing a.o. problems with Multi-keystroke functions like engine selection, pushback etc.
Because an (in most case: unnecessary) event is issued at every gauge schedule (default 55 msec).

Remedy: allways test the current state of the function before issueing an event.
Like in the WingLights example, where one is forced to test the current state because WingLights has no ON and OFF variants (like Smoke events), but just a Toggle.

Cheers, Rob
 
Just as a reminder:
Such code induces the infamous "continuous event" issue, causing a.o. problems with Multi-keystroke functions like engine selection, pushback etc.
Because an (in most case: unnecessary) event is issued at every gauge schedule (default 55 msec).

Remedy: allways test the current state of the function before issueing an event.
Like in the WingLights example, where one is forced to test the current state because WingLights has no ON and OFF variants (like Smoke events), but just a Toggle.

Cheers, Rob


Thanks Rob....

I'm still a rookie with it comes to understanding this stuff. I'm pretty much contented as long as my aircraft doesn't got into a death spiral after I modify these codes. :encouragement:

Tommy
 
Back
Top