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

FSXA Unhandled Exception Error When Exporting In MCX

Messages
1,239
Hi,

I don't understand why I'm getting this unhandled exception. This is the 1986 airport project that I'm currently working on. I'm using the convert and place object wizard to input my kmz file. One thing I've notice is that where it says Select file to convert, which is the input file, is that the location is totally different from where I actually had the input file, and I don't understand that. I've posted the log details below in a text file but I don't know if it tells anything. It says that "object reference not set to an instance of an object" But what exactly does that mean? Even the log details doesn't tell me anything. Here's a screenshot of what appears after clicking the Convert Button in MCX:


Unhandled Exception.jpg



Ken.
 
Last edited:
Please state the exact numeric version of MCX you are using (this does not look like a recent version from its GUI).

Hi Gary,

The version number is 1.9.2026.0307. It should be the latest because I just download and installed it last night.

[MCX install path]\ModelConverterX.exe > Properties > {Details) tab (...this will have info to help with a reply to your query)

MCX Path is installed in C:\Model Converter X folder. I don't see no Properties folder with detailed tab, so I'm confused here.

Does the scenery have a Tower with an Interior 3D model (like a cockpit in a user aircraft) ?

Not in this scenery. I have the 3D tower in another scenery.
 
Browse to C:\Model Converter X folder, right-click on ModelConverterX.exe > click Properties > {Details} tab

Post the MCX version # and date of that executable file.

Arno may need it.


BTW: My error; MCX' GUI does indeed look recent; sorry (tired from grappling for hours attempting to help someone).

GaryGB
 
Last edited:
Hi Gary,

Thanks for clearing that up. The version is 1.9.2026.0307. The date modified is March 7, 2026. I did google that issue and read over the troubleshooting steps. But so far, I haven't seen anything wrong. It's hard to understand how a graphics would have anything to do with this issue. But according to that search, it was reported. I have the Nvidia GeForce RTX-3060 and the driver version is 32.0.15.6614 and the date is November 5, 2024. Do I need to update this driver? By they way, I can upload my Sketchup project file if it's required but I'll probably have to upload it to MediaFire and post the link here.

Ken.
 
Feel free to post a link here in the public thread, a ZIP of the Sketchup file in question, so Arno has access to it.

On second thought, it is possible Arno does not have Sketchup installed, and would be more immediately able to process a Google *.KMZ, Collada *.DAE, or WaveFront *.OBJ.

Be certain to include the mapped Texture folder in the ZIP as well.


I do not use Nvidia hardware, so I cannot advise you about the drivers.

AVSIM FS web forums may have info on which recent Nvidia driver version is working OK with FSX / P3D.


GaryGB
 
Last edited:
Ken,

I don't use the convert and place wizard myself often, so I will try it with a KMZ file this evening to see if I also get an error.

ModelConverterX extracts the KMZ file to a temp folder, that's why you see a different path.

Gary, in the first screenshot Ken posted the version number is clearly visible. So no need to post twice asking for version details. That kind of posts do not help solving the issue.
 
I did not recognize in a tired glance at Ken' OP screenie, the significance of the prefixed path to MCX.

I then failed to see the suffixed "1.9.2026.0307-devrel" string at the end of the text in the MCX application Titlebar.


As I am only now becoming familiar with MCX' new GUI appearance, I had expected to see what I saw previously:

mcx_error_importing_blender_lts-3_6_13_blend_file-jpg.99384


...as in my other thread regarding MCX, wherein the MCX Titlebar does not (yet ? :scratchch) contain the import filename.

https://www.fsdeveloper.com/forum/threads/mcx-fails-importing-blender-blend-file.460749/unread

I see now MCX does put both the filename and MCX version with date in the Titlebar; that's a great help, thanks. :)

GaryGB
 

Attachments

  • MCX_Error_Importing_Blender_LTS 3_6_13_blend_file.jpg
    MCX_Error_Importing_Blender_LTS 3_6_13_blend_file.jpg
    98.4 KB · Views: 26
Last edited:
Ken,

I have been able to reproduce the error here and I will fix it in the next development release.
 
Ken,

I have been able to reproduce the error here and I will fix it in the next development release.

Thanks Arno. I've tried importing using the collada file into MCX and it seems to work okay. The problem is that I would have to create a placement file so that it would place the object in the correct location. But I forgot the correct code and that's why I used the convert and place wizard. One thing I guess I should have mentioned is that after completing the project, I've moved my object so that the origin is on the left side corner of the parking deck so that I could have a reference for the coordinates. I've wondered if that could have caused the problem but I had done this a couple of times in the past. I had forgotten to place the center of my map to the origin before starting the project. It lined up perfectly in google earth after double clicking the kmz file.

Ken.
 
Last edited:
Back
Top