Daube wrote on Nov 27
th, 2008 at 8:18am:
Err yes, but in fact I was TRYING to follow the cheklist and then I got this problem. I know the pane would not start with CTRL+E, it's not meant to be started like that anyway.
AIR there was a new CAB file released for that aircraft to deal with
the FSX-induced problems to that FS9 aircraft but I'm not sure if it
dealt with the starter problem.
I created my own starter code early on, since the way FSX handles
the starters is different than the way FS9 handled them.
I used a simplistic approach, adding two new starter switches to the panel.
Here's the XML code I used for engine 1:
Code:<?xml version="1.0" encoding="utf-8"?>
<Gauge Name="748 Engine Start 1" Version="1.0">
<Element>
<Select>
<Value> (A:General eng1 starter, bool) </Value>
<Case Value="0">
<Image Name="Switch_PYE_ST_Cen.bmp" ImageSizes="25,45,40,72"/>
</Case>
<Case Value="2">
<Image Name="Switch_PYE_ST_Up.bmp" ImageSizes="25,45,40,72"/>
</Case>
<Case Value="1">
<Image Name="Switch_PYE_ST_Down.bmp" ImageSizes="25,45,40,72"/>
</Case>
</Select>
</Element>
<Element>
<Select>
<Value>(L:Port_Turbine_RPM, number) 8000 > (L:STARTER1_active,bool) && if{ (>K:TOGGLE_STARTER1) 0 (>L:STARTER1_active,bool) }</Value>
</Select>
</Element>
<Mouse>
<Help ID="HELPID_GAUGE_STARTER_SWITCH"/>
<Cursor Type="Hand"/>
<Click>(>K:TOGGLE_STARTER1) 1 (>L:STARTER1_active)</Click>
</Mouse>
</Gauge>
A similar XML gauge for engine 2 was created by just replacing the references
to engine 1 with "2" above.
I placed my switches on the panel near the prop sync switch.
Paul