Kasc wrote:
You would get issues where when the cube is rolling on the floor it would also activate the trigger.

A cube rolling? Seems as if havok has some problem, lol.

yohoat9 wrote:
Kasc wrote:

You would get issues where when the cube is rolling on the floor it would also activate the trigger.

A cube rolling? Seems as if havok has some problem, lol.

Rolling is actually just rotation + translation, which is certainly possible for a cube.

EDIT: I have been looking at the wiki, and would the class 'solid' work with the filter class?

chickenmobile wrote:
Like I said, use a trigger with a filter of a block that is parented to the cube. When the (invisible) brush touches the trigger it will fire the catapult.

I'm assuming you are using this method?

Soundlogic wrote:
I'm confused. I'm trying to detect world brushes, which it says are under the class solid. I don't think they have names, so I don't see how filter name could work.

There's no trigger interaction for world brushes - they'd need to be func_brush or func_clip_vphysics with a name.

For your cube idea you could try parenting a thin trigger_multiple (or even the trigger_catapult itself if parenting works) to the cube, covering the relevant face (because parenting anything solid would make it glitchy). Give it a filter_activator_name for the entity 'cube_brushes'. Then cover any surface that your cube can touch with a func_clip_vphysics named 'cube_brushes' & give it an invisible texture.

The func_clip_vphysics can be solid only to the cube by using its filtername keyvalue, so you'd need another filter_activator_name that has the cube's name.