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

64bit XToMdl & P3D SDK

Messages
10,163
Country
us-arizona
Hey all,

This is going to sound crazy, (normal for me), but I am now 'new' to the entire Max creation world. I have been having a heck of a time getting things to work.

I found the only way I can export an X & Xanim file into MDL format is with Sean Isoms cool 64bit Compiler.

But... With my bare bones new plane, (wings, fuselage, basics of the landing gear, no interior yet, barely mapped), I am having export problems.

The fuselage is mapped and has a texture, but doesnt show up in the sim unless its the only thing exported. It has its own separate material. The other parts show up fine (including the parts with 'no' Material) in P3D fine, but no fuselage.

Thus the fuselage isnt on a 64K limitation.

I also get crashes in 3DS Max 2012 32bit when exporting. Its not every time, but often, perhaps 50% of the time.

So... Out of curiosity, does anyone have any idea's on why my plane doesnt want to fully export or rather fully show up in the sim?

I had imported the plane from Gmax derived MDL format into 3DS format via Arno's MCX program, and have smoothed everything to reduce Vertice counts, but I still get this 'missing Fuselage' issue. I have also welded all vertices.

Any ideas?
 
I ran across the same "crash" problem some time ago but things weren't working at all so I reinstalled 3ds max.
Did you "verify" your model before exporting, or get warnings from Sean's XtoMDL?
 
Hey Alexis,

Negative. No warnings.

I dont know what you mean by verify though?





Today, in an effort to get the 'shortcut' going for XToMdl.exe to run, I was shortening the folder names of the Prepar3D SDK folders. I then reset the ConfigSDK.exe to get them in check. I then deleted the old route in 3DS Max and reset it to the new Prepar3D Tools route of the new renamed folders. But.... (yes... ) Now the Aces tools no longer function, and I now have 3 sets of Aces Tools running along the top of my Max toolbar, of which none work.

It only gets deeper... goodness..
 
I am moving on to trying to get the stock XtoMdl to work.

I cannot get the Sean Isom compiler to export the entire model, and the model is very small presently, only the starting work, a basic shell. When the model is done, it may be 300 to 400,000 Polygons, so if its not compiling this, it surely will have issues with a giant model.
 
When you open the "Export LOD" window, there is a verify button.
It checks that you have correct scale, shadow volume, welded verts e.t.c.
Just make sure you "verify" one item at a time as it can crash 3dsmax (especially collocated vertices).

XtoMDL x64 seems to work OK for me, btw -for now.
 
Speaking of co-located vertices, aka: degenerate polys, has anyone ever run across a Maxscript that will automatically find and remove 'em? :D
 
Speaking of co-located vertices, aka: degenerate polys, has anyone ever run across a Maxscript that will automatically find and remove 'em? :D

No, but:
-select everything in the scene (CTRL+A)
-add an edit mesh or edit poly modifier from the stack
-Activate vertex submode
-Select All (CTRL+A): All objects' vertices will be selected as if they're a single object
-Weld

This will give you the same result without attaching all objects to each other.
You can then Rclick and convert to editable mesh. You'll have your separate objects, but because of converting to mesh, you won't have the entire stack of edits you made previously.
By adding an Unwrap UVW modifier to each object afterwards, though, UV coordinates are kept intact.
 
Speaking of co-located vertices, aka: degenerate polys, has anyone ever run across a Maxscript that will automatically find and remove 'em? :D

I have recently gone through a great many scripts. One that I d/l'd was from the famous collection of Bobo's scripts and called SelectCoplanarPoly. I haven't tested it yet, and it may not do what we are after. If you want to have a go at it, feel free:

https://dl.dropbox.com/u/51024107/SelectCoplanarPoly1_0.zip
 
Thanks for the suggestions. Now I have another one that harkens back to the old DOS days and the power of the command line...

Once again, I emphasize that ideally one should use a custom path for both the sim and the SDK to avoid the "rediculously long paths" that are "default", as well as step around any of the draconian "permission issues..."

Or, one can create a "virtual drive letter" via a .bat file for those really long paths using the subst command:

SUBST R: "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK"

Alternatively, one may run the .bat file automatically every time the computer is booted by editing the startup routines.

In either case though, the net result is much shorter command line text! My suggested "Target" for a shortcut then would be:

%windir%\system32\cmd.exe /K R:"\3DSM7\Plugins\xtomdl.exe" /XANIM /DICT:R:"\bin\modeldef.XML" > buildlog.txt

Obviously, one could even go one step further and define two subst drive letters that drill all the way down to the last sub-folder name, which could reduce the "Target" command the absolute shortest possible!

%windir%\system32\cmd.exe /K R:"\xtomdl.exe" /XANIM /DICT:S:"\modeldef.XML" > buildlog.txt
 
Back
Top