Timeline for Is it possible to have concurrent collision detection where every entity acts at exactly the same time?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 27, 2011 at 23:54 | comment | added | Martin Sojka | You don't update the positions one after another, you check for collisions one after another, and re-calculate the positions, then change them all at the same time. There never will be a collision which happens at exactly the same time as another one (not in reality, anyway; in computer programs, you have to watch out for precision problems), so it's OK to calculate their effects one after another too. | |
| Aug 27, 2011 at 22:27 | comment | added | user_123abc | Not sure if we're on the same page about what "sequential" means in the context of a computer application, but iterating through a list of objects and updating their positions one after the other, then checking for collisions, is not a physically correct model. | |
| Aug 27, 2011 at 15:06 | comment | added | Martin Sojka | Physical collisions never happen simultaneously anyway, so not taking such into account is the correct way to go about things. | |
| Aug 27, 2011 at 0:24 | history | answered | user_123abc | CC BY-SA 3.0 |