• 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

Messages
218
Country
greece
1) I was test-exporting my Phantom (P3D SDK) and after doing the checks, I'm getting scale broken errors, with scales of [1,1,1]. I obviously don't get the errors to go away, no matter how I reset the scale (via check window or XForm panel).

2) Another problem is that due to the complexity of the nozzle model, I'm going to get a lot of drawcalls.
Each nozzle consisted of 144 animated parts, multiply by 2 equals 288 draw calls.
Adding 6 fins x 2 wings=12DCs, 3 tail fins, an estimate of 8 parts x 3 gear legs=24DCs, canopies and glass another 4, pilots sticks and levers another 6, so far touching 334 drawcalls and there's more to come (exterior model).

What I want to ask (in order to reduce them):
I've made a skinned version of the nozzle (merged in one part and skinned). Will this count as one drawcall as a single object, despite having 48 bones? That would save me 96 drawcalls from the two engines (and I plan to do it with the other nozzle parts too).
 
Since no one replies I'll just chip in my 2 cents.

I'm by no means an expert on modelling but I do know for a fact that FSX will only use up to 22 bones in one shader pass. So you're looking at at least three calls to draw that nozzle. Moreover you're forcing FSX to split that mash into three smaller parts on its own. Perhaps it's better to do it manually in the model?
 
I'll probably remodel the nozzles to avoid any further scaling errors. For now I've moved on to the wings and will continue from there.
 
Rather than reply in private to the PM, I'll reply here instead...

Simplify your problem by creating just ONE petal of the precise size and shape needed, animate it, then test in sim for proper operations.

Once a single petal is working, then use the Array tool to clone the rest of the petals for a single nozzle.

Again, test in the sim for proper operations.

Once one nozzle is completed, clone all of the animated petals for the other engine's nozzle, use the Animation tool to change the controlling script for the other engine, then export and test in the sim for proper operations.
 
What sim variable are you using as the animation controller?

For testing it would likely be easiest to use lever_throttle0...
 
I'm using:
l_lead_edge_flap_percent_key
wing_fold_l_pct
wing_fold_r_pct

Keyframed 0-100, converted to linear animations from track view and "created" in animation tool.

-Neither the flap nor wingfold works (flaps did work once, but only played like 5 frames of the animation-wingfold never did work).
-The flap keeps also giving me scaling errors whenever I link it to LOD_100, but I fix them and reanimate each time, check for errors and export.
-Even if I don't fix them, I get an error of [1,1,1] scaling.
-Tried creating a box and and tagging it with lever_throttle0, it did work on its own, so the SDK seems to function.
 
What does the Dope Sheet report for the Transform/Scale?

It should show X:100.0 Y:100.0 Z:100.0
 
From dope sheet: every object is scaled at 100% (x,y,z).
Tried setting the flap to lever_throttle0, still nothing budges.
 
Double-check your animation controllers. Position, Rotation and Transform should all be set for Linear.

As a last resort, create a tiny cube object, set the pivot point to align with your nozzle petal.

Link the petal to the cube, remove all keyframes from petal, then animate/keyframe the cube as desired with keys at least at 0 - 50 - 100.

Assign throttle0 to the cube via the Animation Tool. Test in sim.
 
Problem solved.

I assigned lever_throttle0 as an animation to my leading edge flap.

Using the 64-bit version of XtoMDL, no animation seemed to work, after replacing the F/A-18 exterior with the Phantom.
n4gix compiled my .x and .xanim files with the FSX XtoMDL and replaced the default Learjet's model with my Phantom. The flap animated perfectly, in accordance with the throttle input.
I tried installing my "corrupt" MDL to the Learjet: the flap/throttle that didn't work on the F/A-18 worked on the Learjet (and 737 and RFN Etendard).

Strangely, though, wingfold doesn't work in any case, but I'll try and find what else is at work here.
 
Alexis,

In Gmax, we found that sometimes Scales would not clear when parts were attached to other parts.

Here is a way to test this theory. Save a separate model. Disconnect all the parts around the flaps. Start resetting scale on each part. When you are done, save. Resave as next model up and start attaching Hierarchies again. Compile and test.


Bill
 
Alexis,

In Gmax, we found that sometimes Scales would not clear when parts were attached to other parts.

Here is a way to test this theory. Save a separate model. Disconnect all the parts around the flaps. Start resetting scale on each part. When you are done, save. Resave as next model up and start attaching Hierarchies again. Compile and test.


Bill

Indeed, the same applied to my case. I stumbled upon it, unlinked and scaled. But after linking them, scaling problems appeared again after applying an animation.
I kind of see a pattern in this problem, but I'll do a little test tonight to see if exporting with a scale error of [1,1,1] plays the animation properly. If it works, I'll just ignore the error.
 
In regard to testing the model with a scale error of [1,1,1].
The animations worked, as long as the problematic parts weren't linked to one another.

My guess is that this error is not important, and similar to the [-1,-1,-1] caused by using the mirror tool.
 
Why are you scaling anything at all in your project? I noted that you had what I assume is the source .max file, and another that is scaled, presumably for export to FSX.

Scaling in Max or GMax is an operation that should only be done at one of the sub-levels, and not on the object itself...

...and most especially should never be done on animated and/or Linked objects!
 
Scaling in Max or GMax is an operation that should only be done at one of the sub-levels, and not on the object itself...

...and most especially should never be done on animated and/or Linked objects!

I'm only scaling at a subobject level, but I'm still getting those errors.
While the scale error doesn't appear when the object is immobile, when animated (even with a reset transform/scale) the error appears.

My animations even get messed up sometimes without an error appearing (i.e. wingfold is perfect at 0 and 100%, but follows a strange rotation pattern, even though I rotate it around its local Y axis. Same for some nozzle petals).
 
I think Bill Leaming is asking, if your primary source file, your master, main copy, is a different scale?

You should have your constant scale model the actual scale size. I think that is what Bill Leaming is saying. I do not believe you lose any scale detail by having the model at proper scale and not oversize.

With FS2004, we made oversize models to get around the scaling issues where we wanted super nice detail in the mesh (auto-weld was messing things up). With FSX/P3d, we no longer have auto-weld, so no reason for oversized models.


On a second note, models not resetting, I remember having issues with parts a couple of years ago, and could not get them to work right. I ended up redoing the parts and moved on. It was a mess, trying to get them to work, and do not remember the details. In talking about it here, I found many people also had the same issues. One was the guy that does FS planes of Star Wars vehicles, (I cant remember his name, arrgh). He also was encountering this.

So you might try redoing the parts real quick, and check in the sim and see if that helps.


and stay away from bones!!!!! ;)
 
These strange rotations are usually fixed by using a Linear controller for rotation (and position, if necessary).

And you will need to have keyframes at least every 90 degrees, if not every 60 degrees.
 
Back
Top