Torque3D doesn't understand skeleton bone names that have a space in them

#1 Kyrah,

Thanks for the info. I was not tracking that issue. Seems odd since no language handles blank spaces well. I will look into it. Which version of MAX are you using?

Ron

#2 3dsmax 2012

#3 Ok thanks....seems to be a similar issue to the enumeration issue brought up by the Winterleaf guys. Spaces=Bad.....good lord, coding 101.

Ron

#4 It doesn't appear that max allows me to change this behavior.

#5 hmmm, those pesky spaces in enums that torquescript allows....

lol

#6 @Vince
I'm fairly sure this isn't related to that.

@Kyrah
How is it naming them? T3D has always expected spaces in the node names. For instance the spine is expected to look like this:

// Resolve spine
      spineNode[0] = mShape->findNode("Bip01 Pelvis");
      spineNode[1] = mShape->findNode("Bip01 Spine");
      spineNode[2] = mShape->findNode("Bip01 Spine1");
      spineNode[3] = mShape->findNode("Bip01 Spine2");
      spineNode[4] = mShape->findNode("Bip01 Neck");
      spineNode[5] = mShape->findNode("Bip01 Head");

The bones however aren't referenced by name as I recall, I may be mistaken since it's been about 5 years or so since I last had my hands in the animation code.

2012 is also what our artists were using during 1.1/1.2 development, was there an update to just the biped recently?

#7 yes that's how they are named, but then on import, all the bones are named Bip01 and then the skeleton and animations are all messed up.