News for hackers. Stuff that matters.
Re:Valve releases Team Fortress 2 game code by magicalhippo on Tuesday February 18, 2025 @04:34PM (#43095385)
Havok also strikes me as a rather difficult piece to replace. A physics engine will often have hardcoded handling of special cases, and things can be sensitive to lots of numerical details.

Haven't played TF2 but at least HL2 relies heavily on physics for gameplay, so while replacing the rendering engine might lead to rendering artifacts which can be annoying but tolerable in many cases, replacing the physics engine will probably lead to game-breaking issues.

One could reverse engineer it, but then you're into copyright territory...

Re:Valve releases Team Fortress 2 game code by jamesfinlayson on Tuesday February 18, 2025 @06:19PM (#43096403)
There have been a few attempts to replace VPhysics (Valve's library built on top of Havok: https://vghe.net/source-engine.html#vphysics

They seem fairly functional but not fully drop-in replacements.

Re:Valve releases Team Fortress 2 game code by account42 on Wednesday February 19, 2025 @10:55AM (#43103453)
It's not like the Havok-using version of HL2 right now on Steam is free from physics bugs. Bugs can be fixed.
Re:Valve releases Team Fortress 2 game code by magicalhippo on Wednesday February 19, 2025 @10:59AM (#43103522)
Of course, just feels like a physics engine is a few steps harder than many other dependencies.

For example, one of the bugs might be inadvertently relied on in one of the map puzzles, unbeknownst to the map creator.

Re:Valve releases Team Fortress 2 game code by jamesfinlayson on Wednesday February 19, 2025 @07:21PM (#43109610)
Yeah I've heard that it's Havok with a bunch of Valve changes and fixes on top. So presumably it's a fairly outdated version of Havok.