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

New tool - 'mdldefGUI', a multithreaded XtoMDL compiler

DragonflightDesign

Resource contributor
Messages
1,389
Country
northernireland
Uploaded a few days ago with Arno's permission. From the readme:

"mdldefGUI is a multi-threaded front end for P3D’s XToMDL compiler. It is based on using the P3Dv4.x-onwards version of XToMDL so does not have the deprecated /NOGUI, /BATCH and /NOCRASH flags as options. It allows the storage of unlimited ‘projects’ and can compile up to three modeldef.xml files simultaneously. It will also allow you to abort any one of the three running threads at any time and because it is multi-threaded, the GUI never becomes unresponsive. It also runs a lot faster than XToMDLGUI because it is not restricted by having to update the GUI on the compiler thread.

The three compiler windows have different colour schemes to give a quick indication of which compiler you are looking at. The main window is also resizeable. When the compiler starts it copies all the required files into a temporary directory in the main folder - this means that you can continue to work on the original modeldef.xml file while the copy is being compiled. When the compile is complete it moves the .mdl file to the folder specified in the project settings.

As mdldefGUI makes temporary copies of the files needed to run on each compiler thread, you can point the paths at different versions of the P3D XToMDL.exe file e.g. you have an .mdl built with 3DS Max 2020 and are converting it to 3DS Max 2021 but you need to do modeldef checks along the way. You would create one project to point to the 3DS Max 2020 version of XToMDL and another project to the 2021 version."

It should be pretty bulletproof, but I'm equally sure someone will find some way of breaking it :rotfl:
 
Updated to v1.1. Fixed some GUI issues reported by a user.

Told you someone would find a way of breaking it... 🤣
 
Told you someone would find a way of breaking it...
No matter how much you test and now many people are in the dev/test team(s) the point of release will uncover bugs. Never fails. Usually happens within hours of a release.
 
No matter how much you test and now many people are in the dev/test team(s) the point of release will uncover new bugs. Never fails. Usually happens within hours of a release.
 
Back
Top