What happens with .sethidden(?)
by Cinder Games · in Torque Game Engine · 04/01/2006 (7:36 pm) · 1 replies
Hmmm can anyone help me understand the .sethidden command.
I know that rendering and collision are not done for objects once they are hidden, what else does torque bypass? For my "fake portaling" system i have, i currently use .setvisible, which seems to simply make them invisible, but there's a much larger FPS increase when the objects are sethidden.
So i guess my questions are:
1) what other functions gets bypassed with .sethidden
2) is movement affected by this? will a hidden object cease to move, and is it still affected by gravity?
I know that rendering and collision are not done for objects once they are hidden, what else does torque bypass? For my "fake portaling" system i have, i currently use .setvisible, which seems to simply make them invisible, but there's a much larger FPS increase when the objects are sethidden.
So i guess my questions are:
1) what other functions gets bypassed with .sethidden
2) is movement affected by this? will a hidden object cease to move, and is it still affected by gravity?
Torque 3D Owner Sebastien Bourgon
A quick search for either mHidden or isHidden() will show where all the checks are, but yes a hidden object does not move, and not necessarily rendered. TSStatics are rendered weither set to hidden or not, while Interiors dissappear right away. At least thats been my experience in the world editor.