Steam 1.0.1: camera stutter fix and remaining problems

What does Steam update 1.0.1 actually fix?

The official 1.0.1 announcement, published 5 November 2026 at 02:17 UTC, identifies two corrections:

• On certain system configurations, the camera could remain in slow motion after combat effects such as hit stop, Just Dodge or Just Shield ended, producing choppy visuals.
• Some damage multipliers were calculated incorrectly. Correcting them slightly reduces excessive late-game damage.

The announcement does not say all camera, input or frame-pacing problems are fixed. It explicitly warns that stuttering may remain, depending on the system.

How can I tell whether my problem matches?

Compare what happens before, during and after the symptom. A camera that stays slow after a combat slow-motion effect matches the announced category more closely than a black screen, unresponsive button, or general slowdown.

Before comparing results, check whether Steam has an update pending. Record the version if the game displays it; do not guess an installed version from the date you downloaded it. Also identify whether you launched the full game or the separate demo using the edition guide.

This is a way to narrow a report, not a diagnostic test we have run on your system.

What should I do if stutter remains?

Use the developer’s pinned Bug Reports thread. Although its original post dates from the demo in 2025, the full game’s 1.0.1 announcement explicitly directs players there.

First search for a matching report. Then supply the symptom, reproduction steps, screenshots or video if possible, and the PC specifications requested by the developer. Include your edition and any version information you can actually confirm.

For a reproducible report, describe whether the issue follows a particular combat effect, affects the camera alone, or appears throughout play. The reporting checklist provides a compact structure.

Does changing Steam Input or Proton definitely fix it?

No verified universal fix is established by the sources inspected here. Individual forum posts describe particular controller, Steam Input or Proton experiences, but those are player reports. They do not prove the cause of your symptom or a reliable setting for every system.

The Steam store lists Windows requirements; that is not a native Linux support claim or a Steam Deck performance certification. Keep platform and compatibility-layer details in a report rather than treating them as interchangeable with a Windows installation.

Could an older damage guide now give different results?

Yes, the developer’s multiplier correction is a concrete reason that a pre-update damage result may differ. The announcement does not provide a replacement formula or a table of affected multipliers, so this site does not calculate damage from it.

The Reward condition finder only retrieves official reward labels and conditions. For damage-related achievement wording, distinguish single-hit targets from totals using single-run and total conditions; a listed threshold is not a recommended build.

What is the version boundary of this page?

Sources were checked on 6 November 2026. 1.0.1 is the latest Steam update announcement inspected, not a claim that we installed or benchmarked it. The official announcement and its linked report thread are the primary sources. Nintendo Switch patch parity remains unverified.