[SOLVED]Simple(?) question about func_physbox and fizzlers
Quote from Villethemina on July 23, 2012, 6:11 pmSo is there a way to fizzle a brush tied to func_physbox entity using fizzler(trigger_portal_cleanser)?
If not then is there a way around this? Thx in advance.
So is there a way to fizzle a brush tied to func_physbox entity using fizzler(trigger_portal_cleanser)?
If not then is there a way around this? Thx in advance.
Quote from FelixGriffin on July 23, 2012, 6:15 pmDoesn't it fizzle?
I thought it did. If it doesn't, then put a trigger_multiple around the fizzler, filter_activator_class func_physbox, !activator addoutput targetname todissolve, env_entity_dissolver dissolve todissolve.
Doesn't it fizzle?
I thought it did. If it doesn't, then put a trigger_multiple around the fizzler, filter_activator_class func_physbox, !activator addoutput targetname todissolve, env_entity_dissolver dissolve todissolve.
Quote from Villethemina on July 23, 2012, 6:30 pmFelixGriffin wrote:Doesn't it fizzle?I thought it did. If it doesn't, then put a trigger_multiple around the fizzler, filter_activator_class func_physbox, !activator addoutput targetname todissolve, env_entity_dissolver dissolve todissolve.
Thanks for the tip but a direct copy from the Env_entity_dissolver wiki page says:
"This entity will not work on brush entities"
I thought it did. If it doesn't, then put a trigger_multiple around the fizzler, filter_activator_class func_physbox, !activator addoutput targetname todissolve, env_entity_dissolver dissolve todissolve.
Thanks for the tip but a direct copy from the Env_entity_dissolver wiki page says:
"This entity will not work on brush entities"
Quote from FelixGriffin on July 24, 2012, 10:47 amOops, I forgot about that. Try a trigger_physics_trap?
Oops, I forgot about that. Try a trigger_physics_trap?
Quote from Villethemina on July 24, 2012, 12:32 pmFelixGriffin wrote:Oops, I forgot about that. Try a trigger_physics_trap?That didn't work either :/
But it scared the crap out of me when I was testing it the first time and I carried a func_physbox in it to see if it works and for some reason it(trigger_physics_trap) made a loud electrical noise and killed me.
That didn't work either :/
But it scared the crap out of me when I was testing it the first time and I carried a func_physbox in it to see if it works and for some reason it(trigger_physics_trap) made a loud electrical noise and killed me.
Quote from Skotty on July 24, 2012, 1:35 pmDid you already changed the flags of the portal cleanser/physics trap to Physic Props or, just for testing, Everything?
Did you already changed the flags of the portal cleanser/physics trap to Physic Props or, just for testing, Everything?
Quote from zivi7 on July 24, 2012, 2:05 pmI never got that to work either. "Normal" physic pbjects like cans or chairs fizzled but physboxes didn't. But as a work-around you can add a trigger very close to the fizzler and make it OnTrigger Break the !activator.
I never got that to work either. "Normal" physic pbjects like cans or chairs fizzled but physboxes didn't. But as a work-around you can add a trigger very close to the fizzler and make it OnTrigger Break the !activator.
Quote from Skotty on July 24, 2012, 9:37 pmI just tested it, and it really doesn't work on any way.
You could give the illusion of a breaking object by changing it's colour to black (timer and math counter) and use a trigger_vphysics_motion - this could also provide these sparks around the object.
I just tested it, and it really doesn't work on any way.
You could give the illusion of a breaking object by changing it's colour to black (timer and math counter) and use a trigger_vphysics_motion - this could also provide these sparks around the object.
Quote from Villethemina on July 25, 2012, 6:37 amThanks to everyone for their replies. I think I'll use zivi7's method since that does best what I'm looking for, but it's good to know your method too skotty, in case I run into this same kind of problem again.
Thanks to everyone for their replies. I think I'll use zivi7's method since that does best what I'm looking for, but it's good to know your method too skotty, in case I run into this same kind of problem again.