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

falcon409

falcon409

Messages
687
Country
us-texas
I am running P3D_V2.4 only. I no longer have FSX installed and FS9 is only installed in order to access aircraft to convert to static objects. I have the current P3D SDK installed, I have the FS9 SDK installed and I have MCX installed. When attempting to convert the FS9 default Cessna 172, after locating the makemdl.parts.xml file and continuing to "make model", the progress window appears. . .there's about a 10sec lag and I get the message "Unable to convert this model for use with P3Dv2. MCX.dll issue."

What's the problem?

As a footnote, I have read a few other requests about this same problem and the common thread in all of them is that no one seems to know what the MCX.dll file is. One suggestion was that it was part of Arno's ModelconverterX program. . .Arno says no. I've done a search for that file and find nothing other than references back to the forums here and questions concerning the error message. If there is no MCX.dll file then why did the developer find it necessary to add the error message?
 
Last edited:
"MCX.dll issue" does, in fact, mean Arno's MCX dll's, but not a specific one. Basically, what it means is that Arno's .dll (whichever one was being called) returned an error condition which was not meaningful to SAMM. The 10 second lag is not unusual when converting to P3D.

I have just converted the FS9 stock C172 without difficulty. You wouldn't normally be asked to locate makemdl.parts.xml for FS9 files.
Don
 
gadgets said:
"MCX.dll issue" does, in fact, mean Arno's MCX dll's, but not a specific one. Basically, what it means is that Arno's .dll (whichever one was being called) returned an error condition which was not meaningful to SAMM. The 10 second lag is not unusual when converting to P3D.

I have just converted the FS9 stock C172 without difficulty. You wouldn't normally be asked to locate makemdl.parts.xml for FS9 files.
Don
Click to expand...
Ok, however once that message comes up I have two options, 1. Click OK on the error message (which closes the progress window, which never shows any progress at all, without doing the conversion), or 2. Click ABORT on the progress window which does the same thing. If I have the latest of everything, why doesn't it work. . .why do I get an error message? Do you get that error message? If you do, how is it you get a converted aircraft and mine doesn't. I have gone to the model folder after several tries with different liveries and there is a model file there and I have found textures saved for those two planes. I've made a library for the mdl files and placed the two textures in the texture folder of the scenery I'm working on. Using IS3 I select one of the airplanes and there's nothing visible, so obviously the conversion was unsuccessful.
 
Aggravating program!! Apparently, it is converting the FS9 Cessna as a static aircraft, but not for P3D_V2 as I selected at the bottom. . .but for FS9. I've done 5 airplanes thus far, all of which I wanted placed into a single object library. When I click on Make Library it brings up a window. . .a blank window for P3D_V2. There are no P3D converted aircraft. . .there are for FS9 though. . .all 5 of them. When I go to the model folder for P3D in SSAM there's nothing there despite having selected the option to convert those airplanes for use in P3D_V2. All the models and textures are in the FS9 folder. Uggggh.
 
1. Click OK on the error message (which closes the progress window, which never shows any progress at all, without doing the conversion), or 2. Click ABORT on the progress window which does the same thing.
Click to expand...
Is that your primary concern?

If I have the latest of everything, why doesn't it work. . .why do I get an error message?
Click to expand...
Maybe you've got the latest of something else that's causing the difficulty.

it is converting the FS9 Cessna as a static aircraft, but not for P3D_V2 as I selected at the bottom. . .but for FS9
Click to expand...
As noted in the manual, SAMM always converts for the source version, in this case, FS9. It's telling you that it is unable also to convert for P3Dv.

why do I get an error message? Do you get that error message?
Click to expand...
I told you in my previous post I converted without difficulty. That implies no error message. But I KNOW I converted an unmodified stock aircraft. Perhaps yours isn't as "stock" as you think. If you attach your aircraft folder (you can remove the textures to save space) and I'll give that a try. Also, please include a screenshot of your SAMM folders showing (detail mode) so I can see which of Arno's dlls are there.

I have gone to the model folder after several tries with different liveries and there is a model file there and I have found textures saved for those two planes.
Click to expand...
So what's the problem??? To what model folder are you referring?

I've made a library for the mdl files and placed the two textures in the texture folder of the scenery I'm working on. Using IS3 I select one of the airplanes and there's nothing visible, so obviously the conversion was unsuccessful.
Click to expand...
If the models exist and you can make a library, SAMM has done it's job. Have you tried using SAMM's placement facility? This forum is riddled with posts about difficulties with IS. I'm afraid I can't take any responsibility for that.

Don
 
Ok. . . .will SSAM convert a "STOCK", as in default. . .can't be much more stock than that, FS9 airplane (Cessna 172) for use in P3D? That's all I want to do. I don't have FS9 installed for any other reason than to gain access to the default airplanes, as a matter of fact I could keep the aircraft folders and dump everything else. I don't have FSX installed, so the only sim I have installed for flying and scenery development is P3D_V2.4. So, again. . .will SSAM convert an FS9 STOCK airplane for use in that sim? If "NO" then we're done here. If "YES". . .then "HOW", because right now it doesn't.
 
will SSAM convert an FS9 STOCK airplane for use in that sim?
Click to expand...
I've told you twice now, "YES". I did it last night after receiving your initial report. I just disabled FSX (as far as SAMM is concerned) to emulate your setup and it still works. Presumably, you have the P3Dv2 SDK installed

If "YES". . .then "HOW"?
Click to expand...
By following the user manual

I offered to trouble-shoot this issue for you. I'm still prepared to. But, enough of the snarky posts. You didn't pay enough for SAMM to have that privilege.

Don
 
Here are the steps using SSAM:
http://i54.photobucket.com/albums/g84/ejwells409/SSAM_V2202-2014-oct-23-001.jpg
http://i54.photobucket.com/albums/g84/ejwells409/SSAM_V2202-2014-oct-23-002.jpg
http://i54.photobucket.com/albums/g84/ejwells409/SSAM_V2202-2014-oct-23-003.jpg
http://i54.photobucket.com/albums/g84/ejwells409/SSAM_V2202-2014-oct-23-004.jpg

The P3D SDK was just downloaded and installed about 2 weeks ago. It's the current SDK.
I tried posting images directly to this post from Photobucket but it wouldn't work, this was the best I could do.
 
I can't help you if you don't send me what I ask for. I did notice from your screenshots, however, that SAMM "thinks" you still have FSX installed. (SAMM "remembers" what WAS installed so you don't have to repeatedly enter certain data.) While I doubt this has anything to do with the issue, I suggest you delete your SAMM.ini file before starting SAMM so that SAMM can update itself as to what IS installed.

Don
 
gadgets said:
Did you try deleting SAMM.ini?
Click to expand...
Yes, but with the same results. I've found a way to use the output that I'm getting though. I'm loading the mdl files into MCX, compiling as a bgl for P3D and those bgl's show up perfectly in the sim. It's an additional step, but maybe you are correct in that IS3 has a problem with the mdl files. For whatever reason, this works, so I can use SSAM, take that output and compile to single bgl's (rather than a library which also didn't work) and still get the static aircraft I need.

Thank you for your assistance and my apologies for my rudeness. It was uncalled for.
 
I'm loading the mdl files into MCX, compiling as a bgl for P3D
Click to expand...
That's basically what SAMM does.

This zip contains the aircraft folder for the Cessna 172 and a screen of the main SSAM folder
Click to expand...
I have just converted the aircraft you sent me for P3D without difficulty or error message. So, it would seem that whatever the problem, it I due to a difference in configuration of our respective systems. Apparently, the MCX dll isn't getting everything it needs or it is getting invalid data. When you uninstalled FSX, did you also uninstall the FSX SDK? If you look in SAMM.ini, are any of the FSX parameters specified?

Don't know what else to tell you. No one else is reporting similar problems and I can't duplicate your issue. About the only thing I can suggest is that you re-install FSX and see if that helps. If it makes a difference, it would give me some indication as to what is going on.

Thank you for your assistance and my apologies for my rudeness
Click to expand...
. Forgiven!

Don
 
Are you talking about the FS9 static model or the FS9 static model that you've converted for P3D?. If the former, "no" when used wit FS9, "maybe" if used with FSX or P3D (depends on what method was used to create the windows). If the latter, that's a question you need to address to Arno. Whether you convert with SAMM or MCX, the conversion is done with MCX dlls. However, whatever the result, "it is what it is."

Don
 
Yea, the static models (from FS9 default aircraft) that I converted in MCX for P3D. That's fine, was just curious.
 
You must log in or register to reply here.
Back
Top