-
Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:
- Tag FS2020 specific questions with the MSFS2020 tag.
- Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
- Questions about aircraft design can be posted in the Aircraft design forum
- Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
- Questions about terrain design can be posted in the FS2020 terrain design forum.
- Questions about SimConnect can be posted in the SimConnect forum.
Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
animations
- Thread starter jetwelder
- Start date
- Messages
- 1,749
- Country
Gauge problem. Post your gauge please.
DG
DG
n4gix
Resource contributor
- Messages
- 11,674
- Country
It's easily done in a modeldef.xml entry...
Use (A:GENERAL ENG COMBUSTION:1, bool) for the control variable:
The above for example, will open/close based on whether engine 1 is running or not. Easy!
Use (A:GENERAL ENG COMBUSTION:1, bool) for the control variable:
Code:
<PartInfo>
<Name>OpenDoors</Name>
<AnimLength>100</AnimLength>
<Animation>
<Parameter>
<Code>(A:GENERAL ENG COMBUSTION:1, bool) 100 *</Code>
<Lag>20</Lag>
</Parameter>
</Animation>
</PartInfo>The above for example, will open/close based on whether engine 1 is running or not. Easy!
- Messages
- 1,749
- Country
I thought this was gauge driven. So forget that quote i said.
Yes you can make all of your animations in the animation manager. But you need to write a custom xml code.
Add this to the upper section of your xml code located here: Open in notepad.
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\bin
Add this near the other groups:
Add this xml code to the bottom of the page.
A:VAR is used for reading actions.
100 * This tells the animation to animate 100 keyframes.
<AnimLength>100</AnimLength> tells the gauge to only use 100 keys.
Now just assign Intake_Doors from your custom group in the animation manager.
DG
Yes you can make all of your animations in the animation manager. But you need to write a custom xml code.
Add this to the upper section of your xml code located here: Open in notepad.
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\bin
Code:
<Animation name="Intake_Doors" guid="d2d763b6-7994-4658-bbe2-99368c7ceafa" length="100" type="Sim" typeParam2="Intake_Doors"
typeParam="AutoPlay" />Add this near the other groups:
Code:
<AnimationGroup name="My Custom Project" guid="b74c6837-f99a-474b-b76e-55c47fd485a1">
<AnimationRef guid="d2d763b6-7994-4658-bbe2-99368c7ceafa"/>
</AnimationGroup>Add this xml code to the bottom of the page.
Code:
<PartInfo>
<Name>Intake_Doors</Name>
<AnimLength>100</AnimLength>
<Animation>
<Parameter>
<Code>(A:GENERAL ENG COMBUSTION:1,bool) 100 *</Code>
<Lag>40</Lag>
</Parameter>
</Animation>
</PartInfo>A:VAR is used for reading actions.
100 * This tells the animation to animate 100 keyframes.
<AnimLength>100</AnimLength> tells the gauge to only use 100 keys.
Now just assign Intake_Doors from your custom group in the animation manager.
DG
Last edited: