Collision Detection Model, google code project
This collision detection module is straightforward in thinking like most of my works, but I take pleasure of it, and hope that I will have time to refine and expand it and apply it to some interesting projects.
The home page of the project: http://code.google.com/p/chaincd/
I also paste some information on the historical testing worth mentioning exclusively here:
1. Object stuck no matter settled or hidden is almost always caused by improper "Hitting"
2. Error in time is almost always a result from improper interior time control. (e.g. time offset missing or excessively imposed)
3. As the inner data stracture is somewhat complicated, it is quite error prone, especially bugs like inconsistent data modification are very common.
4. There might be some theoretical flaws, though up to now none has been obviously discovered.
The home page of the project: http://code.google.com/p/chaincd/
I also paste some information on the historical testing worth mentioning exclusively here:
1. Object stuck no matter settled or hidden is almost always caused by improper "Hitting"
2. Error in time is almost always a result from improper interior time control. (e.g. time offset missing or excessively imposed)
3. As the inner data stracture is somewhat complicated, it is quite error prone, especially bugs like inconsistent data modification are very common.
4. There might be some theoretical flaws, though up to now none has been obviously discovered.
enjoy every minute of an appless, googless and oracless life