sim prop binary question............

[3rett]

hey bill,

ive got a couple gauges im trying to convert to spb with the aces tool. the best info i could find was a post of yours on another forum. in it you mentioned having a template of the new syntax used in fsx. ive been through every piece of the sdk and cannot find anything on it. so i opened some of the default airbus' xml's and tried some of its syntax. this rendered my gauge inoperable, so........ i was wondering if you could post a template with the updated syntax. its maybe a lot to ask and understand if you cant.

another thing i was wondering about was.......... i started converting a working gauge. first i did the macros to a t. even got the aces tool to ok them. but then the lines that depended on the stopped working. is this because the entire gauge has to be converted in order for it to work, or does it sound like i have deeper issues. anyway thanks in advance for your help

3rett

[n4gix]

The entire gauge must be converted to the new FSX syntax schema before it will work.

You will likely have to "port" the existing XML code one Element at a time and test, test, then retest...

[3rett]

hello bill,

thanks for your response. well that clears up why my gauge wasnt working :). my gauge however consists primarily of the "<element> <select> <value>" tree type syntax with vars and events in between. now the aces tool refuses to except the <value> syntax. i was wondering if you or anyone knows what the proper fsx replacement syntax would be for this particular syntax tree. ive been messing around with "expression" and "script" but so far its not working. so thanks again in advance, i really appreciate all the help ive gotten so far.............

3rett

[n4gix]

Searching through the example XML code from the Bombardier_CRJ_700 for specific examples, you can compare the new syntax with the old quite easily. For example

<Rotate> versus <Rotation id="Rotation>...

FS9 syntax:

<Rotate>
<Value>(A:Attitude indicator bank degrees,radians)</Value>
</Rotate>

FSX syntax:

<Rotation id="Rotation">
<Expression id="Expression">
<Script>(A:Attitude indicator bank degrees,radians)</Script>
</Expression>
</Rotation>

<Shift> versus <Shift id="Shift"> -

FS9 syntax:

<Shift>
<Value Minimum="-90" Maximum="90">(A:Attitude indicator pitch degrees,degrees) /-/</Value>
<Scale Y="-3.467"/>
</Shift>

FSX syntax:

<Shift id="Shift">
<Scale>0.000,-3.467</Scale>
<Expression id="Expression">
<Minimum>-90.000</Minimum>
<Maximum>90.000</Maximum>
<Script>(A:Attitude indicator pitch degrees,degrees) </Script>
</Expression>
</Shift>

As you can see, all of the relevant information is there, but has been "rearranged" in the FSX syntax. It takes more lines/entries to accomplish the same task...