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

FSXA FSDS XToMDL.exe ?

orb505

orb505

Messages
77
Country
unitedkingdom
Hi all,

Attempting to create an aircraft for FSX. I've got FSDS 3.5 installed and the version of the SDK for FSX:A. I've pointed FSDS to the XToMDL.exe executable and created a simple tube to to see if I can get it all to function.

I attempt to create an aircraft and I get the message FSDS cannot find XToMDL.exe, even though it is pointing in the correct place. "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins" on my machine (FSX is on the G drive). Also tried the version in 3DSM9 with equal failure.

Any help?

Cheers
 
Correct path : C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\"
 
Gaaakkk!

What's with the rediculously looooooonnnnnnnnggggggg paths?

Just install the stinking SDK to something simple, such as:

C:\FSX_SDK

Then the path would a shorter one:

C:\FSX_SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins
 
I agree the paths are long but the fact is on this particualr problem they are correct. Being long I can't see being a problem.

O/S is XP Pro, 32bit so no UAC issues, it is good to see that FSDS works on Vista as I have Windows 7 installed on another drive but not installed FSDS on it as yet.

Mirage: From what I can see you're path is the same as mine, so thats reassuring that I am in the correct place. Still doesn't work though!

Any other suggestions chaps?

Regards

Mark
 
orb505 said:
IMirage: From what I can see you're path is the same as mine, so thats reassuring that I am in the correct place. Still doesn't work though!
Click to expand...
Hmm, the last character doesn't look the same as yours ;)
 
True, at work at the mo so can't check but don't you choose the path from a tree style directory list? EG not free type entered? Might be wrong though, I'll check.
 
orb505 said:
I agree the paths are long but the fact is on this particualr problem they are correct. Being long I can't see being a problem.
Click to expand...

Actually, since some of the "tools" are actually run under cmd.exe, long pathnames and in particular "blank spaces" in pathnames can sometimes create problems.
 
Normally surrounding the path on commandline with double quotes " " with solve that.

If I can get the wife off my pc it'll try some off the suggestions!
 
orb505 said:
Normally surrounding the path on commandline with double quotes " " with solve that.

If I can get the wife off my pc it'll try some off the suggestions!
Click to expand...

I never could get the double-quote solution to work, so I went the other way, and simply installed the SDK using a custom location and replaced the silly SDK paths with underscores instead of blank spaces! :D
 
n4gix said:
I never could get the double-quote solution to work, so I went the other way, and simply installed the SDK using a custom location and replaced the silly SDK paths with underscores instead of blank spaces! :D
Click to expand...

However, you do NOT move modeldef.xml from its default location, right?
 
FelixFFDS said:
However, you do NOT move modeldef.xml from its default location, right?
Click to expand...

No, I do not. I leave it in the ..\bin folder of the SDK. All that's "different" about my setup is that I installed the SDK to a shorter path, and made certain to remove all "blank spaces" from the path.

Once I finished my work, I used the ConfigSDK.exe utility to update the Registry information:
Installation to a non-default folder
The paths in the documentation and some tools will only be correct if the SDK is installed to the default folder. If the SDK is installed to a non-default folder, be aware that some documented paths may not be correct, and run the tool ConfigSDK.exe (in the SDK folder) to update the paths of a number of the configuration tools to the correct folder.
Click to expand...
 
OK, got it working, thanks to all. Turned out that when I ticked the option to use the XToMDL exe instead of MakeMDL the path I previously entered disappeared. Works now, let the games being!

Cheers

Mark
 
You must log in or register to reply here.
Back
Top