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

MCX Endless Loop and Exception

G

gadgets

Resource contributor
Messages
9,388
Country
ca-britishcolumbia
Arno, I'm using the latest development release of MCX.

Importing the .mdl file from the "canuck80.zip" available from avsim, flightsim and elsewhere causes MCX to go into an endless loop. Attempting to import the .sca file for the same model generated by Trevor de Stigter's MdlDisAs package causes an "index out of range" exception in MCX just before completion of the import process.

Thought you'd like to know.

Don
 
Hi Don,

I'll give that object a try and see what happens. Sounds like a nasty bug :).
 
That was fast!!!

Things aren't quite as I described. I started the conversion again and went for lunch. When I returned, the model had been imported - less the prop - with several errors noted in the log. I've repeated it several times since and it takes about 5 minutes. (The original FSDS model is only about 1mb).

Unfortunately, while the converted model displays (sort of) in the FS9 aircraft-chooser window, FSX refuses to display it. As well, SAMM "thinks" it has successfully converted the model (which means the file is in the right format - at least_ but the aircraft does not display as scenery.

So, while MCX eventually converts the original (FS2000) .mdl, the converted file still has a problem. I'll see if I can determine what is that problem from an analysis of the converted .mdl file.

Don
 
A quick update. First, while the FS9 aircraft-chooser displays an untextured rendition of the converted model, FS9 crashes as soon as you attempt to seloect that aircraft.

Re SAMM, at least one reason for it not displaying is that the DICTionary is 0-length. For SAMM that means nothing gets displayed.

So, there would appear to be a fundamental problem in the conversion of FS2000 aircraft models.

Don
 
Hi Don,

I haven't tested the model yet, will do so tonight. But I think I already have some FS2000 test models that I can read with ModelConverterX. I'll report more details after I looked into this.
 
Thanks for the update.

To summarize:

1. Several minutes after commencing the MCX import, the "set variable" dialog appears and then, a few seconds after closing that dialog, the textured model appears in the MCX window. There are several errors/warnings listed in the Event log, but the rendered model seems complete other than for the propellor missing (probably due to one of the variables not being set).

2. The model exported from MCX in 3DS format results in a "Improper file format" message from GMax when I attempt to import it.

3. Neither the FS9 nor FSX .mdl file exported from MCX displays as scenery. Both compile without error. I've examined the FS9 .mdl file and there's nothing apparently wrong or missing. Incidentally, when MCX exports a FSX .mdl file, it would be helpful if it also advised the Guid embedded in the file.

4. As I mentioned yesterday, the aircraft .mdl works in FS9, but not in FSX. The FSX aircraft chooser advises "Visual model could not be displayed". If you continue with the aircraft, the bottom half of the screen (presumably where the panel would be displayed) is black and the top half is compressed.

I hope you can fix this. The Fleet Canuck is a vintage Canadian-built aircraft, one of which still flies out of the airport I currently have under development (CYBL).

Good luck,
Don
 
Arno, further to my update, I can now confirm that the FS9 .mdl file exported from MCX does, in fact, display as scenery in FS9. The previous situation regarding that file was my fault - for reasons too embarrasing to mention.

All other aspects of my update remain true.

Don
 
Hi Don,

Thanks for your update, since I was at work I haven't been able to look at the model. I'll try to do so soon.
 
BTW, now that I'm able to display the MCX-exported FS9 .mdl, the "pressure if off", i.e., my specific needs can be met - except for the missing propeller. (I'll "play" with the variables to see if I can get that back).

Don
 
Hi,

Yes, but it would still be fun to figure out what is going on :D.
 
While you're at it, I've got another exception for you - in both the latest stable release and the current development release.

When I attempt to import a SAMM-converted (FS9 scenery) model (which displays normally in both FS9 and FSX) I get a "Non-negative number required" exception. If I click continue, MCX enters what appears to be another endless loop (I let it run for 10 minutes - no change.

I've attached a .mdl file for you to work with.

Don
 
Thanks, will check that as well.
 
Hi Don,

I think you forgot to attach the MDL.
 
I did attach it, but neglected to upload it. Should be there now.

In one respect, the latest exception is a false alarm. I introduced an error into SAMM yesterday which caused some data corruption. With that bug fixed, MCX now imports SAMM models without error. However, so that you can find the cause of the exception, I've attached one of the corrupted files.

Don
 
Last edited:
Hi Don,

OK, let me check if I can make it more robust. But if the MDL has a bug it will probably never become perfect :).
 
Hi Don,

I have made the reader more robust now and the faulty MDL does now show (with some parts at an offset).

I will check the original aircraft model later to see if I can make it quicker.
 
Hi Don,

No, I did not get any PM from you.
 
Got it now.

You can contact me directly at arno@ (name of this site). The admin address goes to all admins.
 
You must log in or register to reply here.
Back
Top