prop_dynamic-related - "Disable" or "Hide"?

  • If you're asking a question make sure to set the thread type to be a question!

MOCOLONI

L6: Sharp Member
Dec 16, 2014
373
89
Hey there. So it's been a question to me for a long time. When I wanted a named entity to disappear, I didn't know what input to apply on it: "Disable" or "TurnOff". I tested them both in different map versions and both gave the same result: becomes invisible, shadows disappear, solidity removed. If there's a difference between these inputs, could someone tell them? Thank you.

P.S: I've already read the wiki and it says it just removes the visibility of the entity, but it doesn't say that it also removes the solidity when it does.
EDIT: "TurnOff" instead of "Hide", I don't know where I got it from...
 
Last edited:
Mar 23, 2013
1,013
347
I always use the disable input, but since it dosn't change the collision you have to use it with the DisableCollision input.

I forgot if TurnOff will also also disables the colision or not. Just try it out, if it dosn't then it dosn't matter if you use disable or TurnOff
 

henke37

aa
Sep 23, 2011
2,075
515
Which entity class are we talking about here? It is kinda important.
 

MOCOLONI

L6: Sharp Member
Dec 16, 2014
373
89
I always use the disable input, but since it dosn't change the collision you have to use it with the DisableCollision input.

I forgot if TurnOff will also also disables the colision or not. Just try it out, if it dosn't then it dosn't matter if you use disable or TurnOff
I think that disabling the entity will completely "remove" it, alongside its collision. The "DisableCollision" input is self-explanatory: disables only the collision, leaving the entity (and its shadows, if available) visible.
Which entity class are we talking about here? It is kinda important.
Mainly about "prop_dynamic", but also about those that support the "Disable" and/or "TurnOff" inputs.
 
Mar 23, 2013
1,013
347
I think that disabling the entity will completely "remove" it, alongside its collision.

nope, that's basicly what the "kill" input does. "disable", just as TurnOff, will only disable the visuals of that entity, but it's still there, and with "enable" and "enableColision" you can bring it back.
 

zahndah

professional letter
aa
Jul 4, 2015
721
642
nope, that's basicly what the "kill" input does. "disable", just as TurnOff, will only disable the visuals of that entity, but it's still there, and with "enable" and "enableColision" you can bring it back.
Disabling something does remove it's collison I'm quite sure, however it doesnt just delete the object like kill does.
 

Hotel Detective

L4: Comfortable Member
Dec 10, 2014
187
191
"disable" will only disable the visuals of that entity, but it's still there
Did you ever test this?
HCS6KPv.png

mzdCySZ.jpg

EEoD1gd.jpg
XEZ5Xw0.jpg
If that last image isn't clear, it's showing that the collision is gone.
 

MOCOLONI

L6: Sharp Member
Dec 16, 2014
373
89
Alright. After a few more testings, I now realized that "TurnOff" just removes the entity's visibility, while "DisableCollision" removes its collision, as self-explanatory. I'm sure that "TurnOff" somehow removed the collisions too, so I've been confused on which input to use. Anyway, to fully "remove" (but not kill) the entity, use the "Disable" input. The other inputs related to the entity would be "DisableCollision", "DisableShadow" and "TurnOff". Thank you all, guys!