Trigger collider still blocking

[adami]

Hi I've gone through documentation and watched a few youtube videos regarding triggers and colliders on meshes. My player control is just a cube with a camera attached to it. The cube has a rigidbody and box collider applied to it and my trigger is just another cube with a box collider set to "Is Trigger". Upon testing this it seems that my player controlled box cannot enter the trigger zone as if it is still blocking the geometry.

I've attempted switching my movement from apply force to Mouse pick and it still blocks my movement. Any suggestions why this is the case?

images supplied to explain.

[Plancksize]

That's so weird. You're saying that the trigger box collider is acting like a collider EVEN without using "apply force"?

The only thing I can think of is that the movement FSM will go into a "non-moving" state when the collision/trigger happens.
 

[adami]

That's so weird. You're saying that the trigger box collider is acting like a collider EVEN without using "apply force"?

The only thing I can think of is that the movement FSM will go into a "non-moving" state when the collision/trigger happens.

Yep, but this appears not to be an issue when using the character controller and +WASD . So how do people get around this scenario if they're using a click to move function instead?

[Plancksize]

That's so weird. You're saying that the trigger box collider is acting like a collider EVEN without using "apply force"?

The only thing I can think of is that the movement FSM will go into a "non-moving" state when the collision/trigger happens.

Yep, but this appears not to be an issue when using the character controller and +WASD . So how do people get around this scenario if they're using a click to move function instead?

A good way would be to create a 2nd FSM on that object that handle the trigger(s).

[jeanfabre]

Hi,

 maybe you can send me your test scene, I'll have a look, it must be something very simple and overlooked.

 Bye,

 Jean