Game Development Community

dev|Pro Game Development Curriculum

T3d 1.0 SDK = wait loadtime disappointed!!

by Szzg007 · 09/29/2009 (8:25 pm) · 12 comments

I think I do not like the T3D 1.0 version of the Collada for the identification and collision calculations. No BETA4 and 5 so normal. T3D1.0 totally does not recognize the production of COL in the COLLADA models inside the object.

I am not very fond of T3D 1.0 SDK in particular, this version of the dae of the collision.

:<
......................................................
........................................
....................
..........
....
..
hope dae back to beta5

#1
09/29/2009 (8:48 pm)
Might see if you can get someone to better help translate your problem, it is hard to make any sense of it.
#2
09/29/2009 (9:05 pm)
Joshua Halls....You hurt my young heart.
#3
09/29/2009 (9:16 pm)
I take it collision mesh/nodes in dae are not working as expected.
#4
09/29/2009 (9:24 pm)
Yeah, either way needs to be submitted as a bug. I think all of our dae models are using polysoup so I do not have 1 to plug in and test.
#5
09/29/2009 (9:46 pm)
Quote:Joshua Halls....You hurt my young heart.

I, for one, always enjoy reading your translations!
#6
09/29/2009 (10:10 pm)
Not Just .Dae...

I Cant Get .Dif's To Show Up At All...
#7
09/30/2009 (2:05 am)
I can load simple difs and export to collada, but I have not tried anything complex or with portals. DTS col shapes fail no matter what I try.
#8
09/30/2009 (2:20 am)
Its a bug... it happens... and the fix is already posted.
#9
09/30/2009 (2:39 am)
That and you could always take the source from previous releases and merge where needed to create a quick hack...
#10
09/30/2009 (6:27 am)
Works just fine for me no problems at all.
#11
09/30/2009 (2:30 pm)
Poor choice, to report a bug in a Blog post.
#12
10/02/2009 (3:31 pm)
Ya, this does seem like a bad spot for a bug report.

Not exactly good publicity.