Most of the published Witch the Showdown performance fixes are already in the demo patch 1.1.09.2, which carries an optimization pass, a Reduce Glow option that is enabled by default, and UI fixes for vertical windows and unusual aspect ratios. On top of that, the graphics options in the game are few: Reduce Glow, the slow-motion speed setting, and a visibility-first option the developers are still working on.

What the latest patch changed for performance

Demo patch 1.1.09.2 is where the list lives, and the same patch ships with the full build:

  • Overall game performance through optimization.
  • Visibility work on the effects that matter. Battle visual effects were adjusted to improve overall visibility, and parry success effects were re-tuned for visibility, so you can see whether a parry landed.
  • Reduce Glow enabled by default, which is the single most obvious thing to check if the screen looks blown out or the frame rate dips when effects fire.
  • UI rendering fixes. A UI rendering issue on vertical windows and unusual aspect ratios was fixed, as was a screen-ratio issue on windows taller than 16:9.
  • Audio fix. Game audio is no longer muted when the game window loses focus.
  • Tournament Mode screens. The card selection screen and the Battle Results screen in Tournament Mode were optimised for performance, which matters because a run spends most of its time in those two screens.

The published system requirements contain no hardware numbers at all, so the store page cannot tell you whether your machine is short on anything: what the requirements actually say.

The graphics options the game ships with

The option list is short, and the developers are still adding to it:

  • Reduce Glow, now on by default.
  • The slow-motion speed setting, which applies to a successful parry and to taking damage. The game is balanced around 100% motion speed, 0% is described as brutally hard, and the developers recommend staying around 25%. Lowering it is also the practical way to learn an enemy's timing.
  • Improving Visual Clarity, which the developers list under future plans. They are currently exploring solutions, and if it remains difficult to balance graphics against visibility they may introduce an option that prioritises visibility over graphical fidelity.

No DLSS, FSR or XeSS support has been announced, and there is no published list of resolution, VSync or frame-rate cap settings.

The slow-motion setting is also the option you will use most on the harder tiers, because enemy attacks change with the tier: the difficulty settings guide.

What players report about frame rate

Player reports in the Steam discussions cover both ends of the range: one player complains the game runs at barely 60 fps natively with the PC pumping out hot air, while another reports a stable 120 fps at 4K. The same thread points out that the usual engine.ini tweak works for Unreal Engine games like this one, and that it worked for them.

The thread also asks for more graphics sliders to fine-tune graphical settings, and reports horrible aliasing, especially on enemy models whose edges look badly jagged during combat. The game is a 2D fighter, so the load is not the problem on most machines; if you are seeing stutter, Reduce Glow and the patch fixes above are the first things to check.

Running it on a handheld is a separate question: the Steam Deck guide.