FSX Error with ModelconverterX 1.70 for FSX

[Franzi]

I can't open an FSX MDL file. Thank you for your answers.

 

[PhotoBird]

I am also having a problem with an Error Handler message. Mine is occurring at startup. Uninstalled my older v. 1.5, installed v. 1.7 and still got the Error Handler message and no startup. I'm running Windows 10, have MS .NET Framework version 4.8.9093.0 and C++ Redistributable 14.38 installed. Graphics card supports OpenGL. Also, I deleted the config files in AppData. MCX was working OK last time I used it... Same OS, same .NET Framework, and same C++ Redist. Any suggestions on what to do next would be appreciated.

 

[GaryGB]

Hello:

I suspect that both of the posts above involve use of MCX version 1.7x, and errors 'may' not occur if MCX 1.8x is used.

I run MCX version 1.8 on Windows 10 Pro with multiple versions of FS BGLs / MDLs and/or 3D model types with no such errors.


Please download and test MCX version 1.8 instead (Arno tests his coding extensively before posting a "development" version):

https://www.fsdeveloper.com/forum/threads/download-modelconverterx.14215/

https://www.scenerydesign.org/development-releases/


https://www.scenerydesign.org/latest-release/modelconverterx_latest_development_release.zip


I also suspect that at least (1) of the posts above might involve attempted use of SCASM / ASM coded BGLs.

I believe that if that is the case, such SCASM / ASM coded BGLs may require "full" conversion for FSX compatibility.

In some cases MCX may fail to- or refuse to- decompile such SCASM / ASM coded BGLs, and simply throws an error message.


In such cases, one may use either of (2) available 3rd party SCASM / ASM coded BGL decompilers, and output source code.

When the output ASM source code is edited (often involving thousands of lines of code) MCX 'may' process it in useful way.

There is serious time required to learn how to work with SCASM / ASM code; IMHO it is best to use FSX MDLs ...in FSX.

GaryGB

 

[PhotoBird]

GaryGB, thanks for the reply. I downloaded and installed MCX v. 1.8 and I no longer get the Error Handler prompt but the program still doesn't start. I click the .exe file and I get a brief flash of an unexpanded black screen, and then nothing. I have the program files in a folder named "ModelConverterX" in C:\Program Files (x86), same location the program was in when it was working properly. I did get a Windows Defender prompt on which I chose "Run Anyway" so I'm pretty sure all the files downloaded. Any other ideas for troubleshooting?

 

[GaryGB]

MCX should be installed outside the Windows protected "system related" folder chain in a sub-folder on the root of the C:\ drive or other drive letter.

I have MCX on my D:\ drive, and I use a shortcut link that has compatibility / security propertIes set so that it always runs with Administrative permission.

Can you tell us what file(s) you are trying to import into MCX ?

GaryGB

 

[PhotoBird]

The FSX .mdl file was for a Japanese Kagero class destroyer pilotable/AI ship by Erwin Welker, originally a CFS2 AI ship by Usio No Ibuki. I wanted to attach stack smoke effects tp the funnels... Pretty simple little job I've done before with other FSX ships. I'm sure the file is workable, I just can't start up MCX to import it. I will relocate MCX as you suggested and we'll see what happens.

 

[PhotoBird]

OK... I moved MCX to its own folder in my C:\ drive, main folder "ModelConverterX" with 90 files and 9 folders inside (see pic). Restarted my PC. Same results as before when I click the .exe file, both directly in the folder and from the desktop shortcut: brief flash of small black screen and then nothing.

 

[GaryGB]

I am also having a problem with an Error Handler message. Mine is occurring at startup. Uninstalled my older v. 1.5, installed v. 1.7 and still got the Error Handler message and no startup. I'm running Windows 10, have MS .NET Framework version 4.8.9093.0 and C++ Redistributable 14.38 installed. Graphics card supports OpenGL. Also, I deleted the config files in AppData. MCX was working OK last time I used it... Same OS, same .NET Framework, and same C++ Redist. Any suggestions on what to do next would be appreciated.

View attachment 97551

Hi again:

Sorry I did not initially notice your old .NET version.

Nor did I initially recall the precise .NET 8.x et seq. version number Arno imposed as a dependency for 'recent' builds of MCX.

See these prior posts by Arno:

https://www.fsdeveloper.com/forum/threads/model-converter-x-will-not-open.459813/post-932456

https://www.fsdeveloper.com/forum/threads/modelconverterx-not-opening.449032/post-855393

https://www.fsdeveloper.com/forum/threads/mcx-installation-requirements.439316/


NOTE: I normally leave it up to Arno to reply to such posts regarding fairly well-defined failure-to-run scenarios involving his utilities.

Historically, Arno tends to take an extended vacation in August, so he has been noticeably absent of late, so I decided to try and help.


.NET is a mixed blessing and P.I.T.A.; we have been nagging Arno for some time to do what all professional programmers do:

list all dependencies on download pages.

Try Arno's .NET link in the post cited above, and see if a newer version is now being made available by MS for Windows 10.

All that is needed is the "Run Times", and not an entire installation of .NET, since MCX only runs on windows to work with a windows-only Flight Simulator.


So, I would probably download this version of .NET if you use a 64-bit version of Windows 10:

https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/sdk-8.0.413-windows-x64-installer


...or this one, if you use 32-bit version of Windows 10:

https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/sdk-8.0.413-windows-x86-installer


Most .NET and other core run times such as Visual C++ / Visual Studio etc., require a restart of Windows to "Register" the run time DLLs; do that, then try MCX again.

https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170


As for any requirements MCX may have for other windows "run times", perhaps Google AI can do what Arno has been reticent to do:

https://www.google.com/search?q=site:+www.fsdeveloper.com+ModelConverterX+Visual+C++requirement&sca_esv=b36dbb310cba81e0&ei=WpiuaK_4HpikptQPw9LmyQU&ved=0ahUKEwivjezhoaqPAxUYkokEHUOpOVkQ4dUDCBE&uact=5&oq=site:+www.fsdeveloper.com+ModelConverterX+Visual+C++requirement&gs_lp=Egxnd3Mtd2l6LXNlcnAiP3NpdGU6IHd3dy5mc2RldmVsb3Blci5jb20gTW9kZWxDb252ZXJ0ZXJYIFZpc3VhbCBDICByZXF1aXJlbWVudEjhQVD2FViDNXABeAGQAQCYAc0BoAGwB6oBBTYuMi4xuAEDyAEA-AEBmAIHoAKsBsICChAAGLADGNYEGEfCAggQIRigARjDBMICChAhGKABGMMEGAqYAwCIBgGQBgOSBwUxLjUuMaAHoRiyBwUwLjUuMbgHlwbCBwUyLTEuNsgHRA&sclient=gws-wiz-serp

I hope this proves successful.


Arno:

The average person does not go the extra distance required- or know where to hunt- for info on requirements of run times that your utilities are dependent upon.

Please post them clearly on separate version-specific download pages, and update the 2017 'sticky' thread in the MCX forum:

https://www.fsdeveloper.com/forum/threads/mcx-installation-requirements.439316/


GaryGB

 

[GaryGB]

BTW:

https://simviation.com/1/browse-Misc-58-38

https://simviation.com/1/download?file=Pilotable1919destroyer_USS-Cole-1.zip&fileId=45410

...shows it to be a SCASM / ASM 3D model that imports to MCX with numerous Event Log status messages and Variable prompts, although the download calls it a "FSX" object.


I am not certain how it actually is displayable in FSX, and if it can accept a FSX *.Fx- versus a SCASM / ASM- Effect for smoke.

Perhaps Tom Gibson may know more about fully converting such 'transitional' legacy 3D models of "pilot-able" craft to FSX format ?

GaryGB

 

[tgibson]

Sorry, I’ve never tried to convert a file older than an FS 98 file.

 

[GaryGB]

Sorry, I’ve never tried to convert a file older than an FS 98 file.

Although Combat Flight Sim 2 was a modified version of FS2002, MDL format(s) used involve "Highly Uncommon Strangeness".

The so-called "FSX" MDL shows this in the header when viewed in NotePad++:

RIFFäf8 MDL8MDLH    H  ”d8 <       (   ¶   FS90   DICT¤     ˜      ´ì$ÆA¹wØzL•Dè   œ      ¤}»ßþGÞ T–*™±          àçâ’©¢©AŒ(î62K’   ž      R‰:–µ¡A@¼{„½¸pK“   š      Í(
Ÿ§E®    ›
°¶ƒæ   ¤      )7±ØüáŠF hæßK¿Ê   ¢      “j .WúÇM w±öö   ®      ¥}»ßþGÞ T–*™±   ¬      áçâ’©¢©AŒ(î62K’   ¨      S‰:–µ¡A@¼{„½¸pK“   ª      Ì(
Ÿ§E®    ›
°¶ƒæ   ¦      (7±ØüáŠF hæßK¿Ê   °      ’j .WúÇM w±öö   ²
èoûFKL²ŽÌ—D   ´      ý%×yÌKB…¬Ôv%{r3BBOX$                                       ISFT<   MakeMDL - Microsoft© Flight Simulator 2002 (8.00.010912.01) BGL

Somehow as a (hacked ? ... "FSX" compatible ?) MDL, the author(s) have managed to implement FSX *.FX Effects via Aircraft.Cfg.

The OP 'may'- or 'may not'- be able to use an AttachPoint for a FSX Smoke Effect at the smokestack part of the 3D model.


This is so far out in left field, I doubt most FS Developers familiar with this unusual type of MDL still remember 'breakfast'.

Good Luck to the OP with this fascinating- but undocumented- aspect of FS innovation.

GaryGB

 

[PhotoBird]

GaryGB, the former CFS2 Kagero DD shows up OK in FSX-SE (see attached). If the .mdl file displays in MCX when I get it working remains to be seen. I am about to act on your recommendations from yesterday's post for getting MCX to start, but I have one question. My computer's system profile shows multiple installs of earlier .NET Framework (see other attached). When I update the .NET Framework per your earlier post can I uninstall these?

 

[GaryGB]

My recommendation is leave the older .NET run times installed (they do not take up much space), as some apps may need them.

MS says new run times are retro-compatible / comprehensive, but sometimes they are not, and instead close doors to older apps.

MCX, 'used' to depend on .NET 2.0, which MS quit distributing in Windows, and we had to download it manually.

Now MCX depends on newer versions of .NET, so we must manually download those run times ...still not included in Windows.


Let us know if the .NET update gets you up and running with the latest MCX.


PS: Rather impressive what the author(s) of that original CFS2 ship were able to do; with MCX we can do amazing things too.

GaryGB

 

[PhotoBird]

GaryGB, have installed the following .NET/Runtime/C++ files per your earlier post:
.NET SDK 8.0 Visual C++ Redist 8.0.413 (x64) which I thought had all that I needed, but...
I also installed Visual C++ 2015-2022 Redist 14.44.35211 (x64) as it was the last stand-alone C++ package MS had listed.
Now I no longer get the quick-flashing black screen but I get a detailed "Fatal Error" message (see attached) which I'm pretty sure is being caused by one of the items I installed.
Can you pls tell me again what I need to have installed for MCX v. 1.8 running as I think I have messed things up at some point. Sorry for being dumb about this

View attachment 97560

 

[GaryGB]

GaryGB, have installed the following .NET/Runtime/C++ files per your earlier post:
.NET SDK 8.0 Visual C++ Redist 8.0.413 (x64) which I thought had all that I needed, but...
I also installed Visual C++ 2015-2022 Redist 14.44.35211 (x64) as it was the last stand-alone C++ package MS had listed.
Now I no longer get the quick-flashing black screen but I get a detailed "Fatal Error" message (see attached) which I'm pretty sure is being caused by one of the items I installed.
Can you pls tell me again what I need to have installed for MCX v. 1.8 running as I think I have messed things up at some point. Sorry for being dumb about this

View attachment 97560

.NET, Visual C++, and Visual Studio are separate run time file groups that are downloaded ...separately

I assume you have a multi-core CPU running Windows 10 64-bit (aka an "x64"- and not a "X86"- version), so:

dotnet-sdk-8.0.413-win-x64.exe is the only known MCX version 1.8 required update clearly communicated by Arno thus far.


This is what I get when I click on the attachment link in your post above:

"Oops! We ran into some problems.

The requested page could not be found."


Please remove and reattach the screenshot you cited on your reply above.


NOTE: Do not install the newest release of MCX on top of any prior release; use a separate folder it.

I maintain older MCX installs side-by-side as MCX version numbers vary in success if importing SCASM / ASM FS objects.

You may need to do this also, since you work with older FS version objects.


FYI: I name my MCX folders with a release date such as "MCX 06-09-2025".

GaryGB

 

[PhotoBird]

GaryGB, thanks for the additional info. I'm going to start all over again with MCX version 1.8 and see if I can get it running.
In the meantime here is the black-screen "fatal error" message I got last night. Hopefully you can see it on this post.

 

[GaryGB]

Hi again:

Do you know which numeric version of OpenGL graphics drivers is installed for your video card (aka "GPU") ?


It would also help to list your CPU, GPU, Motherboard mfgr. / model / revision number here.

If this is a specific commercial computer model with a part number that has not been modified since it was purchased, you could list that instead.

GaryGB

 

[PhotoBird]

I reinstalled all files for MCX v. 1.8 per your post above and Arno's readme in the v. 1.8 download. Put MCX in its own folder in C:\ drive. Still getting same black-screen error as last night: "Fatal error, blah-blah... External component has thrown an exception." I have no clue what external component could be causing the problem as v. 1.7 worked fine last time I used it. My computer is a home build and here are my current specs:
Operating System: Windows 10 Home (x64) Version 22H2 (build 19045.6216)
Processor: 2.50 gigahertz Intel Pentium Dual-Core E5200
64 kilobyte primary memory cache
2048 kilobyte secondary memory cache
64-bit ready
Multi-core (2 total)
Not hyper-threaded
Motherboard: Gigabyte G41M-ES2L
GPU: NVIDIA GeForce RTX 1070 with driver v. 580.97 released 8-12-25
(GPU is new since last month)
Open GL set to "performance" preference
Pic of black-screen error attached.

 

[PhotoBird]

Could the location or ID of the SDK be a problem? I am running FSX-Steam Edition and there is a SDK folder in the game files. I've run MCX versions 1.5 and 1.7 working with FSX-SE and never had a problem until v. 1.7 stopped working a few days ago and I posted here. I am frustrated that I can't fix this.

 

[GaryGB]

Could the location or ID of the SDK be a problem? I am running FSX-Steam Edition and there is a SDK folder in the game files. I've run MCX versions 1.5 and 1.7 working with FSX-SE and never had a problem until v. 1.7 stopped working a few days ago and I posted here. I am frustrated that I can't fix this.

The FSX_SE SDK was never a real entity, and was never licensed, and is incomplete; do not attempt to use it, or link locations of SDK executables to it in MCX or ADE etc.

Download and use Prepar3D version 1.4x SDK with FSX and P3D (all FSX SP2- and most P3D- versions tolerate scenery compiled via P3D SDK v1.4x with few exceptions).

https://web.archive.org/web/20230504011627/http://cloud.prepar3d.com/SDK/Prepar3D_SDK_1.4.4747.0.exe


This is a rather obscure scenario, and it might still prove to be due to a coding issue that only Arno may sort out.

I did not see any notice as to when Arno is returning, but I have read that burglary is a problem in some parts of Netherlands, so folks there do not post that info online.


I am also always suspicious of 'new' Nvidia drivers, but it could also be an obscure AnyCPU versus x64 Windows .NET configuration issue in Windows on your hardware.


But, you may also require an updated install of DirectX 9.0c, since it is not included with Windows 10 et seq.; it will 'refresh' any existing installation of DirectX 9.0c.

SDK XtoMDL compilers require DirectX 9.0c, and it may be that MCX' .NET forwards a missing DirectX error message in a obscure way as Arno has no error handler for it.


DirectX 9.0c runtime installer links are here:

https://www.fsdeveloper.com/forum/threads/direct-x-error-with-mcx.456001/post-907645

https://www.microsoft.com/en-us/download/details.aspx?id=8109


I hope this works for you.

GaryGB