Hi,
You need to add the XML gauge to your panel.cfg;
see the README in the zip file.
The purpose of the gauge is to automate engine smoke, so you don't have to do that manually with the "I" command.
That said (and with due respect to the designer): the gauge isn't very well designed.
This is the code:
Code:
[FONT=Verdana,Arial,Tahoma,Calibri,Geneva,sans-serif](A:GENERAL ENG1 THROTTLE LEVER POSITION,percent) 60 > if{ (>K:SMOKE_ON) } els{ (>K:SMOKE_OFF) }[/FONT]
1. This really is bad design:
The gauge continuously (every 55 msec) issues a SMOKE event.
Causing a.o. problems with Multi-keystroke functions, like Select-Engine, Toggle doors, Pushback, etc …
2. Limited functionality:
a. It doesn't check for running engines; meaning that if Eng1 is Off, and you set Throttle > 60 %, you will see engine smoke… LoL
b. It doesn't make a distinction between left/right engines; see a.
If you really want this auto-smoke gauge to work properly (assuming the throtttle lever criterium is correct):
In the aircraft.cfg, add:
[FONT=Verdana,Arial,Tahoma,Calibri,Geneva,sans-serif][FONT=Verdana,Arial,Tahoma,Calibri,Geneva,sans-serif][SMOKESYSTEM]
smoke.1=-1.2, -9.20,0, fx_beech 18_ExSmoke
smoke.2=-1.2, 9.20,0, fx_beech 18_ExSmoke
In the gauge [FONT=Verdana,Arial,Tahoma,Calibri,Geneva,sans-serif]beech_smoke.xml, replace the line above by:
Code:
[FONT=Verdana,Arial,Tahoma,Calibri,Geneva,sans-serif](A:GENERAL ENG COMBUSTION:1,bool) (A:GENERAL ENG THROTTLE LEVER POSITION:1,percent) 60 > &&
if{ (A:SMOKE ENABLE:1,bool) ! if{ 1 (>K:SMOKE_ON) } }
els{ (A:SMOKE ENABLE:1,bool) if{ 1 (>K:SMOKE_OFF) } }
(A:GENERAL ENG COMBUSTION:2,bool) (A:GENERAL ENG THROTTLE LEVER POSITION:2,percent) 60 > &&
if{ (A:SMOKE ENABLE:2,bool) ! if{ 2 (>K:SMOKE_ON) } }
els{ (A:SMOKE ENABLE:2,bool) if{ 2 (>K:SMOKE_OFF) } }
[/FONT]
Which solves the "bad design", checks for engines running and enables the auto-smoke effect independantly for both engines.
You can edit the aircraft.cfg , and an xml file, simply with Windows Notepad.
TIP: use Windows Copy/Paste, to avoid typo's .....
Not tested, but unless I made typo's myself, Roman will probably agree with this ...LoL
Cheers, Rob
[/FONT]
[SUB][SUP]
[/SUP][/SUB][/FONT]
[SUB][SUP]
[/SUP][/SUB][/FONT][FONT=Verdana,Arial,Tahoma,Calibri,Geneva,sans-serif]
[/FONT][FONT=Verdana,Arial,Tahoma,Calibri,Geneva,sans-serif]
[/FONT]