A Reddit thread claims Valve engineer Dirk has developed optimizations in a new internal engine called Ragnarok, and that those optimizations are similar to work described in the Box2D team's recent Box3D announcement. The Reddit post quotes a passage linking Rubikon, ongoing Valve work, and Ragnarok.

The Box2D announcement, published in June 2026, presents Box3D as a public project with an engineering focus that the Reddit post uses as a technical reference. The Box3D post includes a section titled "Valve to the rescue" and the relevant passage reads:

"On the Valve side, Rubikon continues to evolve and Dirk has developed optimizations (similar to those in Box3D) in a new engine called Ragnarok. Look for that in future Valve games."

Box3D Announcement Technical Focus and Design Goals

The Box3D post frames the project as a 3D successor to Box2D with a clear emphasis on robust contact handling and performance for modern hardware. The announcement highlights engineering themes that are common to current physics middleware, including collision detection pipeline improvements, solver robustness, and CPU-oriented performance tuning.

Specifically, the post describes work in these areas:

  • collision primitives and manifold generation for stable contact resolution in 3D,
  • solver design aimed at deterministic constraint solving across fixed timesteps,
  • performance optimizations oriented to modern CPU features, including tighter memory layouts and reduced branching in the hot paths,
  • attention to broadphase and narrowphase separation so that collision checks scale for larger scenes.

Those topics are presented as engineering goals and patterns rather than as a single implementation detail. The Box3D post uses them to explain the project's priorities and to offer an implementation reference for other teams and researchers.

Valve’s Rubikon, Reported Ragnarok Work, and the Box3D Comparison

Valve has shipped the Rubikon engine in past titles. The Reddit post and the Box3D quote together imply Valve engineers are continuing to evolve Rubikon while also experimenting with additional internal engines or subsystems. The boxed quote explicitly links Dirk's optimizations to techniques described in the Box3D announcement.

Technically, the comparison suggests the reported Ragnarok work targets the same solver and collision pipeline problems Box3D calls out. That includes efforts to reduce solver instability, keep contact generation predictable, and push low-level performance optimizations into the solver and collision routines. If accurate, those changes would show up as reduced jitter in constraint systems, fewer contact-related artifacts, and better CPU scalability in complex scenes.

What The Technical Link Between Box3D And Ragnarok Would Mean For Developers

If Valve's internal work does adopt patterns similar to Box3D, developers could expect several practical outcomes. Physics update paths may move toward deterministic stepping for replay and networking. Collision and constraint code paths may be refactored to allow denser packing of active objects and fewer expensive checks per frame. Finally, Valve could prioritize predictable solver behavior that degrades gracefully under load.

Those are implementation-level trends rather than confirmed feature lists. The Box3D announcement serves as a technical reference that explains why a community observer might equate Valve optimizations with Box3D techniques. The announcement does not itself name Valve projects beyond the quoted passage.

In short, the Box3D post supplies a technical framework for the optimizations named in the Reddit quote. The claim that Dirk implemented Box3D-like optimizations in an engine called Ragnarok appears in the Box3D post's "Valve to the rescue" passage, but independent confirmation from Valve remains necessary to verify a distinct Ragnarok engine and its integration into future Valve titles.