I have a few questions.

Is it possible for a trigger_multiple detect other trigger_multiple?
If it can't, is it possible for a floor button of activate only to a specific cube?

Thanks in advance.

Yes,a trigger can trigger another trigger.

Could you be more clear about "Is it possible for a trigger_multiple detect other trigger_multiple?" please? Are you simply wanting to run TouchTest on another trigger_multiple (this can be accomplished with an output on your first trigger_multiple)? What are you trying to accomplish?

Thank you for helping us help you help us all.

And yes, it is possible for a button to only activate to a specific cube, i would reccommend making the button from scratch like was necessary in portal 1. (tutorial) Just use the models that fit with portal 2. Then just make the trigger that activates the button respond to only the specific cube, using a filter_activator_name. However, only one cube activating a button could be hard to explain to the player, this cube preses the button, but the other one doesnt?

taco wrote:
Yes,a trigger can trigger another trigger.

Could you be more clear about "Is it possible for a trigger_multiple detect other trigger_multiple?" please? Are you simply wanting to run TouchTest on another trigger_multiple (this can be accomplished with an output on your first trigger_multiple)? What are you trying to accomplish?

Thank you for helping us help you help us all.

I want to make it so that a trigger_multiple will activate when another trigger_multiple touches it.
Thanks for helping.

Spam Nugget wrote:
And yes, it is possible for a button to only activate to a specific cube, i would reccommend making the button from scratch like was necessary in portal 1. (tutorial) Just use the models that fit with portal 2. Then just make the trigger that activates the button respond to only the specific cube, using a filter_activator_name. However, only one cube activating a button could be hard to explain to the player, this cube preses the button, but the other one doesnt?

Thanks!

Oh, you want an invisible trigger_multiple to move into another trigger_multiple and the cause it to trigger? I don't think that is possible, and even if it was it sounds like a bad way to go about things.

You should consider the condition/reason why those two trigger_multiples are going to be touching and then trigger based off that condition rather than the fast that this condition is causing them to touch.

Example: if the trigger_multiples touch when a door is open, you should fire your trigger based on the door being open.

If you can explain your situation or upload an example I'd be happy to try to help more.

taco wrote:
Oh, you want an invisible trigger_multiple to move into another trigger_multiple and the cause it to trigger? I don't think that is possible, and even if it was it sounds like a bad way to go about things.

You should consider the condition/reason why those two trigger_multiples are going to be touching and then trigger based off that condition rather than the fast that this condition is causing them to touch.

Example: if the trigger_multiples touch when a door is open, you should fire your trigger based on the door being open.

If you can explain your situation or upload an example I'd be happy to try to help more.

Q_dAIHzzrtU

Basically, I'm making this concept. The thing is, I want to have 2 particles colors in a room.

a way is to make an invisible physics object that's not solid, parented to the trigger, when the trigger is triggered by the physics object, it triggers.

spongylover123 wrote:
a way is to make an invisible physics object that's not solid, parented to the trigger, when the trigger is triggered by the physics object, it triggers.

I'll try it when I get the chance to.

Thanks!