ModelConverterX 170 and 180 -Unable to Export Model

[Airfreighter14853]

I have been using ModelConverterX170 for quite some time, creating FSX models from 'dae' files from my Sketchup drawings. I recently upgraded my desktop hardware and now have Win11 instead of Win7 Pro. my MCX 170 loads a dae file OK, but if I try to export to MDL I get an error saying that Visual C++ runtimes are not installed! I have installed most recent Visual C++ files, and the older C++2005 files, apparently successfully, several times but MCX still insists they are not present.
With MCX 180, I cannot get the program to run! I get a brief flash of a 'Dos' window, which disappears almost immediately and then there's nothing!
Anyone have any idea where I'm going wrong?

 

[arno]

Hi,

I don't know which SDK you are using to export to FSX MDL? Depending on the XtoMDL version that you use you need a different version of the runtime files. This article gives an overview:

Which Visual C++ runtime files does XtoMDL use? | SceneryDesign.org

Also if you double click on the error message about the missing runtime files in MCX it will take you to the download page for the version that is missing.

As for MCX 1.8 not starting. Do you have the .NET 8.0 x64 runtime files installed on your machine? That version uses a newer .NET version than the older versions.

 

[Airfreighter14853]

Hi,

I don't know which SDK you are using to export to FSX MDL? Depending on the XtoMDL version that you use you need a different version of the runtime files. This article gives an overview:

Which Visual C++ runtime files does XtoMDL use? | SceneryDesign.org

Also if you double click on the error message about the missing runtime files in MCX it will take you to the download page for the version that is missing.

As for MCX 1.8 not starting. Do you have the .NET 8.0 x64 runtime files installed on your machine? That version uses a newer .NET version than the older versions.

Thanks for the response. Arno - I'm using the SDK that came with my FSX De-luxe Ed'n discs.
I've used the 'double-click on the error message' link o get the C++, but even after I've installed from that link my MCX complains of the non-installation of the runtimes!

I have installed the .Net 8.0 x64, but I've still got the problem! I think it just doesn't like me!

 

[Airfreighter14853]

P.S.

I currently have, listed as installed on my system, the following C++ versions;

MS Visual C++ 2005 Redistributable (x64) (v8.0.61000)
MS Visual C++ 2015-2022 Redistributable (x64) (v14.42.34433.0)

 

[arno]

The FSX XtoMDL is not a 64 bit application, so you need to download the x86 redistributable for XtoMDL.

As for version 1.8, do you have any error message? Maybe something in the Windows event log?

 

[tgibson]

I thought it was recommended to update the FSX SDK to at least SP2? Weren’t there problems with the original?

 

[arno]

I thought it was recommended to update the FSX SDK to at least SP2? Weren’t there problems with the original?

Can't remember that, but might very well be the case. For years now I am using the P3D v1 SDK when I want to make a FSX MDL file.

 

[Airfreighter14853]

I have SP1 and 2 for FSX installed. Was there a separate Service Pack for the SDK?

 

[Airfreighter14853]

Tried the link from MCX to get C++ runtimes again -downloaded x8 version , but when I try running it I get "Error 1935", with following info;-

Microsoft VC80.CRT,type="win32",version=8.0.50727.6195",PublicKey Token="1fc8b3b9a1e18e3b",proessor architecture="x86"

I also tried a download that provides ALL versions of C++ from 2005 to 2015/2022 packages in x86 and x64. Every version installed OK Except 2005 x86!

 

[tgibson]

FSX SDK SP2:

Microsoft Flight Simulator X SDK SP2

This is the official SDK package from the Microsoft Website for Flight Simulator X Service Pack 2.

flyawaysimulation.com

You must have the SDK from the disks installed first.

 

[Airfreighter14853]

Many thanks for this link, Tom.

 

[arno]

Did you figure out the redistributable? The FSX XtoMDL used the 2005 x86 redistributable.

 

[Airfreighter14853]

I've succeeded in installing the 2005 version using a "vcdist" program on my Flight Sim X disc. If I use the link from the Mcx program I get an error on installation and it fails, but now, having used the one on the FSX disc, I have every version of VC C++ redistributable runtimes from 2005 to the latest 2015-2022 in both x86 and x64 all installed on my system.
However, I still cannot get MCX to export my mdl file, as it still complains that C++2005 is not present!
Another oddity I have noticed with MCX is that I used to be able to assign a ".lm" texture to my window textures as a Night Map in 'properties in the 'Material Editor'. There does not seem to be the option to do this in my MCX any more!??

Screenshots show partial of my Installed Programs listing, and the Error I still get in MCX on trying to export model.

I've also acquired and installed both SP1a and SP2 for the SDK onto my system now, thanks to Tom Gibson's link.

 

[arno]

Hi,

What is the exact version number of the redistributable you have installed now? It looks like MCX might check for a too new version and therefore still gives the error that prevents you to export.

Adding night textures is still possible. It might be the attribute is now called emissive texture as that is the more common name.

 

[Airfreighter14853]

The 2005 (x86) version I have installed is 8.0.50727.42

There is a setting for 'emissive texture', so I'll try that if I can get MCX to make me a .mdl file eventually!

 

[arno]

Hi,

I have checked, MCX is looking if version 6.0.2900.2180 of the redistributable is installed, but I see you have a newer version 8.0.50727.42. So let me find out what registry keys match that version so that MCX will accept that one as a valid installation as well.

 

[arno]

I was mistaken by the version numbers (it seems file version numbers and redistributable version numbers were mixed up). MCX does check for the SP1 of the C++ 2005 redistributable files (version 8.0.50727.762), while you have the RTM version installed. So MCX does check for a newer version.

I also tried to download the installer that MCX links to and it installs without issues on my machine.

I did search a bit for the error 1935 that you get, that seems to be a general error when something does wrong with the MSI installer (e.g. .NET framework corrupt or Windows updates pending). So I am not sure if that helps a lot.

 

[Airfreighter14853]

Hi again Arno
I've tried a re-installation of ".Net 8" in both X64 (I have 64-bit Win 11) and x86, so both of these now show as installed in my programs list. Neither showed any problems during installation. I've also tried re-installing the C++ 2005 (x86) runtimes yet again, but still always get that Error message as shown in screen-shot below!

The 2005 (x86) runtimes are the only version I can't get to install!

 

[Airfreighter14853]

I have managed to get a download of an earlier version of MCX, as I thought it might be OK with my older version of the C++2005, as I have only got the version which comes up using the "vcredist" file on my FSX disc, and this is the one that MCX 1.70 rejects! I have now got MCX 1.30 (tried to find 1.5 but didn't find a download for it!)

The MCX 1.3 is a much simpler version than any I've used so far (my first version was 1.5, but I've lost that long since, with System software & Hardware upgrades), but it DOES accept my C++ 2005 files, and I've managed to get a ".Mdl. file successfully exported, put into a library, and placed on my ADEX version of the appropriate Airfield (EFKK, Finland). The model, when seen in FSX, does not show some of the textures correctly (all of the 'glass' in this model of EFKK Terminal is appearing as what looks like corrugated black sheet! Not at all sure what I've done wrong here!

Model as seen in 3D view in Sketchup

Model as appearing in FSX.

 

[arno]

You can find all stable versions of ModelConverterX here:

ModelConverterX - History

fsdeveloper.com

I am not sure in which version I added the check for the C++ redistributable. That was add since not having it installed gives weird errors from XtoMDL which are hard to "decode" for a normal user. If XtoMDL works fine with the version you have now, I guess I could modify the check to accept both the older and newer version of the redistributable.