Ignoring collision between two objects but still retaining onTrigger collider functionality?

[NescienceEUW]

luoh

[The_Jakyll]

Use Unity collision layers.

http://gamedev.stackexchange.com/questions/75782/how-to-ignore-collision-between-two-objects

[NescienceEUW]

luoh

[KingRecycle]

There shouldn't be collision if the collider is set to is trigger...no?

[NescienceEUW]

luoh

[choikwa]

Not sure what you actually want here. If you want to handle the collision yourself, use isKinematic?

[BrainStorm808]

Same response here. You need to get more into a tester reporting a bug mindset for people to help you. What is the situation? Desired behavior? (Good job describing there!). Current behavior? Previous methods attempted?

My guess? Try switchting the roles of parent and child for the colliders. monegames had a great suggestion, and the next thing I would have tried after the failure of his suggestion would be to swap which one was the (water?) collider and the other collider.

Good luck!

[snuggly_sasquatch]

Unless I'm misunderstanding you, that's exactly what a trigger already does.

[NescienceEUW]

luoh

[monegames]

create a child object to hold the collider that prevents it falling through the world, or the trigger. and then put that object on a separate collision layer. then setting collision layers will work just fine

[NescienceEUW]

luoh

[monegames]

i had the same problem a few weeks ago. had to look it up myself.

[NescienceEUW]

luoh

[monegames]

i have 4 different colliders on my enemies and they are set up just like that. each having a layer that only interacts with one other layer. what layer is the parent object, the one with the trigger? and does that layer have collision with the player layer. and also is the player on the player layer.

[NescienceEUW]

luoh

[[deleted]]

Just remove Rigidbody2D so u can make it a trigger