Advantage of using tsStatic over staticShape?
by Nic Biondi · in Torque Game Engine · 02/02/2004 (1:54 am) · 8 replies
Quick question about the difference of tsStatic and staticShape? I'm looking into adding/modifying a class that closely resembles one of these classes(in order to make the model update it,s position continually) and would like to weigh the pro's and con's of each.
thanx alot guys.
thanx alot guys.
#2
02/02/2004 (2:32 pm)
Gasp! Sado doesn't know... and they call you an employee, jk! I don't know eaither :) Someone want to fill us in? 
#3
02/02/2004 (3:35 pm)
One inherits from shapebase, and the other doesn't iirc :)
#4
Nicolas is on the path..
staticShape includes ShapeBase as it's parent class.
and due to this all those features are within.
you might ask .. to what end?
basically this class was used for example:
the Generator in Tribes 2
im sure was derived from this class. it has the "powered" property and this allowed it to have that state.
also it has in the hierachy GameBase which give it a whole set of "processing" type methods.
the other class tsStatic derives only from SceneObject.
with this class you only get basic dts routines.
you can apply a shape and animate it and all of those features.
(and of course any features previous to SceneObject)
it does not support mounting nor the ShapeBase state machine, nor does it support the processing methods provided by GameBase
if I was you I would use tsStatic as the foundation for anything I needed to do that required a dts model.
I would try to steer clear of ShapeBase|staticShape unless I needed this object to be Highly Interactive to the player.
02/02/2004 (4:03 pm)
This one is easy...Nicolas is on the path..
staticShape includes ShapeBase as it's parent class.
and due to this all those features are within.
you might ask .. to what end?
basically this class was used for example:
the Generator in Tribes 2
im sure was derived from this class. it has the "powered" property and this allowed it to have that state.
also it has in the hierachy GameBase which give it a whole set of "processing" type methods.
the other class tsStatic derives only from SceneObject.
with this class you only get basic dts routines.
you can apply a shape and animate it and all of those features.
(and of course any features previous to SceneObject)
it does not support mounting nor the ShapeBase state machine, nor does it support the processing methods provided by GameBase
if I was you I would use tsStatic as the foundation for anything I needed to do that required a dts model.
I would try to steer clear of ShapeBase|staticShape unless I needed this object to be Highly Interactive to the player.
#5
02/02/2004 (7:34 pm)
Very helpfull, thank you
#6
02/02/2004 (8:24 pm)
Excellent explanation, Badguy... Thanks, I really learned something. :) 
Associate Kyle Carter