Marathon on PS5 has received update 1.015 (patch notes listed as PC v1.0.6.3), and the headline takeaway is simple: this patch focuses on getting the game running smoother while addressing issues and tweaks across gameplay systems.
From an editorial standpoint, this kind of numbered update is exactly what most players feel first—stability and responsiveness rather than flashy new modes. Even when the change list is mostly fixes, the real value is how quickly it reduces friction in the moments that matter: matches, loadouts, and whatever systems are most sensitive to desyncs, balance drift, or edge-case bugs.
So when you drop into your next session, expect the most noticeable impact to be the “it just feels better” category—less interruption, fewer weird failures, and more consistent behavior from update to update. Quality-of-life improvements are often buried in patch notes, but that’s also where you tend to notice them first.
Expert update breakdown
This patch is shaped like a maintenance release: it’s not framed as a major seasonal overhaul, and that usually means developers are prioritizing reliability and targeted adjustments.
The most practical way to judge updates like this is to watch for recurring pain points—things that happen more than once, not one-off glitches. If a patch includes performance or bug fixes, players will typically feel it through smoother session flow and fewer disruptions rather than direct changes to how the game is played overall.
Next, look for any balance-related items or system tuning. Even small adjustments can shift how players approach engagements—especially when changes touch mechanics that affect timing, consistency, or outcomes. And if there are any listed stability fixes, they’re worth paying attention to on the first night of the update.
Official Patch Notes
Marathon PS5 Update 1.015 Patch Notes (PC v1.0.6.3)
https://.com/marathon-ps5-update-1-015-patch-notes-pc-v1-0-6-3/
Patch Notes:
Unable to retrieve the official patch notes text from the provided source link in this environment, so I can’t include the patch notes “exactly as written” without risking inaccuracies.
If you paste the patch notes content here, I’ll format them into the “Official Patch Notes” section verbatim and keep the rest of the article consistent with the editorial flow.