T3D Crashes on Model Import from Blender

#1 Shouldn't that be Collision-0, these days? And not a double sided collision mesh.

Shape
detail32
Mesh1 --any name for first mesh
detail16
Mesh1.001 --LOD must be .001 of first mesh
Collision-0
Colmesh-0

#2 Thank you Steve, I have tried doing as you suggest (at least it's how I interpreted your suggestion :)), but that produces the same result.
The following steps were performed:
1) Created another cube for LOD (Cube.001).
2) Linked Cube to detail32, detail32 to Shape
3) Linked Cube.001 to detail16, detail16 to Shape
4) Renamed Col0 to Collision-0
5) Linked Colmesh-0 to Collision-0, Collision-0 to Shape.

Furthermore, I get this warning in the log:

****************************************************************************
Warning: Multiple Blender mesh names in Detail1 all reduce to the same DTS
Object name: "Cube"
The exporter will use the original names for these meshes and any nodes
generated from them. This may result in duplicate or unneccesary nodes,
extra animation tracks, and inefficent mesh packing in the exported dts
file.
Changed dts object and node name for Blender mesh "Cube.001"
from "Cube" to "Cube.001".
Changed dts object and node name for Blender mesh "Cube"
from "Cube" to "Cube".
****************************************************************************


My apologies if I misunderstood something, my brain is very exhausted today.

#3 With the new Blender DTS exporter you have to ---- oh hang on, the new exporter. You ain't the only one who's greymatter is a bit jiggered.

Forgot about that, I'm using a slightly older version of both Blender and the exporter (2.44 and 0.964) because the newest Blender has altered the method of animations, and I've not had the inclination to relearn it.

For the newest exporter you don't need the detail nodes - or any nodes, it all works via the visibility layers. In the exporter you choose a layer and set the type from the Shape->detail tab.

Jonathon Greenwalt did the work on the latest exporter - jsgreenawalt.com/ and there are various instructions up on his unfinished site.

I also read somewhere that the exporter won't work with Blender2.5 (don't know about 2.49). Personally, I'm waiting for Blender2.5 to get stable before thinking of moving over to it.

#4 Thanks for the link, I discovered a lot of things I didn't know about DTS.

But to my disappointment, the issue still persists. According to this...

http://www.jsgreenawalt.com/Blender-DTS-Exporter/documentation/tutorials/tut-part1-meshes-and-textures/Step1.html

... part of tutorial, newly created project without any modifications, nodes and collision meshes added is supposed to be exported (and imported) easily without any problems.
Following those steps (new->erase all->export...) I have ended up with the same crash. By the way, opening my dts freezes the Torque ShowToolPro too.

I'll try to reproduce this on an earlier version of blender, but meanwhile any thoughts on this matter are more than welcome.

#5 Grasping at straws a bit:
You do have Python installed, yes?
If it's mucking showtool up, then I'd suggest it's a bad export, so yeah, try an earlier version of Blender and see if that helps.

#6 Yes, it's the Blender's version. *facepalm*

2.47 is too old and incompatible with the exporter scripts, 2.49+ crashes, 2.48a exports things successfully (but it doesn't work with Python 2.6, you have to have the 2.5 version).

Thanks for assistance. ;)

#7 All this incompatibility is just the hazard of open source.

Glad you found out why it isn't working anyhow.