Re: [Algorithms] Kinematic Collision
Brought to you by:
vexxed72
|
From: <Pau...@sc...> - 2009-09-02 17:22:04
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 > AFAIK it is still the case, yes. The rationale was that: > - when used correctly (again, see small game above) penetration never > happens > - running an initial overlap check "just in case" seemed too costly In our projects we find that its essential to be able to recover from penetration, and we weren't able to rule it out... :/ It can happen for many reasons; our constraint solver runs for a fixed number of iterations, so it can terminate without fully resolving - stacks of objects will sink into each other over time, and the penetration vector is essential for resolving this. Also we have lots of motored joints like pistons etc which can force objects through each other. If you code the collision routines carefully, you should be able to pull out the penetration info at the same time as finding the TOI... Cheers, Paul. ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify pos...@sc... This footnote also confirms that this email message has been checked for all known viruses. Sony Computer Entertainment Europe Limited Registered Office: 10 Great Marlborough Street, London W1F 7LP, United Kingdom Registered in England: 3277793 ********************************************************************** P Please consider the environment before printing this e-mail -----BEGIN PGP SIGNATURE----- Version: PGP Universal 2.9.1 (Build 287) Charset: US-ASCII wsBVAwUBSp6jcnajGqjtoMHxAQhpQQf+PfUOPGvZGRaO69slR7mNmlwq6pcSeOvZ ksS2efm9KiHujNu6cuDj26FuUqGkdGRYlnPF7DCQhIu/9AAFJFCis5+ziPjPDzbZ 5XDME6LEigCuQC3gb/zCh8KzUTZg6lnfvsBo7EAP9n2/i8gSJ7HxohJNdDbTWxqL WEJ2xVziB4pcFms2g6adzAQcCgKAlCoUA3PSRMcO+BN81Q+QUV06rHkDQ7UC8ZwL aTskWbP+PIUvPrkmBZpfpRq9SbYQtPgzJE13/1BCNgKqgEMXvNPq9qptNXfBnRIb 1Lv7SMnJVCIuEOlpxf8NZl+ou1yRXd7NBZkGLOyHUa/B4c+pGS5aeA== =vS+X -----END PGP SIGNATURE----- |