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

Problem with 3DS Part Naming

tgibson

tgibson

Resource contributor
Messages
11,865
Country
us-california
Hi,

When I export an object as a 3DS object (even one that has no LOD's), I get part names like AA_LOD_100. When I then add another LOD to the model in GMAX (using dummy parts called Exterior_LOD_010 and Exterior_LOD_100) and link all of the parts exported by MCX to the Exterior_LOD_100 part, I get an object that looks and works fine in FS9. These objects have no animations.

But when I try loading the object back into MCX, the LOD with the parts named like AA_LOD_100 and also linked to the Exterior_LOD_100 part, that LOD object displays as "exploded" (random parts are rotated 90 degrees, etc.) and this is the way an exported MDL appears in FS9 as well. But if I rename those parts to names like AA_100 it then displays (and I assume exports) correctly in MCX.

So my suggestion to avoid this problem would be that if the object has no LOD models that in the exported .3DS model parts be named AA, not AA_LOD_100. Only if the model contains LOD models should they include the LOD_nnn extension. Either that or the importer needs some work. :)

BTW, these objects appear exactly the same in MDL Tweaker II, but a tweaked file in FS9 stlll displays OK in this case.

Until then I will use the workaround I found above, but renaming each part in a complex model is a very tedious affair...

Thanks,
 
Hi Tom,

ModelConverterX does not know objects without LODs. Each part always has a LOD and the default value is 100. Hence the naming when you export it.

I guess I could skip the LOD part in the name, when there is only one LOD in the object.

But I don't think it is weird that you have to rename these parts when you add more LODs later on.
 
I was just saying that they appear fine in FS9, but not in MCX or Model Tweaker II. :)
 
You must log in or register to reply here.
Back
Top