Issue with sequence file (TGEA 1.7.1)
by Frank Bignone · in Torque Game Engine Advanced · 01/25/2009 (2:43 am) · 9 replies
When using sequence file through the ShapeConstructor (TSShapeConstructor), my model is completly broken. By broken, I mean that each parts of the model do not have the correct orientation.
On the other hand, when using models with animations embedded in them; then everything is fine.
So my question: did something change between 1.0.3 and 1.7.1 regarding handling of external animation sequence file?
On the other hand, when using models with animations embedded in them; then everything is fine.
So my question: did something change between 1.0.3 and 1.7.1 regarding handling of external animation sequence file?
About the author
Real programmers don't waste time recompiling; they patch the binary files... ... Real programmers don't waste time patching binary files; they patch memory.
#2
Worth a quick debug view...
01/27/2009 (3:24 am)
I only have one animation with a sequence (other then player mesh who work fine) that do not work, it crash the .exe on import- but may not be a bug, but sloppy DSQ creation.Worth a quick debug view...
#3
01/27/2009 (9:21 am)
Can one of you please upload an example case which triggers this crash/other bustedness?
#4
01/27/2009 (4:14 pm)
I noted my 'test' shapes is obsolete, and will be testing this 'bug' to more depth soon. Will post results here.
#6
In all seriousness, definitely looking into this for 1.8.1.
01/27/2009 (9:47 pm)
That's not an issue, that's fantastic! Why wouldn't you want a boar with teeth jutting out of its head?In all seriousness, definitely looking into this for 1.8.1.
#7
I'll put the code back into 1.8.1, but it's going to warn whenever it encounters a duplicate node, and in the future that should be avoided.
01/27/2009 (10:40 pm)
Okay, strictly speaking this issue is with your model. You're reusing node names in the model which is generally a bad idea, and the code which tried to gracefully deal with that was removed in 1.7.0.I'll put the code back into 1.8.1, but it's going to warn whenever it encounters a duplicate node, and in the future that should be avoided.
#8
01/27/2009 (10:47 pm)
Bah, don't put it back in. Force people to create their assets cleanly, and document that process better. :)
#9
On a sidenote, I will tell it to our artists.
01/27/2009 (11:36 pm)
I think should be put back in the code ;) as you may have the issue with some old art packs too.On a sidenote, I will tell it to our artists.
Torque 3D Owner Frank Bignone
Darkhand Studio