I’m trying to visualize the order of the phases of multiple separate collision events during program execution.
I have one object that is colliding with point A and then with point B and I wanted to develop a better understanding of just when the “ended” phase of each collision occurs.
I tracked the “began” and “ended” phases of both collisions using the system timer and I am seeing that:
-
both collision events have a “began” phase eventually have an “ended” phase…dah
-
BUT I don’t always know when that “ended” phase will be. The “ended phase” for point A’s collision could come after or before the “began” phase of the collision that this object has with point B.
Remember, these collisions are happening one right after the other. Often without any resulting action. But even so, the order of which comes first, the end of collision A or the start of collision B doesn’t seem to be consistent or predictable
I’m just trying to see if there is some logical way of predicting the order of when the collision “ended” phase happens.
I hope this makes sense. I’m really curious as to the answer. It will help stabilize my code and make it consistent. [import]uid: 50215 topic_id: 21480 reply_id: 321480[/import]