Changes to setPosition and setRenderPosition in 1.7.0
by Bill Vee · in Torque Game Engine Advanced · 05/20/2008 (8:08 pm) · 1 replies
While developing some custom gravity code which I started way back in TGE 1.4 I created some variables in shapebase that were used in Player::setPosition and Player::setRenderPosition.
In TGE and TGEA 1.0.3 the variables work fine but now in 1.7.0 in Player::setPosition they work fine but in Player::setRenderPosition they default to what they were set to in the constructor.
As an example mAppliedForce can be used in setPosition and setRenderPosition in previous versions but not in setRenderPosition in 1.7.0.
As I was writing this it occurred to me that this may be a difference in how 1.7.0 treats its client/server objects.
Anyone know what has changed that won't allow me to use parent variables in certain functions they way I did in the previous versions?
In TGE and TGEA 1.0.3 the variables work fine but now in 1.7.0 in Player::setPosition they work fine but in Player::setRenderPosition they default to what they were set to in the constructor.
As an example mAppliedForce can be used in setPosition and setRenderPosition in previous versions but not in setRenderPosition in 1.7.0.
As I was writing this it occurred to me that this may be a difference in how 1.7.0 treats its client/server objects.
Anyone know what has changed that won't allow me to use parent variables in certain functions they way I did in the previous versions?
Torque Owner Bill Vee
I didn't port my own code correctly.
Disregard.