"not movable" disables most all behaviors and collisions not just gravity!

deretraum

I was having the hardest time understanding why I wasn't getting any collisions detected by the Rule's "if collision then", then I finally found out it was because movable was on. Why does not movable take actors partially out of the collision detection loop. I've barely found any movement behaviors that act normal once movable is on. I just want to disable gravity for objects like pinball flippers and catapults that still need movement, but attribute defined, not automatic physics response. Is there any work around, or partial immunity. oh and while Im on the soap box i dont thing density 0 really works better than density 1000000

tenrdrmer

Moveable or non movable should not affect collisions at all. if you need something to move or rotate, like you pin ball paddle example) but stay in place you can use interpolate to create movement of a non movable object. but your video does nothing to show your issue so im not sure why its there.

TwistedMech

I found this was new for version 0.9.0.

All my non moveable turrets no longer detected a collision.

jonmulcahy

Submit a bug report

gyroscope

That's strange that this problem's happened: providing the collision behaviour is used, either in the moveable or non-moveable actor, it will work. To underline what tenrdrmer said (again ;-) moveable or non movable should not affect collisions at all.