Nick

That's a haxe error, not a flixel error. But sure, having an actual error message would be good.

Be careful, because at least half of these issues are openfl-related. Even the Mac rendering may be openfl (look at PR 2300).

I had this issue because I was manually iterating through a body's arbiters. It turns out that an invalid arbiter could totally be in the body's list, and that caused...

Here's how I did it. `checkCollision()` returns a boolean based on some custom logic. ```haxe var collision = false; var it = agent.body.arbiters.iterator(); while (it.hasNext()) { try { collision =...

To clarify, there is a frame between when two shapes are no longer touching and when an END callback gets sent out. For the case of standing on the ground:...

Nailing it down a bit more, in `space.step()`, broadphase does its collision check before the velocity and position iterations are run. So a shape's AABB during the collision check is...

Omg. Are you taking into account the penetration step of `begin`, where it takes a frame for you to actually be on the ground as opposed to within it? The...

All I remember is how passionate you were, the 0% chance Luca would change anything, and how everything is fine if you step, update, render, and debug draw in the...

I had a lot more errors. Like “Component is unavailable at this time.”

I’ll try to remember why I had the condition there in the first place, but yeah it’s fine to change it if it makes stuff work as expected. The other...