Failed to export

[GHD]

Using todays update, the export fails with:

"Failed to find ModelDef.xml, please update path in the options".

MCX files dated 11th work correctly.

File attached.

 

[robystar]

Hi,

Works OK here.
With previous update I had to give in the modeldef path again because MCX left out the first part of the path.

 

[GHD]

Hi,

Works OK here.
With previous update I had to give in the modeldef path again because MCX left out the first part of the path.

Hmm,

I don't have a modeldef path in the options

I have MakeMDLPath and XtoMDLPath only.

Where are the options stored? They are not all in LibraryCreatorXML.xml

 

[robystar]

Open MCX > options > fs related settings > modeldef path ...?
No idea where MCX saves its settings.

 

[GHD]

Thanks Roby, it was hidden on another page

 

[arno]

Hi George,

I moved it recently. Reason is that not only the XWriter, but also the MDLXReader uses it now. So that's why I moved it to the more generic FS Settings.

For most people the path should be corrected automatically (if the SDK registry entry is correct), but else you indeed need to set it manually.

 

[GHD]

For most people the path should be corrected automatically (if the SDK registry entry is correct), but else you indeed need to set it manually.

Thanks Arno,

Presumably Roby and I aren't 'most people'

 

[arno]

I guess so . If it is only you two that have issues I am still happy, although I hope that it would just go automatically.

 

[GHD]

Today's update preserved the path

 

[arno]

It should. The settings are stored somewhere in your user data folder. With today's update I changed nothing to the setting, so it will keep working.

Last time I moved the setting from ObjectWriterSettings to FSSettings. For the configuration file that is the same as deleting it and add a new one. But if I don't rename or move them, they are preserved on updates (else I would drive you all crazy all the time ).

 

[robystar]

Hi Arno,

The problem has occurred earlier already and several times.
With some of the updates you have to check the paths again because in one way or another, MCX leaves out the first part of the path.
It is not a problem when you know what is wrong but for some it can be puzzling.

 

[arno]

Hi Roby,

Which part of the path is missing in your case?

When the tool does not find a valid path in the options, it will try to find the SDK path in your registry. The path to XtoMDL, ModelDef.xml, etc are then set by adding their relative paths to the SDK root.

So if you are seeing their relative parts, it would mean that the SDK location in your registry is wrong (or maybe even empty but still existing).

 

[GHD]

My registry entry for the SDK is correct but MCX still got the path wrong.

 

[arno]

Hi George,

Humm, that's interesting. Do you remember what path you get? Then I might be able to debug it.

 

[robystar]

Morning,

MCX leaves out the first part of the path. In my case: C:\
Program Files\ and only remembers SDK\Environment Kit\Modeling SDK\bin\modeldef.xml.
Registry entry never changed.
Roby

 

[GHD]

My registry entry is:

LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator X SDK ( SdkRootdir = F:\FSXSDK\SDK\ )

 

[robystar]

Hi,

And mine is exactly the same except for the sdkrootdir where it says C:\Program Files\SDK.

 

[arno]

OK, thanks for the feedback. I'll double check if there is a bug in the code that sets the right path automatically.

 

[arno]

Hi,

I checked and in my case the path stored in the registry is this:

C:\flightsim\sdk\FSX\sdk"

Within the folder mentioned are the subfolder of the SDK, like Environment Kit, Core Utilities Kit, Mission Creator Kit and SimObject Creation Kit. Is that also the case for the folders you mentioned?

I think I also found some mistakes in my code, when the registry path was not found correctly. I have fixed those in the next development release. But I am not sure if tha twould help in your cases, since the registry entry seems set correctly.

 

[GHD]

Within the folder mentioned are the subfolder of the SDK, like Environment Kit, Core Utilities Kit, Mission Creator Kit and SimObject Creation Kit. Is that also the case for the folders you mentioned?

Yes, all subfolders present and correct.