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

XtoMDL prerequisites

arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,547
Country
netherlands
One common issue when trying to compile objects using XtoMDL in ModelConverterX is that XtoMDL can throw very unclear error messages when the XtoMDL tool is missing one of its prerequisites. For example the FSX XtoMDL needs a very specific DirectX version to the installed and different P3D XtoMDL versions depend on different C++ redistributable package versions. For a user it is often not clear that the error throws is related to such a prerequisites.

In the last development release of ModelConverterX I have made a change. The tool will now check if the right prerequisites are installed before you use XtoMDL and it will give a clear error message (including a download link) in case something is missing. That should make it a lot easier to make sure XtoMDL is working fine.

There is one big catch, on my machine I had all the prerequisites installed already of course. So I was not able to test it well in a situation where things are missing. So if you encounter any weird situations where ModelConverterX reports invalid prerequisites where it shouldn’t or where after installing the prerequisites it still does not work, please let me know.

Continue reading...
 
Hi,
I don't know if I'm the only one but the latest version of MCX (MSFS) was working properly last week.
Since Sunday, with the last version on SceneryDeign.org, a diagnosis is made on a VC++ runtime (2015-2022) that is not installed, this installation do and after a reboot, this DLL is again requested: in a perpetual loop ...
MCX in this last version isn't usable.

PS: old versions (1.3 and 1.5) are fonctional
 
Lagaffe said:
Hi,
I don't know if I'm the only one but the latest version of MCX (MSFS) was working properly last week.
Since Sunday, with the last version on SceneryDeign.org, a diagnosis is made on a VC++ runtime (2015-2022) that is not installed, this installation do and after a reboot, this DLL is again requested: in a perpetual loop ...
MCX in this last version isn't usable.

PS: old versions (1.3 and 1.5) are fonctional
Click to expand...
Ok, let me check what goes on there. This is at start-up of MCX or when you export a MDL file?
 
I had another look at the code that checks if the C++ redistributable is installed and I think I see where it could have gone wrong. I have made a fix and a new development release will be online in about 1 hour. Hopefully that fixes it.
 
Hi,
Sorry, I have not seen your last answer (Yesterday 19:38). To answer to your question, the program was looping when "importing an OBJ file".

Today, I just downloaded the latest version: v1.6.0 DEV 8f020889 DEV 13/03/23 and the application opens correctly, the VC++ 2015-2022 library having been installed last night. This last revision seam to be fully fonctional :cool: : OBJ can be imported and exported in GlTF without any problem and no error message about VC++ librairies 👌

PS: During my troubles, I questioned my installation several times, I even uninstalled all the VC++ from 2005 to 2022 and proceeded to the installation of an old disk image dating from January 2023 just in case but I still had the problem so I went back to the loop problem.
 
Glad to hear the fix works fine.
 
Hi Arno,

The latest development version:
MCX error version.PNG


Throws this error for me:
MCX error.PNG


These are the runtimes that I have:
installed runtimes.PNG


This older development version does not throw the error:
MCX no error version.PNG
 
Hi Dave,

The checks for the XtoMDL dependencies have been added recently, so that explains why the older version does not show the error.

Did you try to install the version that the error messages links to? If you click on the message it will download an installer from Microsoft.

MCX check for version 6.0.2900.2180 of the C++ 2005 redistributables to be installed. Can you see which version you have installed?
 
Hi Arno,

The versions of the 2005 runtimes are:

the top one in the image of reply #9 is:
2005 version.PNG


and for the x64 runtime it is:
2005 x64.PNG


As these are higher version numbers, is this anything similar to the problems I had on a few occasions in the past as in this post ?

Shouldn't the version check be for a minimum version number?
 
Hi,

FSX XtoMDL is a 32 bit application, so it is the x86 redistributable that is used here.

When I check on my machine I see these two versions installed:

1679994310125.png


It seems the version you have is older than that. Did you try to install the redistributable with the download link that MCX provides?

I am checking for a specific registry key, not checking directly the version number. From what I found on the internet that is for version 6.0.2900.2180, but as you see I don't have that version installed myself either and I do not get an error on my machine.
 
Arno,

I've now installed the version from the MCX download link and all is OK.

I was confused about the difference between the installer version number and the version number shown in Control Panel.

Thanks!
 
You must log in or register to reply here.
Back
Top