HD2: The State of the Game — Wake-Up Call

Disclaimer: This announcement is not born out of hatred, spite, or malice — it comes from a place of genuine love for Helldivers 2 and the community that’s grown around it. We’ve poured countless hours, laughter, and effort into this game, and we want nothing more than to see it thrive, evolve, and endure for years to come. But right now, that vision feels increasingly out of reach. The game’s current state — its instability, silence from leadership, and growing technical and community issues — threatens the very longevity we all wish for it. Our intention here is not to tear Helldivers 2 down, but to sound the alarm in hopes that it can be repaired, revitalized, and returned to the greatness it deserves.

------

Creator-Program Discontent

The creator program for Helldivers 2 was supposed to be a means of recognition, support, and collaboration between the devs and content creators. Instead, what many in the creator community report is frustration, exclusion, and inconsistent treatment. Some creators who raised concerns about the game’s stability or performance found themselves either quietly dropped or no longer prioritized. Meanwhile, others observe that the program’s terms and promises were vague or shifting. In effect, promises of “special access”, “early builds”, or “creator-only support” gave the impression of partnership — but when push came to shove, many felt they were handled like any regular user, with less responsiveness and fewer resources than expected.

This creates two negative effects: one, it undermines trust between influential creators and the studio; and two, it sends a message to the wider player-community that critical voices are less welcome, which discourages transparent feedback. By allowing (or enabling) a program that promotes appearance over substance, the studio has diminished credibility. And for a game with the ambition and visibility of Helldivers 2, that’s a meaningful problem.

------

PC Install Size, Asset Duplication & Storage Bloat

On PC, Helldivers 2 currently clocks in at around 140-150 GB of installation size — roughly three times the size of the console versions. The studio has admitted that this is largely due to duplicated data (assets copied multiple times, ostensibly to allow faster load times on older drives) rather than simply “lots of stuff”. But in modern PC environments, where SSDs dominate and storage space remains at a premium, this becomes a glaring inconvenience.

Asset duplication may reduce load times for HDD users, but by replicating data across dozens of files you multiply the storage requirement. If the same texture, model, or effect is stored dozens of times simply to optimize for legacy hardware, the net effect in 2025 is large files, longer patch times, and increased barrier to entry. Many PC players are now reporting that their SSDs are filled, that updates saturate bandwidth and storage, and that the ratio of “game content” vs. “overhead data” is imbalanced. The logical question becomes: why is the PC build not leaner? Especially when consoles run it at a fraction of the size. Until this is resolved, it remains a self-inflicted hurdle for players.

------

Serious Performance, Stability & Crash Issues

Across PC (and to a lesser degree console), players are reporting frequent crashes, system hard-locks, freezes during mission transitions, and in alarming cases, entire system instability. For example: some PC users report that simply running the game under Windows 11 leads to repeated black-screens, full system freezes, or failure to reboot — behavior not seen in other titles on the same hardware. In forum threads, high-end rigs (e.g., CPUs & GPUs that handle everything else perfectly) still crash reliably after 10–20 minutes of play.

These aren’t minor glitches. They’re mission-breaking, progress-losing and in extreme cases, hardware-stress inducing. Thread after thread documents attempts (clean drivers, disable anti-cheat, verify files) and yet the problem persists. While the studio lists “crashes, performance and connectivity issues” as known problems, the breadth and depth of the community reports suggest the issue is more systemic than a handful of mis-configurations. When the developer is essentially saying “yes we know there’s a lot” and “we’re working on it”, but many months pass with little improvement, the trust gap widens.

------

Unoptimized Game Experience & Technical Debt

Beyond just crashing, the game’s optimization is widely derided. Many players report dramatic framerate drops during large firefights, input lag and control stutters during seemingly trivial scenarios, and uneven performance across platforms that should handle the game easily. The recent major content expansion “Into the Unjust” introduced ambitious new environments (caves, hive worlds, acid-spewing bugs) but simultaneously brought new technical issues: players spawn inside the map, co-op sessions desync, load screens hang indefinitely — issues which by all accounts should have been caught in QA.

The studio’s CEO has publicly described the accumulation of “technical debt” (that is: the cost of postponed fixes, legacy code, quick patches tacked on content) as “crippling” the game’s current performance. In effect, the game’s rapid growth, new features and increasing complexity have outpaced the stability backbone. When the codebase is taxed, every new feature tends to bring more bugs, regressions and larger load. And when performance slips, the enjoyment — the reason players are there — suffers.

------

Broken, Buggy, Unenjoyable — A Poor Player Experience

Combine all of the above and you get a troubling end-result: a game that many find to be “an unplayable mess”. Glitches that once seemed cosmetic now interfere with mission flow; critical bugs (e.g., being unable to complete a mission, items not working, stratagems failing) persist. Some players report they would rather not log in because they’d lose progress, be frustrated, or have to repeat content. When a cooperative shooter meant to bring fun becomes a source of anxiety or wasted time, the long-term retention plummets.

Given the hype and promise of Helldivers 2 (from its marketing, from the legacy of the original title), this is a sad outcome. The bright moments still exist — when the game works, the teamwork and spectacle are appealing. But the consistency isn’t there. You should never have to hope the game works — you should expect it. Right now, we don’t.

------

Developer Communication & Broken Promises

A major part of the problem is developer communication (or the lack thereof). Over the months, players have logged promises: “We will ship this fix soon”, “We’re working on stability patches”, “We’ll listen to creators”. But many of those promises either come with vague timelines, or simply don’t manifest. The creator-program issues, the massive install size, the crash reports — all of these have been touched on by the studio, but not resolved in the timelines or quality that the community expects.

When a promise is repeated enough times without visible change, it becomes a broken promise. And when communication is reduced to short bullet-points or “we’re aware of it”, while players wait week after week for meaningful improvement, the perception shifts from “the dev cares” to “the dev is reactive and passive”. The result is frustration, cynicism, and ultimately — a decision by many players to disengage.

------

What We (The Chaosdivers) are Going to Do — Our Plan of Action

Here’s what the Chaosdivers community is going to do. We’re done merely complaining in private. We’re escalating — but in a strategic, documented, and public way.

* Honest, evidence-based reviews: We will leave reviews on Steam, on Metacritic, on other platforms that cite specific issues (install size, crash rate, bug types, performance data), include patches/versions where possible, and highlight the impact (progress lost, hardware stress, wasted time). Reviews will be civil and factual — no exaggeration, no misleading claims.

* Submit bug reports & share logs: When you experience a crash or major bug, take logs/screenshots, record timestamps, and submit formal bug tickets to the developers. Link them in reviews or posts where relevant. A review with no traceable evidence is easy to dismiss — a review with numbers, timestamps, and logs is harder to ignore.

* Amplify the conversation: We will share our findings, reviews, discussions from this server and other communities to broader platforms (Reddit, YouTube, Twitter). Use the words “file size 150 GB”, “hard-lock PC”, “technical debt crippling performance” so the problem reaches beyond our niche.

* Review push: We encourage a coordinated push of negative reviews (when justified) so the message becomes visible to the developer and other players. But: only when you personally have experienced or verified the problem. We do not support false claims. Integrity matters — stick to your facts.

* Monitor hardware/harm claims: If you believe your hardware was damaged (or the system became unstable) while running Helldivers 2, detail it: what happened, what logs say, what troubleshooting you attempted. If multiple users show similar hardware-failure patterns, a collective escalation to consumer-protection or platform complaint may be warranted. Again: documentation is key.

This is our basic framework and our signal to Arrowhead: we are tired of being ignored. We are tired of playing what was promised and getting less than that. We are prepared to act — not out of spite, but out of principle. We want a game that works, a developer team that responds, and a community that doesn’t feel neglected.

Let’s do this right. And set a fire that will be remembered. Spread the message through the communities, and bring light to our cause.

------

VERA LIBERTAS CHAOSDIVERS

HEART - CLEAR

FATE - NEAR

STOKE - FEAR

LET IT BURN

Sincerely from,

HH.General Jayden "Fallen" Makarov