jit.phys.body does not report all collisions

Hey phys.nerds,

I am running a patch that hosts 60 jit.phys.bodies with the following initial attributes:

jit.phys.body @mass 0 @force 0 0 0 @restitution 0 @scale 0.02 @filterclass other @filters other @collisions 1

anyhow, the jit.phys.body outputs the collisions-dictionary, though for some reason not always… when obvious collisions occur, these are sometimes not reported.

Has anyone run into this behaviour?

Should I increase the maxsubsteps of the jit.phys.world?

Does this happen inbetween frames and is thus ignored? Any help would be fantastic.

(…)

That being said, I have decided against jit.phys.multiple for several reasons, mainly because I can handle bodies and their collisions individually without parsing the entire collisions-dictionary and the sendbody method does not work as expected, or at least I am unable to understand the exact message body required… I have left Rob Ramirez without a reply in the corresponding thread so far because I even have difficulties setting up a patch that highlights the problem comprehensively.

It will be difficult also to share a patch here since it involves poly~ and numerous other stuff which could cause the problem. Would just like to know if anyone has a fraction of an answer to this.

Thank you!