PDA

View Full Version : Oil Temp gauges for 2 eng turbine heli



malibu43
March 4th, 2014, 22:36
Hi,

I am brand new to gauge/cockpit editing in FSX. I have a certain payware, turbine, helicopter that was released with some issues and appears to have been abandoned by the developer. Over the last few days, I have been able to piece together a working HUD (using existing freeware) and fix an issue with a Nav Radio. One of the remaining issues is that the Oil Temp gauge for Engine 2 is not registering anything in FSX. The gauge for Engine 1 appears to be working fine. I have scoured the .xml files for the two gauges and can't see any difference between the two, other than pointing to ENG1 or ENG2. I have compared the gauges and aircraft.cfg to working examples from some freeware aircraft and everything appears to be correct. I was hoping someone here might be able to help me see what I'm missing.

The entries from panel.cfg:

...
gauge15=Ah-1w!OilTemp1, 29,1699,351,351
...
gauge18=Ah-1w!OilTemp2, 421,1699,351,351
...


OilTemp1.xml (works fine)

<Gauge Name="Oil Temp 1" Version="1.0">
<Image Name="OilTemp.bmp" Luminous="yes"/>
<Element>
<Position X="75" Y="75" />
<Image Name="OilTemp_ndl.bmp" Luminous="yes">
<Axis X="3" Y="3" PointsTo="East" />
</Image>
<Rotate>
<Value Minimum="-50" Maximum="150">(A:GENERAL ENG1 OIL TEMPERATURE:1,celsius)</Value>
<Nonlinearity>
<Item Value="-50" X="128" Y="99" />
<Item Value="0" X="78" Y="137" />
<Item Value="50" X="20" Y="111" />
<Item Value="100" X="17" Y="42" />
<Item Value="150" X="75" Y="10" />
</Nonlinearity>
<Delay DegreesPerSecond="90"/>
</Rotate>
</Element>
<Mouse>
<Tooltip>Engine Oil Temp</Tooltip>
</Mouse>
</Gauge>


OilTemp2.xml (shows up fine, but needle doesn't move or register any values)

<Gauge Name="Oil Temp 2" Version="1.0">
<Image Name="OilTemp.bmp" Luminous="yes"/>
<Element>
<Position X="75" Y="75" />
<Image Name="OilTemp_ndl.bmp" Luminous="yes">
<Axis X="3" Y="3" PointsTo="East" />
</Image>
<Rotate>
<Value Minimum="-50" Maximum="150">(A:GENERAL ENG2 OIL TEMPERATURE:1,celsius)</Value>
<Nonlinearity>
<Item Value="-50" X="128" Y="99" />
<Item Value="0" X="78" Y="137" />
<Item Value="50" X="20" Y="111" />
<Item Value="100" X="17" Y="42" />
<Item Value="150" X="75" Y="10" />
</Nonlinearity>
<Delay DegreesPerSecond="90"/>
</Rotate>
</Element>
<Mouse>
<Tooltip>Engine Oil Temp</Tooltip>
</Mouse>
</Gauge>

Engine sections from aircraft.cfg

...
[GeneralEngineData]


//0=Piston, 1=Jet, 2=None, 3=Helo-Turbine, 4=Rocket, 5=Turboprop
engine_type = 3
//fuel_flow_scalar = 0.325
fuel_flow_scalar = 1.0
engine.0 = 0, 0, 4
engine.1 = 0, 0, 4
min_throttle_limit=0.00000


[TurbineEngineData]
fuel_flow_gain =0.02
inlet_area =0.000000
rated_N2_rpm =33000
static_thrust=150.00


[turboprop_engine]
power_scalar = 1.0 //Scalar on Turboprop power
maximum_torque = 3270 //Maximum torque available (ft-lbs)
...


I'm at a loss, and tempted to just replace OilTemp2 with OilTemp1 so both gauges match. Any ideas? What else should I look at? Is there anything in the .air file that would play into this?

Thanks.

n4gix
March 5th, 2014, 06:40
Study the SDK carefully, because even though engine one "works" it is purely by accident...

FS9 uses the ENGn convention.
FSX use the :n convention.

You have combined the two conventions in this statement, which is why it "won't work"...


(A:GENERAL ENG2 OIL TEMPERATURE:1,celsius)
The above says read ENG2's oil temp, but uses engine 1's index!



(A:GENERAL ENG2 OIL TEMPERATURE,celsius)
// or //
(A:GENERAL ENG OIL TEMPERATURE:2,celsius)

malibu43
March 5th, 2014, 15:14
Study the SDK carefully, because even though engine one "works" it is purely by accident...

FS9 uses the ENGn convention.
FSX use the :n convention.

You have combined the two conventions in this statement, which is why it "won't work"...


(A:GENERAL ENG2 OIL TEMPERATURE:1,celsius)
The above says read ENG2's oil temp, but uses engine 1's index!



(A:GENERAL ENG2 OIL TEMPERATURE,celsius)
// or //
(A:GENERAL ENG OIL TEMPERATURE:2,celsius)


Ahh... Thank you. So the bold one would be correct in my situation (FSX), right?

To be honest, I didn't actually read through any of the SDK stuff. I just jumped in and started "learning by doing" (or maybe "learning by attempting"). Maybe I should read up on some of this stuff. :)