OK Jake, let's go to the basics.
The XML code should go to the file MakeMDL.parts.xml, which is located on your disk, just where you installed Microsoft SDK MakeMDL_SDK.
You insert the code just after the statement:
using a text editor, and save it.
Then, when you compile again your model, then the new model (.mdl) has your inputted code "built in".
What I mean "the code"?
For example:
Code: Select all
<part>
<name>anim_Spoiler_C</name>
<animation>
<parameter>
<code>
(A:RADIO HEIGHT, feet) 50 < (A:FLAPS HANDLE PERCENT, percent) 99 > 50 * *
</code>
<lag>20</lag>
</parameter>
</animation>
</part>
How do we "consume" that code?
It's easy - this way, when you'll give a part in your FSDS3 model the name "anim_Spoiler_C", then the part called "anim_Spoiler_C" will behave just how the XML tells it to.
You have to make an animation for a keyframe 0 and for a keyframe 50, for the above example.
When the condition is FALSE then all the above code "returns" 0 and this is our 0 keyframe. It corresponds to that spoiler is retracted.
When the plane is lower than 50ft AND flaps are fully deployed (we are landing) then the condition returns ... 50.
This is our keyframe 50 so we move the spoiler for the keyframe 50 to the deployed state.
Well, all that XML stuff is not very easy but after some training you should catch the clue.
.
.
, you could use (almost) whatever. I wanted it meaningful.
