Marathon Season 2 Performance Issues: PS5 Stutters and PC Spikes

Reddit is quiet this week — not in the "everyone is content" way, but in the "low engagement across the board" way. Most posts are sitting at zero score with minimal comment counts. The loudest organized activity showing up right now is bug coordination: a megathread for Season 2 glitches, a daily tracker for crashes and performance drops, and individual reports working through specific hardware issues. That's the honest read. The community isn't exploding with opinion this cycle — but the performance noise is real and worth surfacing.

Steam, by contrast, tells a genuinely warmer story. Reviewers with substantial hours — 208, 290, 64 — are calling it the best extraction shooter available and describing it as a game that rewards time invested. The divergence between a low-energy Reddit and a largely positive Steam is the actual shape of this week's community.

The most specific signal from Reddit this cycle comes from u/CantbeatES1, who describes CPU usage spiking erratically — bouncing between 95% and 10% mid-match or even in the lobby — triggering what they call a "Time skew maxed" error and dropping to 10 FPS. Their note that "the game typically runs fine" at 90–95% CPU at 60 FPS before the spike hits suggests this isn't a baseline hardware issue; it's something intermittent and harder to pin down.

Separately, u/TindippOglibbLover flagged PS5 stuttering tied to a TCL HDR TV without VRR support, with stuttering occurring specifically during movement. Neither of these are dramatic community-meltdown reports — they're the kind of friction that erodes new-player retention quietly over weeks, which is more concerning than a loud angry thread because it doesn't generate the visibility that forces a fast fix.

Bungie's 1.1.0.3 patch did address "a few server stability issues," but specific client-side CPU spiking and console display-sync problems weren't called out in those notes. That gap matters.

The contrarian voice on Steam is worth naming plainly. A 3-hour reviewer isn't engaging with the game — they're running a "Bring Back Destiny" grief post, which tells you more about what's been lost than what Marathon is. An 11-hour reviewer raises the $40 price tag alongside a paid battle pass and paid cosmetics as a deal-breaker. These are real frustrations, but they sit against reviews from players with ten to thirty times those hours who describe the game as deepening with investment.

One 55-hour reviewer directly names the outside-noise problem: "A lot of people will write this game off because they blame it for Destiny dying or because they have already decided they like Arc Raiders more." That framing captures a real split — between players engaging with Marathon on its own terms and players arriving with a pre-loaded verdict. The low-hour negative reviews and the high-hour positive ones aren't really in the same conversation.

On Twitch, the most-clipped moment this cycle — "ABSOLUTE CINEMA" from Drewskys's stream at 180 views — is the clear attention peak, though clip titles alone don't tell you what the moment was. What the titles collectively suggest is players finding highlight-reel moments worth sharing: a loot-defense clip from Toonchie, a trap clip from umnickk, a gold key pull from TroolyFPS. The clip activity is modest but present — a quiet week, not a dead one.

Reddit this cycle is thin on debate and heavy on coordination — bug megathreads, LFG posts, Discord server plugs. Steam is carrying the substantive sentiment this week, and it leans positive among players who have stayed. The performance friction is real and ongoing. The question is whether intermittent CPU spikes and console sync issues are getting the attention they need before they become the reason quieter players stop logging in.