Crimson Moon known issues: what's broken, what Team Metal has confirmed, what to do meanwhile
By DayOneFix Editorial · September 2, 2026
| Issue | Status | What we know / workaround | Source |
|---|---|---|---|
| No keybinding on PC — Alpha remapping shipped in Patch 1.0.0.1 | Fixed | Patch 1.0.0.1 (version 162350) went live on 4 September, a day ahead of the Friday target: Settings > Keyboard > custom profile lets you rebind every available action, reset to defaults and adjust mouse sensitivity. Team Metal calls it an Alpha — multiple bindings per action, double-tap and hold inputs are not in yet. | Steam announcement 'Crimson Moon Patch 1.0.0.1' (4 Sep) |
| Loadout Station unavailable between missions — not a bug, you are mid-run | Fixed | Team Metal's 3 September post: a run is three missions plus a World Boss; returning to Sanctus Clypeus between missions does not end it, so the Loadout Station stays locked until you finish the run or die. Likewise, purified gear unlocks at Common regardless of the rarity you found it at — upgrade through Gajov to raise its floor. Marked green because it needs no fix, only the explanation. | Steam announcement 'Helpful Resources: Runs, Loadouts & Gear' (3 Sep); official wiki crimsonmoon.wiki.gg |
| Hotfix 1.0.2 announced 17 Sep — no date yet | Acknowledged | Team Metal's 17 September post says 1.0.2 is aiming for "next week", fixes more bugs than 1.0.1 did, and targets save & progression among other areas. No date is confirmed: the studio says it will announce one once testing finishes and platform partners sign off. | Official post "Hotfix 1.0.2: More Fixes Coming Next Week", 17 Sep |
| Save data can be lost when the game updates | Fixed | Addressed in Hotfix 1.0.1 (11 Sep): rolling backup saves were added as protection against corrupted or unloadable saves, plus fixes for several cases where progression could reset. The studio still calls this a top priority, so treat it as mitigated rather than closed. Listed by the developer as high priority; a fix is being prepared for the first hotfix. Until it ships, back up your save folder before applying any update. | Official Hotfix 1.0.1 patch notes, 11 Sep |
| Co-op disconnects and freezes (Moore Manor, map transitions) | Acknowledged | Officially listed: clients may freeze or disconnect in Moore Manor, and an incorrect 'Player has left the session' message can appear. Players also report the client dropping the moment the second map starts. | Official Known Issues; Steam thread 'Consistent connection loss in co-op' (1–2 Sep) |
| Accepting a co-op invite can strand the joiner on the title screen | Acknowledged | Officially listed. Workaround from players: have the host stay in the hub and re-send the invite rather than joining mid-load. | Official Known Issues (Launch Day) |
| Mission progress not always awarded to the host in co-op | Acknowledged | Officially listed. Player reports are mixed on the joiner's side quests; loot is confirmed not instanced (shared drops). | Official Known Issues; Steam thread 'Multiplayer Progression Not Shared?' |
| Crashes in combat, with ray tracing, and for the host entering Ramshorn Keep's second arena | Acknowledged | Three crash classes on the official list. If you crash with ray tracing on, turn it off first — that is the one with a clean toggle. | Official Known Issues (Launch Day) |
| Shader-compilation stutter on the Epic Games Store build | Acknowledged | Officially listed for the EGS version specifically. Steam players reporting stutter should look at frame generation and V-Sync first (see below). | Official Known Issues (Launch Day) |
| Saves may not sync between Steam and Steam Deck | Fixed | Fixed in Hotfix 1.0.1 (11 Sep) — the patch notes name Steam Deck/PC save syncing directly. Officially listed. Play on one device until the hotfix if your run matters to you. | Official Hotfix 1.0.1 patch notes, 11 Sep |
| Camera clips into walls / forced auto-centering | Acknowledged | The most-mentioned theme in negative reviews (~35% of a 100-review sample): camera clipping underground or into walls in narrow spaces and boss fights, and no free-look because the camera auto-centres. Now acknowledged: the 1.0.0.1 patch note lists 'camera improvements' first among the issues the team is working on for the next patch. | Steam reviews sample (2 Sep); Steam thread on camera auto-centering; Patch 1.0.0.1 note (4 Sep) — 'camera improvements' named for the next patch |
| Ultrawide shows a zoomed-in 16:9 image | Open | Reports conflict — some 3440×1440 players say it is fine, others see a cropped field of view and refunded. Community workaround is a UE Engine.ini edit; unverified by us and not on the official list. | Steam thread 'To all Ultrawide users' (1 Sep) |
| Frame generation not working / 60 fps lock | Open | AMD FSR frame gen reported as doing nothing; one player fixed it by enabling it and restarting the game. A 60 fps lock is being tied to V-Sync by other players. Not on the official list. | Steam thread 'Frame Generation not working, anyone else?' (2 Sep) |
| Loot pickup radius too large; duplicate boss health bars; XP decimals | Acknowledged | Officially listed UI issues: the interaction area around dropped loot is larger than intended, extra health bars on Tyrigon and other encounters, XP shown with decimals, repeated HUD notifications. | Official Known Issues (Launch Day) |
| Fake 'Crimson Moon Wiki' site in circulation | Acknowledged | Team Metal's pinned notice: a malicious site is posing as the game's wiki. The only official wiki is crimsonmoon.wiki.gg; do not follow links to any other 'wiki'. | Steam pinned thread '⚠️ IMPORTANT NOTICE' (3 Sep) |
How this table works: every row is a problem we could source either to the developer’s own Known Issues list or to player reports we read ourselves — the light goes green only when a fix actually ships, not when one is promised. Same rule as our status board for the game.
The launch is rough. Twenty-four hours in, Crimson Moon sits at “Mixed” — 572 positive to 513 negative on Steam (our count on the morning of 2 September), with a median negative reviewer at about 90 minutes played. That is not a dead game; it is a game whose first day was spent arguing about controls and camera instead of combat. The good news is unusual for a launch this size: ProbablyMonsters has already published an official Known Issues list and says a first hotfix is being prepared.
Two rows that matter more than the rest
Save data can be lost when the game updates. This is the developer’s own wording, marked high priority, with a fix “being prepared for the upcoming hotfix”. Read that carefully: the hotfix itself is an update. Until the fix is confirmed inside a patch note, back up your save folder before you let any update apply — on Steam, that means before you launch the game after a download, not after.
No keybinding on PC — shipped 4 September. Team Metal announced plans for a first implementation on 1 September 2026, and Patch 1.0.0.1 delivered it on 4 September as an Alpha: custom profiles under Settings > Keyboard, with no multi-bind, double-tap or hold yet. Around 30% of the negative reviews in our 100-review sample cited this before the patch; the keybinding status page tracks what the Alpha still lacks.
What the official list covers, and what it does not
The support site’s Known Issues (Launch Day) article groups its items under stability, multiplayer, saves, UI and bosses. Everything in it is in the table above as Acknowledged — that includes the Ramshorn Keep second-arena host crash, the ray-tracing crashes, the Epic Games Store shader stutter, the Moore Manor co-op freezes, invites that strand the joiner on the title screen, host mission progress not being awarded, and the Steam ↔ Steam Deck save sync.
Three things players complain about loudly are not on that list yet, so they sit as Open: the camera (clipping into walls and forced auto-centring — the single most-mentioned theme in negative reviews at roughly 35% of our sample), the ultrawide crop, and frame generation doing nothing. Open means nobody official has said they are working on it, not that it is not real.
The practical bits
- Crashing with ray tracing on? Turn it off first — it is the only crash class on the official list with a clean toggle.
- Co-op dropping every second map? Read the co-op page — the host should stay in the hub and re-invite rather than pulling players in mid-load, and the Moore Manor freeze is acknowledged.
- Frame generation “not working”? One player reports it only takes effect after enabling it and restarting the game; a 60 fps ceiling is being tied to V-Sync. Both are player reports, not fixes.
- Ultrawide zoomed in? Reports conflict — some 3440×1440 players see no problem. The community route is a UE Engine.ini edit; we have not verified it and it is not on the official list.
- Loot hard to pick up? The interaction radius around drops is officially “larger than intended”. Not you.
Related
- Crimson Moon keybinding — the Alpha shipped 4 September, and what it still lacks
- Crimson Moon co-op disconnects and progress not saving
- Crimson Moon release page — editions, price, platforms
Sources
The Acknowledged rows are from ProbablyMonsters’ Known Issues (Launch Day) article on the Crimson Moon support site and Team Metal’s Steam announcements of 1 September (“Crimson Moon is OUT NOW!” and “An Update on PC Keybinding”). The Open rows and the percentages come from our own read of the 100 most recent negative English Steam reviews and the Steam discussion threads on co-op connection loss, multiplayer progression, ultrawide, frame generation and camera auto-centring, all read on the morning of 2 September. The review split is Steam’s count at the same check. Statuses change only on evidence; the last-checked stamp above is written by the data file itself.