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

Merging MDLs with visibility problem

DaveWG

DaveWG

Messages
244
Country
england
Hi Arno, hope you had a good Christmas and New Year.

Yesterday, I encountered an odd issue with MCX. I was working on converting an old FS9 model to P3d native. That basic conversion worked fine, no problem there. Next I wanted to add some simple external stores with visibility controlled by payload weight. The parts were modeled & visibility conditions added, then the finished MDL was merged with the aircraft MDL in MCX. Results looked fine in MCX, but when the model was loaded into P3d all the animated parts seemed to be rotated 90 degrees and would not move. I reloaded the MDL into MCX, but the animations looked fine there. After some trial and error, I found that if I merged the parts without the visibility conditions, then added tagged them afterwards in MCX, the exported model worked fine.
 
Same here so I always sequence the workflow as follows:

- Check MCX Options > ObjectModel Settings > Optimize > CollapseModelParts=TRUE (I set this option to FALSE to isolate/strip modelparts but sometimes I get borked exports with this option at FALSE so I set it to TRUE before merging parts and exporting the aircraft MDL)
- Merge modelparts without viscons (make sure the materials properties are not the same as the ones already used in the aircraft MDL to prevent welding)
- Add attached effects without viscons
- Export the MDL
- Reload the new MDL
- Add the viscons
 
Last edited:
Yep, that's pretty much how I got around it. Seems odd that MSX will import, and display correctly, the mdl that P3d won't though.
 
Humm interesting findings. I'll see if I can reproduce it. Sounds like something gets messed up.
 
You must log in or register to reply here.
Back
Top