• 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 Cannot reset scale - drawcall question

I think Bill Leaming is asking, if your primary source file, your master, main copy, is a different scale?
On the very first model (fuselage), I had made it a bit longer as per F-4E specifications, but later discovered I had to scale it down to F-4B size (bad reference). So I scaled down and reset XForm.
The thing is that this was on the fuselage, not any animated parts (they didn't exist at the time). Apart from that, I'm building at a 1:1 scale, only scaling vertices to get some symmetry when moving them.

Regarding rotations, I'll try adding a second or third keyframe (i.e. the nozzles are animating at 28deg, so I'll make it 4 keys every 7 degrees) and see how that pans out.
 
If anything was linked when to the fuselage in a hierarchy when you did that, you may have to reset XForm for the child objects too. (all of them)
 
Update on problem and solution:

Nozzles:
Problem: Scale is [1,1,1]
Result: animations worked on any parts that weren't linked to another "scaled" part.
Solution: Reset XForm, edit pivot to be the way I want it, link and animate. Everything is normal.

Problem: Jerky animationsin 3dsmax and FSX (parts rotated on two axes instead of only the one I keyframed)
Solution: Instead of using "Autokey", I used "Set Key" and rotated the parts in position, manually keyframing one or two intermediate positions to be safe. Animation played fine in 3dsmax and FSX

Gear Doors, Wingfold and canopies
Problem: Jerky animations
Solution: Manual keyframing ^^
That method seems to work for all parts, so I will not use autokey again as it's done more good than bad on all my models (not only for FSX, also for FS9, Battlefield 1942 and other games).

Thanks to everyone who posted their ideas and helped me!
 
I'm happy to read that you've found workable solutions for your issues, although I must say I've never experienced any problems using "Autokey," but then again it's quite possible that my precise procedure is a bit different than the one you are using... :twocents:
 
I am happy too!:)
Despite still getting scale errors of 1,1,1 for some animated parts, animations are smooth as silk and working fine. Let's hope it won't be a problem later.
Phantom_Nozzle.jpg
 
I got the "pruning scene graph error".
It was solved after I noticed that I had volume shadow checked for a material, assigned to half the mesh (the mesh had 2 material IDs). This caused the shadow to go through the other half of the fuselage.
After unchecking it, the error stopped.
My 2 cents.
 
Taken from P3D SDK:
Code:
  <PartInfo>
        <Name>launch_bar</Name>
        <AnimLength>200</AnimLength>
        <Animation>
            <Parameter>
                <Code>
                    (A:LAUNCHBAR POSITION:1, percent) 0 &gt; if{ (A:LAUNCHBAR POSITION:1, percent) 100 + } els{ (A:GEAR ANIMATION POSITION:0, keyframe) 100 min }
                </Code>
            </Parameter>
        </Animation>
  </PartInfo>
I see it is a 200 frame animation, with 0 as stowed, 200 fully extended.
and now the question: what does the "else" statement mean?
If I understand properly (just starting to understand XML):
The launch bar position is the percentage of its extraction +100 keyframes.
Thus 0%=100th keyframe, 1%=101st, 100%=200th.

Else, its position at 0% extension will be the one that is found when at the 100th keyframe of the gear animation (fully extended)?

I'm asking because I'd like to see if I can use the launch bar animation on the Phantom gear. On the Phantom, the gear is extended fully before launch to increase AOA.

The 2nd Q would be: if I animate the nose gear strut to extend as a launch, will the contact point move lower with it so that the nose is raised? Or will it just drill through the deck?

I suppose I could animate the entire aircraft to rotate and assign the launch bar animation to it, but that would create a mess.
 
Last edited:
I think the else statement is to cause the launch bar to retract as the gear retracts. It links the launch bar position to the gear extension state, in the case where the launch bar is not greater than 0% extended. The "100 min" is setting a ceiling on the launch bar animation - it cannot exceed 100, even if the gear animation position exceeds 100 (which would occur as the gear compresses - if it weren't there, the launch bar would move with the gear compression), as long as the launch bar is not being actuated.

As for extending the nose gear, I don't think you can make the contact point move, so the nose gear will just extend through the ground. I'd love to be proven wrong, though - that would be a cool function.
 
Last edited:
For some reason, no animations work anymore when exporting from both max 2011 and 2012.

I tried compiling with an old, working .x and .xanim file but no animations work here either. My guess is that something's wrong with my system after formatting.

.NET and VC++ redists are installed (up to 2010 versions). Any idea on what might be causing this?

If someone wants to try compiling the .x files, I can generate and send them.
 
Swapped stops and commas and it worked.
Another couple of observations:
-The .x exporter works fine regardless of regional settings. The problem is in XtoMDL
-Animations with scale errors of [1,1,1] work fine. It seems, though that this is required only at the keyframe positions. My C_Gear has a scale of 0.9999 at intermediate positions and works perfectly.
 
Back
Top