The Final Stages of Production Are Here - HLX Files #9

| Summary status | complete |

Overview

The video argues that HLX has passed the point of maximum risk — the annual Valve holiday-break window in which major projects have historically been rebooted — and is instead in an optimization and polish phase. Tyler’s evidence is a ten-hour datamine of a late Dota 2 update that he says contained mostly small, end-of-production engine changes, plus a late-breaking “HLX FSR3” string spotted by others in the February 25, 2025 Deadlock update. The middle of the video is an explicit recap of previously covered HLX systems (physics, fluids, NPC mood AI, randomized entity placement, vehicles) rather than new findings. He is confident about the optimization reading and about an announcement possibly landing in calendar year 2025, but repeatedly hedges that this means an announcement, not a release, and that the 2025 timing is a “could be expected” inference from rumors.

Mentioned events

HLX survived the holiday break without a reboot

• Description: Tyler states that a recent major Dota 2 update gave “final confirmation” that HLX survived the holiday break, is not going through any form of reboot, and that an announcement “seems to be inching ever closer.” He frames this as the resolution of roughly two months of worry that the project had been restarted during Valve’s winter break.
• Confidence: Mixed — the engine-level evidence (continued HLX-related work in the Dota 2 update) is presented as a primary artifact, but the reading that this “confirms” no reboot occurred is Tyler’s interpretation of that evidence.
• Category: Development state
• Source: Datamine of a major Dota 2 update, as described by Tyler.
• Earlier mentions: None identified in this video.
• Verification: needs follow-up — the underlying Dota 2 build strings and file diffs would need to be re-examined; “no reboot” cannot be proven from engine strings alone.

Two months without a major engine-level HLX update

• Description: Tyler says no major engine-level update had arrived since mid-December 2024, and that the update contained “not a whole lot of meat to go off of.” During that window most interesting reporting concerned external play testing — people from outside Valve and outside its orbit being brought in to try HLX and “bug test it hardcore.”
• Confidence: Speculation — the observation about the update gap is factual in nature, but the alarm it produced is Tyler’s inference; he explicitly describes himself and others as worried.
• Category: Development state
• Source: Tyler’s tracking of HLX-related engine changes and of external play-testing reports.
• Earlier mentions: None identified in this video.
• Verification: unverified — build/change history for December 2024 through February 2025 and any corroboration of play-test sessions would confirm the gap and the testing activity.

Valve’s holiday-break reboot pattern as historical context

• Description: Tyler lays out a recurring pattern in which a major Valve project in development before a holiday break does not survive it: Team Fortress 2, originally an aliens-versus-humans game called “TF2 Invasion,” was reportedly remade into a Team Fortress Classic follow-up after the post-Half-Life 2 break; the same pattern is said to have happened with Left 4 Dead 3 in the mid-2010s. He also lists reboot periods for other titles — Deadlock was formerly Neon Prime, Half-Life: Alyx was originally a game about Combine sympathizers and a woman named Han, and Half-Life 2 was “dark and gritty.” He notes external play testers are typically the people who cause Valve to re-evaluate projects.
• Confidence: Speculation — presented as “the legend has it” and as a pattern Tyler and others inferred; no document or artifact is cited in the video.
• Category: Development state
• Source: Tyler’s retelling of Valve development history, including the “TF2 Invasion” account.
• Earlier mentions: None identified in this video.
• Verification: unverified — Valve’s own accounts (e.g., the Team Fortress 2 / Half-Life 2 development commentary) and former-employee statements would test the pattern.

Ten-hour datamine of a Dota 2 update found mostly minor engine changes

• Description: Tyler says he and others spent 10 hours datamining the Dota 2 update and found “a lot of stuff,” but characterized it as a large volume of very finite engine changes — “the kind of thing that happens near the end of a production cycle.” He notes most of it was not covered on Reddit, Twitter, or Bluesky.
• Confidence: Fact — Tyler describes his own direct datamine of a shipped Dota 2 build as the source.
• Category: Technology
• Source: Tyler’s own datamine of the Dota 2 update.
• Earlier mentions: None identified in this video.
• Verification: needs follow-up — the build diff itself would confirm the character of the changes; Tyler does not name the specific build number or update.

AI processing scaled by distance from the player

• Description: Tyler highlights an image circulating with a caption claiming Valve has reached the “optimization and polish phase.” The change he describes lets the engine tone down the computational power of each AI within a space based on its distance from the player. He states plainly that this “absolutely is optimization work.”
• Confidence: Mixed — the string/behaviour is datamined evidence, but the “optimization and polish phase” conclusion is Tyler’s reading of it.
• Category: Engine feature
• Source: Datamine of the Dota 2 update, plus a screenshot circulating on social media.
• Earlier mentions: None identified in this video.
• Verification: needs follow-up — the exact Source 2 convar or code path for distance-based AI throttling would confirm the mechanism and its app.

Production believed to be nearing completion; announcement possible in 2025

• Description: Because the majority of the Dota 2 update findings pertain to optimization and polish, Tyler concludes it “does feel as if Valve is nearing completion of the production of HLX,” and says rumors and rumblings behind the scenes support this. He expects an announcement — explicitly not a release — possibly within calendar year 2025, hedging with “could be expected” and repeating the qualification at the end of the video (“we might be closer than even I originally thought”).
• Confidence: Mixed — the optimization-heavy string set is evidenced; the 2025 announcement timing rests on unnamed behind-the-scenes rumors and Tyler’s inference.
• Category: Release date
• Source: Tyler’s inference from the Dota 2 datamine plus unspecified industry rumors.
• Earlier mentions: None identified in this video.
• Verification: needs follow-up — an official Valve announcement, store page, or rated listing would confirm; the rumor sourcing is not disclosed.

HLX described as a single-player first-person shooter with Barney Calhoun

• Description: Tyler restates that HLX appears to be a single-player first-person shooter and that thematically and story-wise almost nothing is known “other than Barney Calhoun is likely a part of it.” He frames the mechanics as an evolution of the systems first seen in Half-Life 2.
• Confidence: Speculation — presented as a recap of what “appears” to be the case, with the Barney Calhoun detail explicitly qualified as “likely.”
• Category: Gameplay
• Source: Recap of Tyler’s prior HLX coverage and datamined strings.
• Earlier mentions: Referenced only generally as things already covered; no specific prior video, leak, or claim is named.
• Verification: unverified — character, model, or voice-line references tied to Barney Calhoun in HLX builds would confirm.

Expanded physics: buoyancy, flammability, deformation, material weights

• Description: Tyler describes heavily evolved physics compared with Half-Life 2’s original physics system, citing buoyancy, flammability, deformation, and per-material weight thresholds that must be met before a material deforms. He calls the existence of a physics system the “groundbreaking feature” of the earlier game and this an evolution of it.
• Confidence: Speculation — a recap of systems Tyler says have been found in strings; no specific string, filename, or build is cited in this video.
• Category: Engine feature
• Source: Recap of previously datamined Source 2 strings.
• Earlier mentions: None identified in this video.
• Verification: needs follow-up — the specific Source 2 material/physics keyvalues for buoyancy, flammability, and deformation thresholds would confirm.

Fluid simulation and fluid-driven surface state changes

• Description: Tyler describes fluid simulation and physics between fluids and objects, including how specific fluids can change the flammability state of a surface, and how a surface’s sound properties change with its state. In a later aside during live datamining he again mentions surface properties tied to Steam Audio and 3D audio ray tracing, with audio rays bouncing off different surfaces according to surface type.
• Confidence: Mixed — surface-property and audio strings are described as datamined findings, but the fluid behaviour is Tyler’s interpretation of what those systems enable; the audio portion is read live and not tied to a named build by him.
• Category: Engine feature
• Source: Recap of datamined Source 2 strings, plus strings Tyler reads aloud during the recording.
• Earlier mentions: None identified in this video.
• Verification: needs follow-up — fluid simulation entities and the Steam Audio / ray-traced audio surface-type string set in a specific build would confirm.

NPC mood system driven by visual, auditory, and smell cues

• Description: Tyler says human-based NPCs appear to have an entire mood-based system in which an NPC’s surroundings — visual, auditory, and smell-wise — affect that NPC’s state and change both verbal and non-verbal reactions conveyed to the player and to other NPCs.
• Confidence: Speculation — described as what NPCs “appear to be able to” do, based on strings, with no artifact named in this video.
• Category: Gameplay
• Source: Recap of previously datamined Source 2 / HLX strings.
• Earlier mentions: None identified in this video.
• Verification: needs follow-up — AI state or mood enum strings and associated sensory-input parameters in a build would confirm.

NPCs dynamically adjust nav meshes after destruction

• Description: Tyler states NPCs appear able to dynamically adjust their navigation meshes when destructibility occurs within a map’s environment, allowing pathing to react to changed geometry.
• Confidence: Speculation — hedged with “appear to be able to”; no specific string or build cited.
• Category: Gameplay
• Source: Recap of previously datamined Source 2 strings.
• Earlier mentions: None identified in this video.
• Verification: needs follow-up — nav-mesh regeneration code paths or entity I/O tied to destruction events would confirm.

Voxel-based destruction now attributed to a different project

• Description: Tyler says the voxel-based destruction systems that he and others “have long speculated on” for HLX are “starting to appear to be for a different project.” This is a walk-back of a prior association rather than new evidence about HLX.
• Confidence: Speculation — stated as an impression (“starting to appear”), with no artifact or replacement project named.
• Category: Development state
• Source: Tyler’s reassessment of earlier datamined voxel destruction strings.
• Earlier mentions: Yes — Tyler explicitly refers to voxel-based destruction systems “that we have long speculated on”; he now says they appear to belong to a different project, downgrading the earlier HLX association.
• Verification: needs follow-up — identifying which project’s branch contains the voxel destruction strings would resolve the reassignment.

Randomized entity placement on hand-crafted maps

• Description: Tyler expects replayability from random assortment and placement of entities: the map is not procedurally generated and all level geometry is hand-crafted, but placement of health kits, enemies, and blockages to different areas can differ each time the player returns to or replays an area. He compares it to the Director in Left 4 Dead.
• Confidence: Speculation — framed as an expectation (“we can also expect a level of replayability”), supported by strings he does not cite individually.
• Category: Gameplay
• Source: Recap of datamined strings plus Tyler’s inference from the Left 4 Dead Director design.
• Earlier mentions: None identified in this video.
• Verification: needs follow-up — spawn-group or entity-placement logic and difficulty/director-style entity names in a build would confirm.

Significant vehicle simulation, land and possibly water

• Description: Tyler describes significant vehicle simulation covering land vehicles similar to cars and trucks, with water vehicles “not out of the question,” and says the level of simulation is on par with games predominantly focused on driving.
• Confidence: Speculation — “not out of the question” is explicit hedging on water vehicles; the whole passage is a recap without a named artifact.
• Category: Gameplay
• Source: Recap of previously datamined Source 2 vehicle strings.
• Earlier mentions: None identified in this video.
• Verification: needs follow-up — vehicle entity definitions, wheel/suspension parameters, and buoyancy handling for watercraft in a build would confirm.

February 25, 2025 Deadlock update: four lanes to three, three months of engine changes

• Description: Tyler reports that on February 25, 2025 a “massive” Deadlock update shipped, changing the four-lane map into a three-lane map and carrying roughly three months’ worth of engine changes. He states he has not datamined this update himself; a few others did “a very basic search.”
• Confidence: Fact — a specific dated, publicly shipped game update with observable changes.
• Category: Development state
• Source: The publicly shipped Deadlock update of February 25, 2025, as reported by Tyler and other dataminers.
• Earlier mentions: None identified in this video.
• Verification: verified — the Deadlock update and its map-lane change are publicly checkable.

“HLX FSR3” string found in the Deadlock update

• Description: Tyler reports that a basic search by other dataminers turned up the string “HLX FSR3” inside the February 25, 2025 Deadlock update, which he reads as Deadlock adopting FSR3 support by way of HLX’s FSR3 development. He argues you do not use FSR until a game is nearly done, since AI post-processing systems are not meant for development, and therefore HLX now has FSR3 working in its development build — “we are now at the very end of the game’s development.” He repeats the string several times while reacting live.
• Confidence: Mixed — the string’s presence is a datamined fact reported by third parties (Tyler did not datamine it himself), but the conclusions that Deadlock is borrowing HLX’s implementation and that this places HLX at the end of development are Tyler’s inference.
• Category: Engine feature
• Source: Third-party datamine of the February 25, 2025 Deadlock update, described second-hand by Tyler.
• Earlier mentions: None identified in this video.
• Verification: needs follow-up — re-checking the Deadlock build’s string table for “HLX FSR3” and the FSR3 DLL/plugin configuration would confirm the artifact; the “nearly done” reading would not be settled by the string alone.

Steam Audio and 3D ray-traced audio surface strings

• Description: In a live aside near the end of the video, Tyler reads out a further set of surface properties relating to Steam Audio, 3D audio ray tracing, and the bouncing of audio rays off different surfaces according to surface type, tying it back to the surface-state discussion earlier in the video. He reacts with “this is happening fast.”
• Confidence: Unclear — the strings are read aloud but Tyler does not say which build or update they came from, and the passage is unscripted.
• Category: Engine feature
• Source: Strings Tyler reads aloud during the recording, apparently from ongoing datamining.
• Earlier mentions: None identified in this video.
• Verification: needs follow-up — locating these surface-type audio strings in a named build would establish provenance.

New or changed in this video

• New: confirmation, via the Dota 2 update datamine, that HLX continued development through the holiday break without a reboot.
• New: the specific optimization finding that AI processing is scaled down by distance from the player.
• New: the “HLX FSR3” string in the February 25, 2025 Deadlock update, treated as evidence HLX has FSR3 working in its development build.
• New: an explicit 2025 window for an announcement (not a release), offered with heavy hedging and attributed to behind-the-scenes rumors.
• Changed: voxel-based destruction, previously speculated as an HLX feature, is now said to appear to belong to a different project.
• Recap: the physics, fluid, NPC mood AI, nav-mesh, randomized entity placement, and vehicle simulation sections are an explicit summary of prior coverage rather than new findings, by Tyler’s own framing.

Notable quotes

• “It does feel as if Valve is nearing completion of the production of HLX.” — Tyler’s central conclusion from the optimization-heavy Dota 2 datamine.
• “And an announcement, not a release, but an announcement for the calendar year of 2025 could be expected. I said could be expected.” — the hedged timing claim.
• “Then you don’t use FSR until you’re nearly done with a game.” — reasoning behind reading the FSR3 string as an end-of-development signal.
• “It legitimately is nearing the end of development.” — reaction to the Deadlock FSR3 finding.
• “While the voxel-based destruction systems that we have long speculated on are starting to appear to be for a different project.” — the walk-back of the voxel destruction association.

Open questions

• Which exact Dota 2 update and build number contained the optimization strings; Tyler does not name it.
• Who the external play testers were and which project phase they were testing.
• Whether the “HLX FSR3” string reflects shared code with Deadlock or a separate integrated path, and what build it appears in.
• Which other project the voxel-based destruction systems belong to.
• What the unnamed “rumors and rumblings” behind the 2025 announcement window actually are.
• Whether the Steam Audio surface strings read at the end came from the Deadlock update or a different source.