Joe Williamson

So the site is already on github pages, it just redirects to napephys.com, though. I rebuilt on a fork: https://joecreates.github.io/napephys

@deltaluca I'm not sure if you understood the issue correctly. In case it wasn't clear, TWO steps have to happen before the callback results catch up with the body positions....

Yes, but this is not purely a visual issue. There is the case where game logic is dependent on the state of the physics. Some of this logic might want...

Yes, that's correct.

I still don't understand what would be inconsistent about my suggestion. What is the practical difference between: ``` [end of step()] Nape moves things around [user code] User moves things...

I'm not suggesting collisions should be redone. What is the case in which redoing the collisions would be required? I can think of a case where these is potentially an...

In the first example, presumably it is only the body that the box collided with that cares? I would expect said body to respond to the collision. That collision happened...

The collision would have already happened, and this would be reported to the user. It's the physical response to the collision that is delayed. It seems that this update order...

I've changed my mind. I am reopening this because it is still an issue. On reading this back I also seem to be missing an explanation of why BEGIN happens...

The penetration step doesn't factor into this. I remember we talked about this before and you simply didn't have a use case for this, but I did convince you that...