Beast of Reincarnation Known Issues and Workarounds

Fictions has one support article about PC crashes, covering Steam and PC Game Pass, and it does not diagnose anything. It asks players to open a ticket, attach the dump from C:\Users\<username>\AppData\Local\CrashDumps, and suggests trying a BIOS update, linking seven motherboard and laptop vendors. Read as what it is, that is informative in two directions. It is the only first-party escalation route that exists for a crash on this game — no other page on this site could tell a reader where the dump file lives — and it is first-party confirmation that the cause has not been established, because a studio that knew the cause would not be collecting dumps. It is filed here rather than under official fixes because nothing in it fixes anything.

The game reaches the Fictions logo and stops there. There is no error dialogue and no crash report, and in some accounts no window ever appears. Player Zer01 reported it on 3 August at 7:33pm and Andriod reported a DirectX 12 launch that failed outright; both got past it by forcing DirectX 11, which is what makes this one of the few entries here with a fix behind it rather than a guess.

A launch failure reporting CreateProcess() return 11c7, which the reporter traced to Windows Smart App Control refusing to run a self-signed executable. That diagnosis is the reporter’s reading of their own machine, not a developer statement, and no second player has confirmed it. The date is approximate: the post was still rendering with a relative timestamp when the thread was read on 2026-08-05.

Reports of a black screen instead of the game on Steam Deck and on desktop Linux, with reporters pointing at the compatibility badge the store displays. Whether the Deck and the desktop Proton cases are the same fault has not been established by anyone, and there has been no developer reply to either. The date is approximate; the posts carried relative timestamps when the thread was read on 2026-08-05.

Turning the wheel on the way to the Foreman opens a hatch down into the subcity. Leave the area before going through it and the hatch is shut when you return, with the wheel now permanently non-interactive. Two players reported being hard-blocked, neither has posted a way past it, and there has been no developer reply. The date is approximate: the posts were rendering with relative timestamps when the thread was read on 2026-08-05.

One report describes being autosaved inside a boss arena where the fight appears to need the Entanglement Overdrive skill, with no route back out. It has no replies. Nobody has confirmed or refuted whether the arena can be left, whether the boss is genuinely gated on that skill, or whether the autosave is recoverable, so "softlock" here is the reporter’s word and not a verdict. The skill name is the solid part: a player typed "Entanglement Overdrive" out in full in the same megathread, which is what lifts it above a machine caption reading it as "Enhancement". The date is approximate.

A report from the prologue that the second enemy never appears, leaving the sequence unable to advance. One reporter, no replies, no developer response, and nobody has said whether reloading clears it. The date is approximate — the post was rendering with a relative timestamp when the thread was read on 2026-08-05. Possibly related and deliberately not merged: v1.0.8 fixed “an issue with the cloud streaming version of the game where delayed enemy spawns could block game progression”. That is the same shape, on a platform this report does not name, so it is recorded as an adjacent fix rather than as this one being resolved.

A report that the screen goes black after the Rangifer boss fight and stays black, with no crash and no return to gameplay. No replies and no developer response. The boss name is written-source only: it comes from creator video titles and from both established wikis, and has never been read off the game client, so it is the spelling everyone publishes rather than a confirmed in-game string. The date is approximate.

After an unexpected power loss or hard shutdown, the game no longer recognises existing save data. A developer replied to the original report without offering a solution, and later reposted a community explanation that the game stores save metadata separately from the save itself: if the metadata is missing, the save may not appear in the load menu even if the save file exists. That repost is useful evidence about the failure shape, not a published recovery procedure.

The game closes to desktop with an EXCEPTION_ACCESS_VIOLATION error. The report in the megathread carries no reproduction steps and no developer reply, and no second reporter was recorded when the thread was read, so this is an open report rather than an established pattern. The date is approximate.

Players report the game crashing during cutscenes. The cause is contested and this record does not pick a side: one reporter says disabling DLSS and upscaling stopped it, while another on an RTX 5080 still crashes at minimum settings with DLSS off. Both accounts cannot describe the same fault. No cause has been established by anyone and there has been no developer reply to either post. The date is approximate — page 6 of the thread was rendering these posts relatively on 2026-08-05.

Two players in the pinned Game Freak message thread describe repeated Unreal Engine crashes on AMD cards: one names a Radeon RX 9070 XT with driver timeout errors, and another names a Radeon 7800 XT with crashes regardless of graphics settings. Sam [developer] replied that the team is trying to figure out what is happening with 9070 XT users, and separately that crash bugs are being reported back to the team for investigation and fixes. That is an acknowledgement of the crash class, not a published cause and not a fix.

Players describe two versions of the same failure shape: parries and dodges registering late or being dropped, heals not firing after repeated presses, and roughly a second between a run input and the character running. The newest corroboration is ContinuumX’s healing report, which ties the symptom to animation lock after aiming, skills, Blade Arts and assassinations; Wildchants and Valegor report the same shape on heal, parry and dodge. Sam [developer] later reposted ContinuumX’s report into the pinned bug megathread, which confirms the report is being tracked. It does not settle whether this is input being dropped, input intentionally refused by game state, or a mixture of both.

A report that landing a perfect block produces no on-screen feedback, leaving a player unable to tell a successful parry from an ordinary guard except by the damage they took. The reporter files it as a bug; whether it is a bug or the intended presentation has not been established by anyone, and no developer has replied. The date is approximate.

Prompts display glyphs for a controller other than the one connected. Sam [developer] named controller glyphs in the bug thread among the things being looked at, and the 9 August notes then shipped “fixed a bug causing button icon type changes to not be saved correctly” — which is the neighbouring fault, not this one. A setting that would not save is a different bug from a setting that displays the wrong glyph, and this record does not move to fixed on the strength of an adjacent line. The date here is approximate.

A report that with a Switch Pro Controller on button layout C the face buttons are mapped the wrong way round. One reporter, no replies, no developer response, and nobody has said whether another layout avoids it. The date is approximate.

Two controller complaints from the same corner of the megathread: a saved button configuration reverting to Type B, and a DualShock 4 producing no rumble. The 9 August notes speak to the first and say nothing about the second — “fixed a bug causing button icon type changes to not be saved correctly” is a settings-persistence fix in exactly this area, and v1.0.7 also made the “interact” button remappable. Whether the configuration half is the same bug has not been established by anyone: no reporter has come back on 1.0.7, and the notes do not name Type B or DualShock 4. Recorded as two reports that shared a corner of a thread, not as a shared cause, which is why the patch can plausibly close one and not the other.

Players on 3840×2160, 2560×1440 and 5120×1440 displays report the in-game resolution list ending at 1920×1080. The developer has acknowledged a resolution-reporting bug, and separately Sam [developer] asserted in the bug thread on 3 August at 7:04pm that 4K settings exist — an assertion players in the same thread say does not match what they can select. No cause and no working fix has been published by anyone, including the developer.

The game does not render natively at ultrawide aspect ratios and ships no field-of-view slider. It is the loudest launch complaint on the Steam forums. The v1.0.7 Steam notes now list “Ultrawide monitor support” for subsequent patches, but not in v1.0.7 itself. No date, scope or aspect-ratio list has been named.

Select DLSS and the game is back on AMD FSR1 the next time it launches. Frame generation, field of view and film grain are reported as failing to save in the same way. Sam [developer] confirmed the upscaler reversion in the bug thread on 3 August at 8:13pm, then replied in the pinned Game Freak message thread that the team is aware of the DLSS-to-FSR reset and planning to fix it.

A report that the V-Sync option is unavailable when DLSS is selected. Whether that is a bug or a deliberate restriction has still not been stated. v1.0.7 does carry a V-Sync fix — “changing V-Sync settings will no longer impact the player’s resolution settings” — and that is a different fault: one is a setting that cannot be reached, the other is a setting that reached too far. The reason to re-test anyway is that the second half of this record has genuinely changed. It used to say the upscaler resets on every launch so the setting this interacts with does not hold either; the notes name that reset as fixed, so the interaction can now be tested cleanly for the first time.

Reports of hitching while moving through the world and during shader compilation, with the CPU reported pegged at 100% while it happens. Part of this is expected work: BenchmarKing’s settings testing documents a shader compilation step on first launch, so a first session that stutters and then settles is the build behaving as designed. The traversal stutter and the pegged CPU are the parts nobody has verified, explained or replied to. The date is approximate.

Framerate drops in the Xbox Series X performance mode, acknowledged by the developer. This record said until 2026-08-10 that no Xbox build number had been published to check against; that was wrong. The publisher’s support centre gives Xbox Series as 1.0.7.0, so the 9 August patch did reach the console and there is a number to compare with. What still does not exist is an Xbox-specific note: nothing in the changelog is addressed to console performance, and no reporter has retested this on 1.0.7.0. The date is approximate — the report carried a relative timestamp when it was read on 2026-08-05.

Players report seeing no difference with ray tracing enabled, and in places fewer reflections than with it off. This is the one entry here with independent measurement behind it: BenchmarKing measured the setting at a 2% cost in a quiet scene and up to 7% elsewhere for a difference it describes as barely visible, and found that in places it disables screen-space reflections without replacing them. Whether that is a bug or simply the state of the implementation has not been established, so it sits on the watch list rather than being called either. The date is approximate.

Players report interface text that is unreadable at their display size and subtitles that never show. PC v1.0.7 adjusted text size throughout the game with no control over it; v1.0.8 added the control — subtitle size at five steps from Extra Small to Extra Large, though gameplay subtitles outside cutscenes stay at Medium above that. Neither note addresses the missing-subtitles half of this record, and a fix for text appearing unintentionally scaled down elsewhere is still only on the forward list.

This record is unusual and worth reading as much for how it got here as for what it says: the developer named it before we did. GAME FREAK listed "camera adjustments" first among the changes in its 5 August patch statement, and press coverage of that statement — GameSpot's headline calls the cameras broken — treats camera complaints as one of the launch's two most common. What no source we hold provides is the specific fault: nothing states whether the problem is the lock-on, the collision behaviour in tight spaces, the sensitivity range, or something else. So the record names what the developer named and stops there.

A report that the character model rendered on the Equipment screen is visibly lower quality than the one in gameplay. Cosmetic, one reporter, no replies. It is recorded because a player who notices it should know somebody else has seen it too and that no settings change has been reported to affect it. The date is approximate.

Three world and interface glitches reported separately in the megathread: falling through the floor near the bunker, rock textures rendering transparent, and the skill-tree cursor moving inverted. They are grouped in one record because each is a single unreplied report, not because a shared cause has been established. The bunker location is the reporter’s wording and has not been checked against a map. The dates are approximate.