I've tried all combinations of order in the code, even a separate element within an element, with the Shift or Rotation applied to the top level or next level element, but no change. Limiting the output to +/- pi or 2*pi had no effect. Changing <PointsTo> had no effect.
Do XML gauges just have a limit to how large an image can be to rotate before it can't handle it? Relevant XML is below.
Code: Select all
<?xml version="1.0" encoding="UTF-16"?> <SimGauge.Element id="ADI bmp"> <FloatPosition>282.000000,202.000000</FloatPosition> <Image id="ADI2.bmp" Name="ADI2.bmp"> <Axis>300.000000,600.000000</Axis> <Bright>True</Bright> <Bilinear>False</Bilinear> </Image> <Rotation id="Rotation"> <PointsTo>NORTH</PointsTo> <Expression id="Expression"> <Minimum>-3.141593</Minimum> <Maximum>3.141593</Maximum> <Script>(A:ATTITUDE INDICATOR BANK DEGREES, radians)</Script> </Expression> </Rotation> <Shift id="Shift"> <Scale>0.000000,1.000000</Scale> <Expression id="Expression"> <Script>(A:ATTITUDE INDICATOR PITCH DEGREES, degrees) 10 *</Script> </Expression> </Shift>
For comparison, a different method using 2 rectangles and a line worked perfectly, but that makes showing pitch bars and numbers a lot more complicated.