Helldivers 2 Studio CEO Acknowledges It “Underinvested” In Technology by Using Stingray Engine

Why It Matters

The engine shortcomings expose the risks of relying on unsupported technology, potentially affecting player retention and future revenue. Arrowhead’s commitment to extend Helldivers 2’s lifespan underscores the strategic importance of post‑launch support in the live‑service market.

Key Takeaways

• Helldivers 2 built on defunct Autodesk Stingray engine.
• CEO admits studio underinvested in engine technology.
• Over 20 million copies sold, >$700 M revenue.
• Updates fixed particle-effect crashes; issues still surface.
• Studio targets Helldivers 2 as a forever game.

Pulse Analysis

When Arrowhead Game Studios launched Helldivers 2, it was already deep into development on Autodesk’s Stingray engine, a tool that lost official support in 2018. While many studios migrate to modern frameworks like Unreal or Unity, Arrowhead chose to stay the course to avoid delaying release. This decision now surfaces as performance bottlenecks, memory spikes, and crash‑prone particle systems, highlighting how legacy technology can become a liability in today’s high‑expectation gaming environment. PlayStation’s backing provides a distribution safety net, yet it cannot replace core engine stability.

Jorjani’s public admission of underinvestment signals a shift toward allocating resources for engine maintenance rather than new features. The studio’s rapid hotfix that curbed particle‑effect crashes demonstrates the importance of agile post‑launch support in preserving player sentiment. Even with these technical hiccups, Helldivers 2 has moved more than 20 million units, translating into upwards of $700 million in gross revenue, proving that strong brand loyalty can offset short‑term performance flaws. Additional income from microtransactions and premium Warbonds further cushions the financial impact of technical setbacks.

Looking ahead, Arrowhead plans to treat Helldivers 2 as a ‘forever game,’ investing in Stingray updates to sustain long‑term content pipelines similar to MMORPGs like RuneScape. This approach reduces pressure for a sequel while leveraging existing infrastructure, but it also demands continuous internal tooling expertise without Autodesk’s backing. Community feedback on Discord has become a direct channel for prioritizing patches and performance tweaks. Success will hinge on the studio’s ability to balance ongoing optimization with fresh gameplay experiences, a challenge that could set a precedent for other developers managing legacy engines in a live‑service era.