• 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.

FSXA Custom Animation won't work

Heretic

Resource contributor
Messages
6,830
Country
germany
I've got a model using custom and stock animations, visibility tags and mouse rectangles.
Modeling tool: *Max

- The mouse rectangles all work
- The stock animations all work
- The visibility tags all work

The custom animations, however, won't.

- They're all keyframed and work in *Max
- They're all correctly tagged with the animation manager and Attach Point tool (mouse rect)
- XtoMdl parses them without complaining

In FSX, however, I click a part and nothing happens.

Well, not entirely true...something happens, but very quickly.
Checking up with XMLTools, I can see that their L: vars get switched from 0 to 1 and and back again within a split second.

- A few dozen repetitions of "Reset Scale" did not help
- Retagging the parts with the AM and AT did not help either


Remodeling the parts in question is no option.

Here's a sample code (the GUID is unique):

Code:
<Animation name="F27_Window_R" guid="bd6a6b12-9076-43e3-b522-4503fc2ac02e" length="100" type="Sim" typeParam2="F27_Window_R" typeParam="AutoPlay" />

<PartInfo>
<Name>F27_Window_R</Name>
<AnimLength>100</AnimLength>
<Animation>
<Parameter>
<Code>
(L:WINDOW R,bool) 100 *
</Code>
<Lag>25</Lag>
</Parameter>
</Animation>
<MouseRect>
<Cursor>Hand</Cursor>
<TooltipText>Open/Close Right Window</TooltipText>
<MouseFlags>LeftSingle</MouseFlags>
<CallbackCode>
(A:AIRSPEED INDICATED, knots) 40 &lt;
if{ (L:WINDOW R, bool) ! (&gt;L:WINDOW R, bool) }
</CallbackCode>
</MouseRect>
</PartInfo>


Any ideas?
 
Does it work reliably if you remove the airspeed condition? It is possible that is causing the problem...
 
For funsies, I've exported just the window part as the VC and tried it in FSX. It doesn't move. When I, however, alias it to the DC-3 as the interior model, it *does* move!

Dito for the entire VC!!

Grey eyebrow level: 50.


- Edit:

Exported only the fuselage of the exterior model and guess what...



- Edit²:

Well...

Code:
<PartInfo>
<Name>F-27 Controller</Name>
<Visibility>
<Parameter>
<Code>
(L:WINDOW L, bool)
(A:AIRSPEED INDICATED, knots) 40 &gt;
and
if[ 0 (&gt;L:WINDOW L, bool) }

(L:WINDOW R, bool)
(A:AIRSPEED INDICATED, knots) 40 &gt;
and
if[ 0 (&gt;L:WINDOW R, bool) }
</Code>
</Parameter>
</Visibility>
</PartInfo>

Spot the error!
 
Last edited:
Oh my! This is indeed one of the chief "drawbacks" to having separate .mdl files now, as one has to be very, very careful to keep the exterior model updated along with the interior model especially while still in the animation/development phase.

I've had this same situation bite me on the posterior more than once. :confused:
 
Just curious... Did you try resetting scale on the parts? Are you testing in FSX? If you have P3D, test in that and see if they work. If they do, then its a scaling issue.

Make sure you also did all of your frames notation and 'double name' in the top end of the ModelDef sheet. I have left off the second name before, or had the previous name slot in it, (two names in one string) before and didnt see my mistake.

Try also resetting your animation. Set for animation key frames (0-50 or what ever it has) and delete/reset it.

Also check that your animations match the animation block with the title string in the ModelDef, and also key frames match those as well.

Since the animation is working in the other model, its surely your part.

If you have a $pan texture on the part and you are 'also' animating it with a mouserect, then your $pan is over-riding it. (Paper-Mouserect-Scissors-Stone laws. $pan is paper; MouseRect is Stone. $pan always wins over MouseRectums).
 
Just curious... Did you try resetting scale on the parts? Are you testing in FSX? If you have P3D, test in that and see if they work. If they do, then its a scaling issue.

Yes: Scale and FSX
No: P3D



Good points for anyone else running into any similar error though, Bill.
 
Try opening your ModelDef in Chrome browser and see if it shows up ok.

It may still show up fine but still have an issue in the code somewhere.
 
hehe someone forgot to hold down the shift key :) they really need to make a keyboard for xml coding which has a few of the shit/key combo's reversed :D
 
hehe someone forgot to hold down the shift key :) they really need to make a keyboard for xml coding which has a few of the shit/key combo's reversed :D

Nope, someone accidentially pressed "ALT GR"+"8" instead of "ALT GR"+"7". (German layout!) ;)
 
My pinky finger refuses to learn the memorized placements of { and }. I always have to look at the keyboard. Poking in the air with said pinky always hits Enter or misses the key I need.
 
I know exactly what you mean. Never learned blind ten-finger-typing and probably never will.
 
Back
Top