One-way CollisionShape3Ds

[somerandomguy21]

so it turns out collisionshape3ds cannot be one-way
hopefully that can be implemented the same way as one-way collisionshape2ds (which do exist)

[AThousandShips]

How would this work? In 2D the direction is trivial to define, but how do you define it in 3D where you have more degrees of freedom, how would it behave?

[somerandomguy21]

lets say that the goal is a collision that is one-way from below: so, if you go from below to above, you'll pass through it.
in that case, couldnt a condition like velocity.y > 0 be checked, and if it returns true the collision becomes disabled?
what about using Vector3().direction_to(collision) and checking if its y value is above 0?

[Mickeon]

@AThousandShips Normal vector representing the one-way direction. This could actually be compressed to 2 floating-point numbers internally because only yaw and pitch matter, not roll.

For the check, a negative dot product between the one-way direction and the normalized velocity means a collision should occur (if I am picturing this correctly).

The harder part would be actually supporting this at the engine level. I don't believe Jolt Physics supports this.