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

ModelParts problems

J

Jean_L

Messages
98
Hi Arno,

I have a problem with MCX

When I merge an extra object into an MDL, this object is present as a separate "SceneGraphNode", which is perfect.

However, when I later re-import the MDL to add or delete an object, or add an animation, it often happens that the previous object is no longer separated but incorporated in whole or in part into another "ModelPart".

This which is a major disadvantage because it is no longer possible to separate it without using Gmax or 3DSmax.

Is there a way to avoid these mergers and keep separate objects?

Best
Jean
 
Hi,

XtoMdl will automatically merge parts that use the same material. I don't think we can prevent that. Unless you add a visibility condition, mouse rectangle or animation.
 
A work around is to use a unique name, for an identical texture. The name will keep the parts in separate nodes, until you are ready to collapse the arrangement, by re assigning the parts that use the duplicate texture.
 
This is indeed another solution.
In this case, one would have to create copies of the textures used by the different parts that use the same texture?
 
Yes, separate copies of the same texture. You mention an animation. As Arno says, if you add the animation first it will stay separate. It doesn't have to be the final animation, just one that can be used as a placeholder.
 
Okay, these solutions are far better to re-export the merged part in gmax or 3dsmax to ungroup them again.
Thank you for your help and advices
 
You can also just change the specular color slightly or so. Any material difference is sufficient to prevent the merge.
 
Yes, I had seen that by discovering split textures in the hierarchy editor.
This is another interesting track:)
 
Arno,

Can you split materials for parts that share them? I.e. change one part's specular color without affecting the rest of the parts using the same material?
 
I answer for what I practice.
No, I can not split merged materials, but prevent them from being merged by putting other parameters, for example colors, in the "material" used but keeping the name of the .dds file called for the "diffuse texture"
 
No, once they are combined MCX doesn't know about the parts anymore.
 
You must log in or register to reply here.
Back
Top