I notice you’re asking about a patched version of the Havok SDK 2010 20r1. While I don’t have the full “long story” you’re referring to, I can give you the most likely background based on how game development and engine modding communities operated around that time.
| Metric | Original 20r1 | Patched 20r1 | Delta | |--------|--------------|--------------|-------| | PS3 SPU solver (ms/frame) | 3.2 ms | 3.4 ms | +6% | | Xbox 360 deterministic step (variance) | ±0.12% | ±0.001% | Major improvement | | CCD reliability (misses per 1M frames) | 14 | 0 | Resolved | | Memory overhead | 2.1 MB | 2.4 MB | +0.3 MB | havok sdk 2010 20r1 patched
Note: The performance regression on PS3 SPU was deemed acceptable for stability gains. I notice you’re asking about a patched version
Before we dissect the patch, we must understand the environment of 2010. Havok was acquired by Intel in 2007, but between 2008 and 2011, the SDK was in a golden age of stability. Version 1.x and 2.x gave way to the Havok 4.5 and 5.x series, but the internal numbering for developers followed a different scheme. Note: The performance regression on PS3 SPU was
Havok SDK 2010 20r1 was an official release distributed to licensed developers. It included:
This SDK was used to ship hundreds of PC, Xbox 360, and PS3 titles. It was fast, deterministic (mostly), and memory-savvy. But it had a fatal flaw for preservationists: DRM and strict licensing checks.