• 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 High Poly Model

Messages
1,749
Country
unitedstates
My latest projects has 199K poly for the exterior and 206K poly for the interior.
The exterior exports with no issues. The interior is always missing random parts.
I do not get an error message that i have reached the 65K texture mapping limit. So i believe this is not the issue.
Why would the interior with slightly 6K over 200K fail to write all parts? Is there a 200K limit? Or is there another issue?

Using 3DS Max 2016 with the latest XtoMDL UI tha includes the FSX_GmaxGamePack XtoMDL converter.

Also does anyone have the P3D V1.4 XtoMDL. I can't find my copy. Thanks. Is this still the last version that works for FSX and P3D?
Exports fine using P3D V4 XtoMDL and only loading in P3D. So it's my FSX model that needs help.
 
Last edited:
Update:
I found that it does not matter how many poly's i have. It seems to be my animated parts total causing the issue. If i export less animations all parts show. And the only parts that were not showing were animated.
So what is this limit?
 
Why would it be a polygon limit? Have you exported a functional animation?
 
Mark, I ran into this animation limit with the B737-200C. I wound up converting all of the two position switches to static objects of the on/off positions and used <Visibility> scripts to control them. The reason I chose this type of switch is that the all shared the same texture.

It was extremely frustrating since the animated objects that failed to show up in the sim apparently were randomly chosen. I never did discover what the absolute number of animations is when compiling for FSX.
 
I wound up converting all of the two position switches to static objects of the on/off positions and used <Visibility> scripts to control them.

That is genius as it will only look like a snap animation now but is actually using visibility for the 2 positions. :stirthepo

We found a ton of unneeded animations like the floor light switches or the pitot/static selector or the floor to windshield vent. These are all dummy lever and switches. This also may cause less FPS so maybe i should be using so many animations.
 
Last edited:
From memory, it’s around 500 animations.
I have a total of 594 animation. I will try to lower to 500. This may be correct.

Update:
580 works and 581 does not.
I am not sure if it's only a total of the animation list or a combination of the part count assigned to the total animations. That is a answer that some may want to know.
I believe its the total animation list only. Because 576 is working every time.
 
Last edited:
Update:
We found that the animation list of 581 limit was not the correct science. We had different values under under 581 work. So we have been looking at the Xanim file size. We noticed 538KB is near the limit as well.
 
Last edited:
Update: :p

I no longer see the message buffer size exceeds maximum limit. I have takes large groups and re grouped into smaller groups. I removed all duplicate names for non animated parts. Some may have been linked to animated parts. And now i have gone from 581 animates to around 643. I am using aftermarket gps units and that is why so many animations. I do see to 1 or 2 parts that will not show from recent groups that i work on even if i rename the group name a lower value. So it seems the project is so close to exporting perfect but it always likes to leave 1 or 2 parts out. And this time its the largest group the main panel. And i can't split this group up. So i un grouped all groups inside. Now only a few annunciator lights will not show.

So close!:banghead:

The reason i did not see this message was because i started to use the V1.4 XtoMDL. (buffer exceeds maximum size) The gmaxgamepack will show this message. So i wonder if i have to figure out which groups are causing this large buffer?
 
Last edited:
I am only missing about 14 visibility Annunciator parts. I wonder why its only these types of parts now? When i export less parts these missing parts showed up. Arg!:banghead:

Update:
By welding parts like static buttons where there was a bunch of them did the trick. So it seems if you are heavy on animations you can get the total parts list lower to export a complete model.:eek:

I also noticed that if i removed a lot of groups that had no or little animations this made no changes. So this kept me thinking it was the animations total. I tried other groups and the 2 that did work had the large amount of static buttons. So by welding these buttons together in each group seems to be the solution.

So my believe is on large projects keep the overall total parts list low by welding static parts that share the same texture mapping.:stirthepo
 
Last edited:
Don't know about 'welding' but you can save huge numbers of discrete parts by 'attaching' them so that they form one part, provided they address the same material. Then, should you need to go back to what had previously been a separate part use the 'element' subpart function to re-isolate them. Naturally, this wont work for animated parts. Well, I guess you knew all this.
 
Don't know about 'welding' but you can save huge numbers of discrete parts by 'attaching' them so that they form one part, provided they address the same material. Then, should you need to go back to what had previously been a separate part use the 'element' subpart function to re-isolate them. Naturally, this wont work for animated parts. Well, I guess you knew all this.

Weld is just another term for attach because they are both are creating 1 part and you have to attach 2 parts first anyways to weld. And yes if you click the element you can select each separate part that was attached previously. If you actually weld 2 parts using vertex or edge then element will no longer work unless you set different material ID's. And you must weld them water tight to be considered welded. Just attaching 2 poly's will not work. So you can use the term weld or attach if you are referring to combining 2 parts into 1 part. But technically what i am doing is attaching parts to save on the total part list since i am not going to weld these parts together. So attach is the correct term in this case. Most developers would recognize both terms and know they are the similar procedures no matter how many steps your connection is. :teacher:
 
Last edited:
Sorry, this makes no sense to me at all. Welding and attaching is the same thing, and then it isn't? Not that it's terribly important...
 
True, true; I knew what he meant even if it wasn’t exactly what he said. I had a bunch of panel screws modelled and mapped which slowed CFS down. The answer was to Attach them to each other in Gmax and park their textures in a corner of a main texture sheet. Carry on!
 
Hi,

My understanding:

Attaching means combining two objects into one. Welding means taking two meshes within same object and making them a single mesh.
 
Hi,

My understanding:

Attaching means combining two objects into one. Welding means taking two meshes within same object and making them a single mesh.

Yes that is correct. Both take 2 parts and make 1 part. That is why i have a habit to call it welding even if i am only attaching.
 
Sorry, this makes no sense to me at all. Welding and attaching is the same thing, and then it isn't? Not that it's terribly important...

No they do not do the same procedure weld is a second step after attach so it still uses attach but they both take 2 parts and make 1 part. And its called weld. I use the term welding for both attach and weld terms. That is where the confusion is.;)
If you read post #13 i quoted "So attach is the correct term in this case." I just like to use "welding" not weld or attach as a term.:teacher: In the future i will only use attach as the term if i do not weld poly's together.
 
Last edited:
Try this, understanding that it can only be used on parts not already linked to anything else. Create a dummy node at 0,0,0. Link one of the offending parts to it and see if it shows.
 
Try this, understanding that it can only be used on parts not already linked to anything else. Create a dummy node at 0,0,0. Link one of the offending parts to it and see if it shows.
The parts that will not show are changing each time i work on the project. Most of the time its from the highest named group. Or if not that group its always the main panel. I took the simple 4 poly part that have a vis tag and linked it too a box i just created and the part still does not show. If i remove the tag then it shows. So it seems to be a model.def total not a animation or poly limit.

Next test i added the rear gear which is not needed. I wanted to see what happens since it has a lot of animations. Almost all of the parts did not show including the parts from the main panel. So i think i have too many model.def codes for this xtomdl. Works with no issues in P3D V4.

Next i removed another set of annunciators to see if that would free up space on the visibility codes. And the few parts still will not show when i press the test switch. And of course they work if i export 20% less of the project.
 
Last edited:
Back
Top