Weighted vertices???

#1 Interesting question...What I've noticed about GameSpaces native Joint/Bone system is this: It seems the exporter is recognizing the BONE objects/nodes and not the joints...it's the same if you want to export your gS shapes rigged, to Milkshape3D...you need to make certain each bone in your rig is uniquely named; otherwise they arrive in the milkfarm all as individually, unlinked joints...not exactly what ya want to work with...;). I've also noticed that I'm unable to cull nodes in my gS produced DSQ's...I have to include the mesh or I get an error, and if I cull nodes via a CFG file, the process crashes on trying to remove a skinned node....perhaps I've not been processing things correctly, I'd love to find out...this may push any content back into Milkshape3d for this current project...

#2 Is it much easier to produce dts files in milkshape? If so, what features are missing from the milkshape exporter?

#3 Yes, we are very aware of the way that bones and nodes are exported from gameSpace. Its because of the way the bones and skining are handled in gameSpace and trueSpace. Verts in gameSpace are attached to both the joint and the bone using tendons and muscles. While this is cool for rendered ainmation it pretty much sucks for exporting game animation.

The result of working with Caligari's developer team to come up with a solution is what you see in ShowTool Pro. The animation data will export and work just fine, (because the vericies are reltive to the position of the exported bone location) its just that because of the way that the bone information is exported there is currently no way to use the default animations that come with TGE. (because the bone positions are so drastically different)

This requires that all of your animation be created in gameSpace or trueSpace. It just looks a little different in the ShowTool Pro but causes no other problems.

@Rex: to control node animation in your DSQ files you shouldnt use the NeverExport list in the .CFG you should instead use the NeverAnimate list. Another thing that you mention above is wrong. When exporting a DSQ file for animation the mesh is needed for objects animation data to be exported properly, but the MESH DATA IS NOT EXPORTED INTO THE DSQ FILE.

DSQ files contain only animation data, period. If you dont want a node or bone to be animated in the DTS or DSQ add its name to the NeverAnimate list in your .CFG file.

#4 Thanks, Matt, sorry for the bad mesh info, I read my dumps of dsq's and see mesh objects included[and wonder, huh??]....I'll try the NeverAnimate route...thanks a bunch. I would guess, disregard any mail sent concerning this...;).

I guess I'm confusing this dsq process with Ms3d exporter's, which doesn't seem to allow the NeverAnimate option...but I can snip joints away as needed.

#5 Ah, Eric....I've sent off some files and scenes for your perusual; quite a bundle[3 zips total+ instructions]...;); and now I've gone and redone the setup for the Caligari/BUZZ3d.com elf from the VTM's. I got it to compile into a DTS shape with appropriate nodes, bounding box, mesh and rig! What you might call a player character....lol. I didn't save the export setup[dropping the start01 skeleton/rig onto the _detail128 marker] as this causes the scene to Bork in a very bad way, ;). So you have to set it up each export....this might do well as a Resource for all GameSpace users here in the community. If there is enough call for it, I'll submit the ELF scene, as I've never done this type of submission before....good luck!

Rex

#6 Thanks Rex! I was also able to export the elf with a root and run animation and get him running in Torque. I appreciate all your help with this.

#7 Great news, Eric! Glad you got it all sorted, from the tidbits discovered thru the months working with the program and exporter.