These cannot currently be imported or exported in any way.

How should this work? Would it be a separate menu option?

At the moment they'll just end up overlapping or falling

Sometimes detail LODs are interpreted as collision and collision LODs are interpreted as detail.

Should this completely replace "bounds" and "center"? What about radius?

Would likely be fixed by #22

I've run into an issue where the model I need to import for some reason has it's Levels of detail reversed were Level 0 is the full res and 4 is invisible. Is there a way to import LOD level 0?

Right now you have to make sure to seek to it before exporting a DTS with animation in it

It seems like the exporter gets the general 'shape' right, but the texture does not even cover the entire surface even with simple UV mapping. It leaves a lot of empty space, and just scaling/translating the values does not help.

It's supposed to apply the per-object location/rotation/scale to the mesh data

I can't even parse DTS files with embedded sequences! There's something weird going on in the format regarding the default scale properties

I figure that a top level empty would be a LOD and any armatures under it would be nodes.

We also need to automatically create LODs/nodes when this structure is absent.

How do we handle having equally named nodes in different LODs when Blender doesn't like duplicate names?

There should be a setting to not create any armatures & instead compute the relative positioning per object

This means that they cannot be manipulated in pose mode.
The importer should automatically create bones with 100% weight painting.

1. Import m.dts, modify it or leave it as the original.
2. Export m.dts over the original
3. Join a server, instead of a familiar face you'll see an abomination in its place.
4. Start a singleplayer session, you'll be normal again.

Currently the exporter considers flatshading on a per-scene basis

Looks like the code doesn't support version 25 and above, used in T3D which might be useful if you're trying to import or export more recent shapes.

For ref:

• version 25 has secondary uvs, colours, and a slight hack in the generation code to support more indices in each mesh.
• version 27 (also known as version 26) can store verts directly in an assembled buffer (reducing load times in some cases), but otherwise doesn't have any new data.

Great work on this BTW!

Right now DtsShape-using code wrangles a lot of index attributes manually, which would be nice to avoid

Hello! I am on the matter of editing already existing objects in Life is Feudal:Your Own, a game which uses .dts files via the Torque 3D engine. For that i need to import the files to Blender. I have absolutely no clue about blender and would just like to know how to install the plugin. Thanks in advance :)

Here are some screenshots along with a temporary fix for the issue: http://imgur.com/a/1mFaz
The orange dot in the first two pictures represents the object's origin. This fix requires you to disable "Use mesh transforms" when exporting.

A similar problem occurs for this guy: http://forum.blockland.us/index.php?topic=293830.0
He just didn't disable "Use mesh transforms"

This is due to nodes/objects being shared and LOD variants being stored as multiple meshes in one object

I'm not sure if this is an issue with the way Torque uses the DTS data or just the exporter (not like there's much documentation on how it's supposed to handle this), since transparency is a material property and is only assigned where it should be.

/title, the rotations will not be exported proper and the .dts file itself will error on import.

I have yet to confirm this issue, but DTS only supports one texture coordinate per vertex whereas Blender stores them per loop index(?).

This would reduce file size and NodeOrder user problems

Hi,

I'm not very experienced with Blender and also not with addons.
I was just looking for a quick and easy way to view .dts files.

Unfortunatly I'm not able to get this addon to work. Maybe I'm just doing something wrong.

I downloaded the zip file from the release tag 0.2.0.

In Blender I went to the Preferences view -> Addons and selected -> Install from file.
Then I selected the .zip file I downloaded and installed it.

Actually Blender says that it installed it and it is also present in the addons folder for blender.

So far, so good.

But I can't find the installed addon in the list of addons and therefor I can not activate it.
I also don't have the import and export options for Torque (.dts).

I tryed this with Blender version 2.81, 2.77 and 2.74 (as mentioned in the init.py file).

Can you help me to get this to work? Would really appreciate it.

Thanks and Regards

As far as I can tell the engine overwrites them anyway, so they shouldn't matter - test with m.dts

The following IflMaterial fields should not matter:

• firstFrame
• time
• numFrames

This will be much nicer than having users manually add custom properties

Classes such as Point3D, Point2D, Box and Quaternion are implemented in this plugin for working with DTS file data. Initially, the actual DTS interface (DtsShape, DtsTypes) was written to work independently of Blender, so that it could be reused.

However, Blender implements all these types as well (most likely also more complete and more efficiently). Could we perhaps just use these instead of reimplementing?

These should be exported as embedded sequences.
Depends on #2.

This is going to be hard as I can't seem to import embedded sequences right either

This makes working with animations an absolute pain. You can't have rest poses, and you can't have multiple animations in one scene. Using a single armature with a hierarchy of bones to represent skeletons would fix all these issues, and is what experienced Blender users would expect.

This should be doable, though it'll be a bit messy; Blender does not allow zero-length bones (head = tail). The vast majority of TGE models have nodes with zero offset from their parent node.

It does not import the cached.dts file.

This fixes them stretching out/etc when blended, since they expect to be given transforms that are relative to a neutral transform.

Should it read data directly from the f-curves instead?

This would require going through faces, grouping those that share a material and saving each group as a primitive.