• 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 - Options - Exporter Settings

BASys

BASys

Messages
1,361
Country
scotland
Hi Folks

Arno -
Either I'm having a very serious senior moment,
or something weird's going on with my MCX's Options Exporter settings.

I hadn't used MCX for a while.

Today, needed to convert a model into FSX format.
Imported the model.
Went to export, received an unexpected error -
08:21 MDLXWriter Error Failed to locate XtoMDL, please update the path in the options

Opened Options and looked at the paths,
and was gobsmacked to find
all entries had been overwritten with P3D paths.

Underlying reason for the error -
due to disk-space constraints,
I'd relocated both FS9 & P3D's SDKs to another drive.



Now here's the weird bit -
I don't have P3D installed.
I only have the P3D SDKs.

I have never used the P3D SDK,
other than to look at its contents or read sections of documentation.

I have certainly never used P3D's SDK in conjunction with MCX.
I have certainly never edited MCX's options to populate it with P3D paths.

Note also that -
these P3D SDK path values,
occupy the FSX SDK path options,
and not their appropriate P3D SDK path options.

Additionally,
I've never had FS9 installed in that FS9 path.

Please see screenie attached.



Any suggestions as to how this came about
would be very much appreciated.

Anyone else reported/experienced similar ?



Many thanks
ATB
Paul
 

Attachments

  • MCX_Options_Exporter_Settings_Overwritten_by_P3D.jpg
    MCX_Options_Exporter_Settings_Overwritten_by_P3D.jpg
    113.4 KB · Views: 625
mcx options.jpg
Looks like MCX could not find your FSX SDK anymore.
Are you sure you have the latest Dev Release of July 23rd?
It should look like this: see screenshot.
 
Last edited:
I'm guessing that you installed the P3D SDK via an installer, which placed its location into the Registry. MCX when starting up may check the Registry and fill in those paths automatically?
 
Hi,

This is by design. After you moved the SDKs MCX couldn't find them at the original locations anymore. So then there is logic that tries to find the SDK based on the registry (for FSX and P3D, FS2004 has no registry entries for the SDK).

When trying to find the FSX SDK I both consider the P3D v1.4 and FSX SDK, since they make the same output. But since the P3D v1.4 XtoMDL is slightly better I first look for the P3D v1.4 SDK and then for the FSX SDK. So if you have that one installed, that is the one being picked up.
 
Hi Folks

Cheers for your reply Arno.

I couldn't think of any reason why,
when FSX's SDK was still present,
FSX paths would be populated by P3D values.

Reasonable approach. :)



I notice modeldef.xml's path
is also changed to P3D's value.

Does MCX check to see
if the user has added any custom animations ?



Whatever -
It would be worth updating the Wiki manual
to explain that P3D will override FSX.



Many thanks.

ATB
Paul
 
No, MCX does not check if local additions have been made to the ModelDef.xml file. It just uses the file that you point it to.

The manual on the wiki is still for version 1.3, so for sure it needs an update will all recent changes. Just not sure when I will find the time for such a big task.
 
Hi Arno.

Cheers for your reply.
I'd forgotten the manual was non-dev specific.

Many thanks
ATB
Paul
 
You must log in or register to reply here.
Back
Top