Haggis wrote:
How do you stop a sphere making a prop_floor_cube_button work. I know it will be a filter but i do not know which ones and what outputs i need to put in.

A sphere can activate a cube button? I didn't know that.

Anyway you need to use a filter_activator_name.

Haggis wrote:
But i dont know how to set it up

Check here: mapping-help/filtering-a-trigger-t462.html

OnStartTouch/OnPressed > math_counter > add > 1
OnEndTouch/OnUnPressed > math_counter > subtract > 1

Add the following to he math counter. Make sure the maximum setting is 2.

OnHitMax > open door or whatever
OnChangedFromMax > close door

Hope this helps!!!!!!

iWork925 wrote:
Hope this helps!!!!!!

Thankyou, it did.

OnStartTouch > Button Name > Enable

OnEndTouch > Button Name > Disable

Have the button start disabled, or if you can't do that, then have a logic_auto that disables it. Less hassle without the math_counter.

Marise wrote:
You don't need a trigger at all. You can have the button test the filter when activated. Say you use a filter_name, and your cube is named cube1. Have the filter look for cube1, and only activate the outputs if cube1 is placed on the button. So in other words, the filter serves as a 'middle-man' between the button and its output. I don't have Hammer in front of me right now, so I can't remember the exact I/O to use, but it's pretty simple.

That's right !
For example, i have a prop_floor_cube_button, and i want that when a cube (but not a sphere) press it, a door opens and a prop_indicator_panel gets checked, and when unpressed the door closes and the panel gets unchecked.
So i put a filter_activator_name, and for its properties :
- Name : filter1 (for example)
- Filter mode : Allow entities that match criteria
- Filter name : [the_name of your cubes] (in my map i had 2 kinds of prop_weighted_cube : a standard one named template_cube, and a reflective one named template_cube2, whereas the spheres were named template_sphere, so for the Filter Name i wrote template_c* so that it allows all that starts with "template_c")
I guess it could also work with a Filter Mode = disallow entities that match criteria, and a Filter Name = template_sphere

For my prop_floor_cube_button, here were the outputs :
OnPressed > filter1 > TestActivator (uncheck fire once only)
OnUnPressed > [name_of_the_door] > Close (uncheck fire once only)
OnUnPressed > [name_of_the prop_indicator_panel] > Uncheck (uncheck fire once only)

For my filter_activator_name, here were the outputs :
OnPass > [name_of_the_door] > Open (uncheck fire once only)
OnPass > [name_of_the prop_indicator_panel] > Check (uncheck fire once only)

And from now spheres won't activate the prop_floor_cube_button !

There are two minor problems i can't solve :
- even if the sphere doesn't activate the button's outputs, we still hear the button's activation sound
- the sphere still changes it's color from blue to yellow as if it had activated the button (this is also true when you put a cube in a prop_floor_ball_button)

Hope this will help...