New 3DCrafter/Old 3DCanvas user

Interesting – that .X file looks OK. Can you run XtoMDL from the command line to convert it to a mdl?

Looks like you’ll have to stick with 8.2.7 for now. I have 3dc 9..1.1, 8.2 and 7.1.2 all running on the same Win 7 64 bit laptop.

I’ll need to look though the plugin code to see how it searches for xtomdl.

Paul

Thanks. That’s what I’m doing now. I came across this url while searching on xtomdl.exe: <!– m –><a class="postlink" href="http://www.flightsim.com/vbfs/showwiki.php?title=XtoMDL-exe">http://www.flightsim.com/vbfs/showwiki. … XtoMDL-exe</a><!– m –> I don’t fully understand it but I did go to international formats and insured that I’m using a period in lieu of a comma for a decimal point, else I’d get an mdl file with no volume. But, I still get no volume in my mdl files. When I dragged an x file to my xtomdl the DOS window doesn’t last long but I do see &quot;ERROR&quot; at times.

I was wondering if it were possible to save a command prompt file when I remembered something from about 20 years ago: I used the command prompt to have an x file executed by xtomdl.exe and typed &quot;&gt;error.txt&quot; after the command. I was surprised to see a new error.txt file appear. I’m attaching it. Maybe this will help. Just got informed that a txt is not allowed. Lemme think. I have no choice but to copy and past it here:

OutputFile: testcube64.MDL
Output file after modification: testcube64.MDL
Creating output MDL file: testcube64.MDL
(0): error : XToMdl.exe Unhandled Application Exception
(0): error : System.IO.FileNotFoundException: Could not load file or assembly ‘Managed_CrashTree, Version=10.0.61472.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.

(0): error : File name: ‘Managed_CrashTree, Version=10.0.61472.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ —&gt; System.IO.FileNotFoundException: Could not load file or assembly ‘Managed_CrashTree, Version=10.0.61472.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.

(0): error : File name: ‘Managed_CrashTree, Version=10.0.61472.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’

(0): error :

(0): error : WRN: Assembly binding logging is turned OFF.

(0): error : To enable assembly bind failure logging, set the registry value [HKLMSoftwareMicrosoftFusion!EnableLog] (DWORD) to 1.

(0): error : Note: There is some performance penalty associated with assembly bind failure logging.

(0): error : To turn this feature off, remove the registry value [HKLMSoftwareMicrosoftFusion!EnableLog].

(0): error :

(0): error : at Microsoft.FlightSimulator.XToXmlLib.ModelProcessingContext.Dispose()

(0): error : at Microsoft.FlightSimulator.XToXmlLib.XToXmlLib.&lt;GetFileProcessor&gt;d__0.MoveNext()

(0): error : at Microsoft.FlightSimulator.XToXmlLib.FileExporter.OutputModels(IEnumerable ProcessedModels)

(0): error : at Microsoft.FlightSimulator.XToXmlLib.XToXmlLib.OutputModels(IEnumerable`1 processedModels)

(0): error : at Microsoft.FlightSimulator.XToXmlLib.XToXmlLib.ProcessAllFiles()

(0): error : at Microsoft.FlightSimulator.XToXmlLib.XToXmlLib.Process(ModelFile[] InputFiles, Hashtable[] AnimationLinkage, String[] AnimationFileRef, XPartDict PartDictionary)

(0): error : at Microsoft.FlightSimulator.XToMDL.XToMDL.ProcessInputs()

(0): error : at Microsoft.FlightSimulator.XToMDL.XToMDL.RealMain(String[] args)

(0): error : at Microsoft.FlightSimulator.XToMDL.XToMDL.Main(String[] args)

(0): error :

(0): error :
(0): error :
(0): error : Could not load file or assembly ‘Managed_CrashTree, Version=10.0.61472.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.
(0): error :
(0): error : Stack Trace:
(0): error : at Microsoft.FlightSimulator.XToXmlLib.ModelProcessingContext.Dispose()

(0): error : at Microsoft.FlightSimulator.XToXmlLib.XToXmlLib.&lt;GetFileProcessor&gt;d__0.MoveNext()

(0): error : at Microsoft.FlightSimulator.XToXmlLib.FileExporter.OutputModels(IEnumerable ProcessedModels)

(0): error : at Microsoft.FlightSimulator.XToXmlLib.XToXmlLib.OutputModels(IEnumerable`1 processedModels)

(0): error : at Microsoft.FlightSimulator.XToXmlLib.XToXmlLib.ProcessAllFiles()

(0): error : at Microsoft.FlightSimulator.XToXmlLib.XToXmlLib.Process(ModelFile[] InputFiles, Hashtable[] AnimationLinkage, String[] AnimationFileRef, XPartDict PartDictionary)

(0): error : at Microsoft.FlightSimulator.XToMDL.XToMDL.ProcessInputs()

(0): error : at Microsoft.FlightSimulator.XToMDL.XToMDL.RealMain(String[] args)

Have you moved the xtomdl.exe from it’s original folder?
it seems to be missing a dll file that is supposed to be in the same folder.

Re your &quot;Have you moved the xtomdl.exe from it’s original folder?
it seems to be missing a dll file that is supposed to be in the same folder.&quot;

Of all the times I’ve installed 3dc (all versions) in the past few weeks, I do recall a couple times getting a small window that stated the xtomdl.exe was missing in the Plugins folder. I assumed it was the PluginsImportExport folder where, in fact, it was missing. So I inserted a copy there. Also, there is not one in the Plugins folder. Should one be there? I’ve been using the one dated 12/10/2007. In my unbiased, unpreduciced opinion, I would think the msi file would have handled that. I never move a file that was installed. Your questions leaves me a bit in a quandary: what is the &quot;original&quot; folder you speak of? Also, what dll file seems to be missing and from where? Seriously, Paul, I’m just a simple operator of a very complex machine. I have no idea of what’s in a msi file, nor can I decompile any dll files. I leave that up to people of your caliber. Sir, I just follow your instructions Sir! BTW, noticed that you were up late working on this, thanks, but take a break.

misunderstanding, nothing to do with 3DC <!– s:) –><img src="{SMILIES_PATH}/icon_e_smile.gif" alt="" title="Smile" /><!– s:) –>

The xtomdl.exe is installed by the FSX SDK into a folder along with the required DLL’s – that is the original folder I was talking about.

I suspect that dragging the .X file onto the xtomdl.exe caused the program to run in a different folder where the exe couldn’t find the DLL’s?

To convert the .X file you probably need to check the SDK help or look at the tutorials on <!– w –><a class="postlink" href="http://www.fsdeveloper.com">www.fsdeveloper.com</a>&lt;!– w –>

The .X coming out of 3DC appears correct, the plugin can’t find the defualt folder for the xtomdl (hence the message after export) so you then need to convert it &quot;manually&quot;

Just read your last post. Looks like we’re on the same page now.

<!– s:o –><img src="{SMILIES_PATH}/icon_e_surprised.gif" alt=":o" title="Surprised" /><!– s:o –> I finally did it!!! I got a mdl with volume. It was a rather round-about way though. I was sitting here staring holes into my monitor, when I asked myself, &quot;I wonder if 3DC has any idea where my SDK is?&quot; All the files that would make a mdl file were in the SDK. So, on a hunch, I pasted the .x file that 3DC had generated (along with an empty .mdl file) into the sdk: …sdkEnvironment kitModeling SDK3DSM7Plugins folder. This folder had an xtomdl.exe, MdlScan.exe along with some dll’s including the Managed_CrashTree.dll that my error file cited. I then dragged and dropped the generic TestCube64c.x into the xtomdl.exe and promply got a mdl file with volume. I then took the config and new mdl file back to my Work_in_Progress file. I opened LibraryCreatorXML.exe, opened Options to make sure it had the path to my SDK, saved the new library file, selected the new mdl, and I was promply furnished a bgl file. After making a placement.bgl file, I put it into the FSX scenery file I was working with. Launched FSX and I now have a cube floating in a field nearby. (It floats ’cause I purposely made it higher than ground level of 8.5 M.)

It is now apparent the 3DCrafter has no idea where my SDK is. I went to the 3DCrafter program file and in the Plugins folder, there is a FS10Attach.xml file which I opened with Notepad. There is an entry:

&lt;fs10attach&gt;
&lt;effects root=&quot;HKEY_LOCAL_MACHINE&quot; key=&quot;SOFTWAREMicrosoftmicrosoft gamesflight simulator10.0&quot; subkey=&quot;SetupPath&quot; suffix=&quot;effects&quot;/&gt;
&lt;parts root=&quot;HKEY_LOCAL_MACHINE&quot; key=&quot;SOFTWAREMicrosoftmicrosoft gamesFlight Simulator X SDK&quot; subkey=&quot;SetupPath&quot; suffix=&quot;sdkEnvironment KitModeling SDKbinmodeldef.xml&quot;/&gt;

I searched in the Registry for the &quot;parts root&quot; in HKEY_LOCAL_MACHINE address above and couldn’t find it. I’m not too comfortable fooling around with the Registry, so exited.
I was wondering if there was any kind of way to make a directory path to the SDK in my Work In Progress folder or even in 3DCrafter program folder such as some sort of ini file that the program would read. I don’t know what the wording would be anyway. At least now I know I can generate an acceptable mdl file. Now I’ll have to try it with a more complex file. Later…The more complex file, about 550KB big, worked fine. I can now get back to work on it. I know now why there’s no xtomdl.exe file in 3DC. It gets all its work done by the SDK when it comes to FSX files. See, I told you that I was just a simple operator! <!– s:) –><img src="{SMILIES_PATH}/icon_e_smile.gif" alt="" title="Smile" /><!– s:) –>

Getting there <!– s:) –><img src="{SMILIES_PATH}/icon_e_smile.gif" alt="" title="Smile" /><!– s:) –> <!– s:) –><img src="{SMILIES_PATH}/icon_e_smile.gif" alt="" title="Smile" /><!– s:) –>

One last thing you can try to make the MDL creation automatic:

Copy the entire contents of the folder …sdkEnvironment kitModeling SDK3DSM7Plugins into the 3DC pluginsimportexport folder

I’ve tried it on a laptop with Win7 64 here and it created the .X file then ran xtomdl

That worked just fine! Now I can get back to work doing scenery. Your leading comments and suggestions made me dig in and research the program further. Now I understand the program much better. I have to write a note to myself to remember all this at a later date.

You can now get back to your baby: Train Sim. Many, many thanks!