FSXA Unhandled Exception Error When Exporting In MCX

[kmanning]

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:

Ken.

 

[GaryGB]

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

See: https://www.fsdeveloper.com/forum/t...rror-when-exporting-in-mcx.460751/post-939224


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


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

If so, this is only one of the numerous possible causes of the general error message you see; however, Arno is best qualified to reply to this issue.

https://www.fsdeveloper.com/forum/threads/mcx-1-8-2025-1121-doesnt-load-certain-mdl-objects.460465/

https://www.google.com/search?q=site:+www.fsdeveloper.com+MCX+"object+reference+not+set+to+an+instance+of+an+object&sca_esv=57908ecadfb13611&source=hp&ei=8Xa3aaf3HbSYp84Pof-RmQg&iflsig=AFdpzrgAAAAAabeFAbyTb53m9v3IXZz7qjd6HPKlSUJt&ved=0ahUKEwjns7mVu6OTAxU0zMkDHaF_JIMQ4dUDCBY&uact=5&oq=site:+www.fsdeveloper.com+MCX+"object+reference+not+set+to+an+instance+of+an+object&gs_lp=Egdnd3Mtd2l6IlNzaXRlOiB3d3cuZnNkZXZlbG9wZXIuY29tIE1DWCAib2JqZWN0IHJlZmVyZW5jZSBub3Qgc2V0IHRvIGFuIGluc3RhbmNlIG9mIGFuIG9iamVjdDIIEAAYBRgHGB4yCxAAGIAEGIoFGIYDMgsQABiABBiKBRiGAzIIEAAYiQUYogQyBRAAGO8FSIetAVAAWP6kAXAAeACQAQCYAYcBoAHmBqoBAzQuNLgBA8gBAPgBAvgBAZgCBaACpAXCAgsQABiABBiKBRiRAsICBRAAGIAEwgIGEAAYBxgewgIIEAAYBxgeGAqYAwCSBwMwLjWgB5E4sgcDMC41uAekBcIHBzMtMi4yLjHIB3SACAE&sclient=gws-wiz

GaryGB

 

[kmanning]

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.

 

[GaryGB]

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

 

[kmanning]

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.

 

[GaryGB]

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

 

[arno]

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.

 

[GaryGB]

I did not recognize in a tired glance at Ken's 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:

...as in my other thread regarding MCX, wherein the MCX Titlebar does not (yet ? ) 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

 

[arno]

Ken,

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

 

[kmanning]

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.

 

[kmanning]

Hi,

I just happen to be wondering if a component in a Sketchup project would cause problems when exporting and importing projects from Sketchup to MCX. I happened to google that and I happened to find out that it will cause problems. Is that true? In my project, I have several components, one being terminal C, one being the parking deck, one being the rounded parking deck you see at the back side of the parking deck, one being terminal B, one being the crosswalk from the parking deck to the terminal. I guess I have about 5 or 6 components. Since I've read about this, I'm thinking now that I need to explode each of the components before exporting that my project. Am I correct about this?

Ken.

 

[GaryGB]

IIUC, Arno was able to review his code solely based upon your description in the OP above, and subsequently found a bug.

If you link to a current build of the scenery object(s) in question, we can see what else may also require troubleshooting based on your latter descriptions in this thread.

If they are topically not directly related to the issues in the OP above, IMHO, it may be best to move the latter inquiries into a separate thread.

IIUC, making that determination would first call for Ken posting a link to the objects in question.

If there are concerns regarding object placement, we would need to see the related project placement BGLs and/or their XML source code, along with the 3D model objects and their mapped textures.

I would assume we may find out whether MCX has issues with import of 3D models in KMZ files that are still in a "Component" format native to the sketchup environment.

IIRC, MCX has always been able to successfully import KMZ files regardless of whether they contain 3D models that are still in a "Component" format native to the sketchup environment.

However, IIRC, according to a reply to a question I posed to Arno years ago, MCX disassembled 3D models into code, then reassembled them after processing to optimize nearly all aspects of geometry and texture mapping, but not performing draw call minimizing without explicit permission being granted via a specific part of MCX' GUI.

Thus, during import, Sketchup 3D models which were either Components or that were simply Grouped, essentially got "Blowed Up Real Good" (SCTV 'Farm Film Report' terminology) / 'exploded' (Sketchup terminology).

IIUC, that older processing sequence was later changed in MCX to retain the Sketchup native attributes of Components and Groups as well as BoundingBoxes (and CrashBoxes in other 3D models that are not a native Sketchup attribute).

Arno has thus far not explained in detail, exactly what changes are imposed by MCX on Sketchup 3D models which are either Components or that are simply Grouped, so this may be an opportune time for Arno to explain the current processing of those types of Sketchup-generated objects.

I also recall there were past issues with MCX processing of Collada *.DAE files, but not those contained inside the ZIP-packaged KMZ file format.


However, those issues were resolved by updates to the Assimp 3D model exchange file inter-conversion library which MCX now uses for internal processing during imports.


Back to the task of 3D model placement, there are numerous ways to do that, some of which involve use of MCX, and many which do not.

Do you still need to place- or 'correct' placement coordinates- for 3D models in your KBHM project ?

GaryGB

 

[arno]

Hi Ken,

The exception you got had nothing to do with the content of your model. It would have happened to any model as long as the option to convert the textures was enabled.

Or do you mean you have another issues on import now?

 

[kmanning]

Hi Arno,

I knew the exception had nothing to do with the content of my model in Sketchup. But when I would export the model in MCX with components. it would give me warnings regarding textures and how they were aligned. So, I exploded all the components in Sketchup and tried the same thing again. This time, I did not get any of the warnings when I export in MCX.

Ken.

 

[GaryGB]

Uh-Oh... that suggests MCX has issues when importing Sketchup project KMZ files containing Sketchup Components.

Does MCX have issues when importing Sketchup project KMZ files when Groups (but not Components) are used ?

I am asking this for all of us in general, and due to my own future interest in developing a workflow to create MSFS SimPropContainer object 'Primitives'.


FYI: If you have used any kind of true Sketchup Component [there is more than (1) type], these can be converted into simple Groups before KMZ export.
However, I wouldneed to know qhich type of Sketchup Component you are ysing, before I recommend a specific plugin so that it has the becessary features and capabilities to successfully convert your Components into simple Groups.

There are a few Ruby plugin scripts which can do this on your behalf instantly if not sooner, and the resulting KMZ is likely to be imported by MCX properly.


Please state what you are using, and if you are attempting to process 3D models with 2-way import / export via MCX between Sketchup and FS2Kx BGLs.

GaryGB

 

[arno]

I knew the exception had nothing to do with the content of my model in Sketchup. But when I would export the model in MCX with components. it would give me warnings regarding textures and how they were aligned. So, I exploded all the components in Sketchup and tried the same thing again. This time, I did not get any of the warnings when I export in MCX.

I you have more details about the exact error message and maybe a sample COLLADA file I can check what these errors mean.

 

[arno]

The new development release I put online today contains the fix for this error.

 

[kmanning]

Uh-Oh... that suggests MCX has issues when importing Sketchup project KMZ files containing Sketchup Components.

Hi Gary,

I'm not sure if this post was directed to me or Arno but I'll go ahead and reply just in case. I hope I'm not making things too confusing but regarding the components that I've talked about and the warning errors I was getting in exporting the contents of the model in MCX occurred when using dae or collada file, not kmz, since I was never able to export them due to the bug in MCX. I'm not suggesting that exporting the model in MCX with components actually caused the warning in the event log. I'm just saying that after I exploded all the components in my model no longer gave any warnings in the event log in MCX. I hope that clears it up.

Does MCX have issues when importing Sketchup project KMZ files when Groups (but not Components) are used ?

I haven't tried it using groups but I can try it if you want me to.

However, I wouldneed to know qhich type of Sketchup Component you are ysing, before I recommend a specific plugin so that it has the becessary features and capabilities to successfully convert your Components into simple Groups.

When I mentioned components in my model, these are the ones I've created in Sketchup. Take the terminal for example, I would make that a component. Then when I make my parking deck, I would make that a component. Then terminal B as a component. I did it that way to make some things a little easier for me. But after completing the model, one can just simply save the model with componets in a certain name, then explode all the components and save it with a different name, if components are a problem when exporting them in MCX. I do admit that I think some of my textures are slightly misaligned, many times due to making copies, and for some reason get misaligned. That could be the reason for the warnings in the event log.

Please state what you are using, and if you are attempting to process 3D models with 2-way import / export via MCX between Sketchup and FS2Kx BGLs.

I'm not sure what you mean.

I hope this clears things up.


Ken.

 

[kmanning]

I you have more details about the exact error message and maybe a sample COLLADA file I can check what these errors mean.

Okay. Let me export the model with the components and I'll post it with the warning messages. It seems that there is a button that allows me to make a copy of the event log. I'll post it too.

Ken.

 

[kmanning]

Hi Arno,

Here is the event log warnings, a screenshot, and the collada file:

Ken.