Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Start with Low quality, a 30 FPS cap, and native output: 1280×800 on Steam Deck or 1280×720 on a low-end Windows PC. Reduce shadows and post-processing before textures, and check card and menu text after every resolution change. This is a cautious starting profile inferred from the published GTX 1060 minimum, not a measured performance guarantee. Deadhand Theater is still unreleased, so there is no official Steam Deck preset or verified FPS data yet.
What Deadhand Theater is—and why its settings need a cautious approach
Bag Track Games describes Deadhand Theater as “a dark, turn-based roguelike deckbuilder where you play poker hands to command your shadow puppet’s attacks.” Its systems are deliberately dense: you can sacrifice body parts for active effects, build a deck with cards and sigils, buy talismans, reattach limbs, and deal with hexes and stage modifiers. The itch.io page lists 60 talismans, 40 sigils, 45 hexes, 25 grafts, and 30 stage modifiers. Those cards, icons, and tooltips make readability more important than chasing the highest possible visual preset.
The current itch.io build is v0.3.1, updated 9 September 2026. The Steam page lists Bag Track Games as both developer and publisher, gives a release date of “To be announced,” and says the game is not yet available on Steam. SteamDB identifies the parent app as Windows-only and lists Unreal Engine. That metadata does not establish SteamOS or Proton compatibility, and neither the developer nor the store has published a Steam Deck rating, Deck graphics preset, complete graphics-menu breakdown, or FPS benchmark.
Accordingly, every profile below is a sensible first configuration for testing the released build—not a promise that a particular Deck or PC will hold a particular frame rate.
#1 Best Overall
- 1TB NVMe SSD
- 1280 x 800 HDR OLED display with premium anti-glare etched glass, 7.4" Diagonal display size up to 90Hz refresh rate
- Wi-Fi 6E
- 50Whr battery; 3-12 hours of gameplay (content-dependent)
- Carrying case with removable liner
Published PC requirements
These are the only official hardware targets currently listed on Steam. They are a baseline for judging a low-end Windows machine, not a substitute for a game-specific benchmark.
| Target | Operating system | Processor | Memory | Graphics | Storage |
|---|---|---|---|---|---|
| Minimum | Windows 10 | Intel Core i3 | 8 GB RAM | GeForce GTX 1060 | 1 GB available |
| Recommended | Windows 10 | Intel Core i5 | 8 GB RAM | GeForce RTX 2060 | 1 GB available |
The listing does not specify the exact Core i3 or Core i5 generation, whether the GTX 1060 is the 3 GB or 6 GB model, or whether the 1 GB figure includes updates. Treat those labels as broad classes. A PC with an older integrated GPU cannot be assumed to meet the stated graphics minimum simply because its CPU and RAM are sufficient.
Best starting settings on Steam Deck
Use the following order so you can identify which change helps. Keep a simple note of the setting, the scene tested, and whether movement feels consistent; changing several options together makes stutter harder to diagnose.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Set the game to 1280×800. This is the Deck’s native output and avoids an unnecessary scaling step. If the game offers a render-scale slider, leave it at 100% for the first test.
- Choose Low, or the lowest available preset. The game may expose different labels in its final build; select the preset that clearly reduces effects rather than assuming a particular menu name.
- Cap the game at 30 FPS. A stable cap is the appropriate first target for a turn-based game. Use the game’s limiter if available; otherwise use the Deck’s frame-rate control.
- Lower shadows first. If a separate shadow-quality or shadow-distance option exists, reduce it to Low or the minimum value.
- Lower ambient effects and post-processing next. Bloom, ambient occlusion, depth of field, motion blur, volumetric effects, and similar image processing can be expensive on a small GPU. Disable them or select their lowest setting when the menu provides those controls.
- Leave textures higher when possible. Texture quality often affects memory use more than frame-rate. Keep it at Medium or the next setting above Low only if frame pacing remains consistent and the text on cards stays sharp. If the game stutters or reports memory pressure, return textures to Low.
- Check the interface before raising quality. Open a card description, a talisman screen, and any combat tooltip. If letters look soft or icons are difficult to distinguish, restore native output before experimenting with more effects.
- Raise one option at a time. Once Low settings hold the 30 FPS cap in a representative combat scene, increase a single setting, play the same scene, and keep the change only if pacing and readability remain acceptable.
Deck profile for maximum consistency
| Option | Starting value | Reason |
|---|---|---|
| Output resolution | 1280×800 | Native Deck resolution; avoids a first-pass scaling penalty |
| Preset | Lowest available | Safest way to stay near the published GTX 1060 class baseline |
| Frame-rate cap | 30 FPS | Prioritizes consistent frame pacing over an unstable higher cap |
| Shadows | Low or Off | First graphics reduction to try when frames vary |
| Post-processing and ambient effects | Low or Off | Removes costly effects while preserving core textures |
| Textures | Medium if stable; otherwise Low | Preserves card and character detail without ignoring memory limits |
| Render scale | 100% initially | Maintains text and icon clarity while you establish a baseline |
If 30 FPS is not sustained at this profile, reduce render scale in small steps rather than jumping immediately to a very low resolution. After each change, inspect the same card and menu screens; a few extra frames are not useful if the deck-building interface becomes hard to read.
Best starting settings on a low-end Windows PC
- Choose 1280×720. Use fullscreen or borderless mode, whichever gives the smoother result on your system. This resolution is a practical first step for a 16:9 display and leaves room to reduce render scale later.
- Select the lowest quality preset. Do not begin at Medium merely because the machine has 8 GB of RAM; the published minimum calls for a GTX 1060, and the exact performance of older cards is unknown.
- Set a 30 FPS cap. An uncapped frame rate can create uneven delivery and makes it harder to tell whether a setting change helped.
- Reduce shadows, ambient effects, and post-processing. Apply these changes before lowering texture quality so cards and menus remain legible.
- Close overlays and capture utilities while diagnosing. Turn off recording, hardware-monitor overlays, and unnecessary launchers temporarily. Re-enable them one at a time after establishing that the game itself is stable.
- Test one variable per run. Use the same battle or menu sequence, change one option, and compare hitching, input response, and text clarity.
Windows profile for a machine close to minimum
| Option | Starting value | Adjustment if performance is poor |
|---|---|---|
| Resolution | 1280×720 | Lower render scale or resolution in small steps |
| Display mode | Fullscreen or borderless—whichever is smoother | Switch modes once to check for a driver-specific issue |
| Preset | Low | Keep Low while diagnosing; do not raise several settings together |
| Frame cap | 30 FPS | Keep the cap until frame pacing is consistent |
| Shadows and post-processing | Low or Off | Reduce before textures |
| Textures | Low initially | Try Medium only after stutter is resolved and memory use is stable |
Resolution and render scale: protect the interface first
Deadhand Theater communicates through cards, sigils, talismans, grafts, and combat tooltips. Resolution changes therefore have a direct usability cost that a purely visual game might avoid.
When to keep native output
Keep 1280×800 on Deck when the game holds its cap and the interface is clear. Native output gives the cleanest one-to-one presentation for the handheld’s panel. On a Windows monitor, keep 1280×720 if the game is already smooth and text is readable.
Rank #2
- International (UK) Version
- 7.4” diagonal, HDR OLED, 1280 x 800 x RGB, up to 90Hz Refresh rate, High performance touch, <0.1 ms Response time, 1,000 nits peak brightness (HDR), 600 nits (SDR)
- SteamOS 3.0 (Arch-based)
- 512GB NVMe SSD, 16GB LPDDR5 on-board RAM (5500 MT/s quad 32-bit channels), microSD UHS-I supports SD, SDXC and SDHC
- 6 nm AMD APU, CPU: Zen 2 4c/8t, 2.4-3.5GHz (up to 448 GFlops FP32
When to reduce render scale
Use render scale only after Low settings, reduced shadows, and reduced post-processing have been tried. Lower it gradually, then open a card description and a settings menu. If thin lettering, numbers, or icon edges become difficult to distinguish, move back up one step even if the frame counter improves.
Why an unusually low resolution can be counterproductive
A very low internal image can make menus blurry and force extra effort during every fight. In a turn-based deckbuilder, that trade-off is rarely worthwhile unless the alternative is severe hitching. Favor a stable, readable image over a peak frame-rate number.
Frame-rate caps and frame pacing
Thirty frames per second is the conservative target because the game is turn-based and no official higher target has been measured. A cap prevents the GPU from rendering unnecessary frames during simple scenes and makes fluctuations easier to see.
- Stable 30 FPS: Keep it. This is preferable to a fluctuating 40 or 60 FPS profile for the initial setup.
- Frequent drops below 30: Reduce shadows and post-processing if they are not already at minimum, then lower render scale. If drops occur only when new areas load, note whether they are one-time hitches or repeat during ordinary combat.
- Frame counter looks fine but motion feels uneven: Check for background recording, overlays, power-management changes, or a mismatch between an in-game cap and an external cap. Test with one limiter enabled at a time.
- Very high but unstable readings: Keep the 30 FPS cap. A higher average does not compensate for uneven delivery during card selection or transitions.
There is no published basis for promising 40, 60, or any other exact FPS figure on a specific Deck model or PC. Treat any such number from an individual configuration as a local observation, not a guaranteed setting for everyone.
Which graphics options to lower first
| Priority | Option group | Why it is a sensible first move | What to watch for |
|---|---|---|---|
| 1 | Shadows | Often has a large GPU cost and does not change card information | Loss of depth or visual separation in stages |
| 2 | Post-processing | Can remove multiple screen effects at once | Menus or effects may look flatter; confirm that text remains clear |
| 3 | Ambient effects and occlusion | Reduces background shading and atmospheric work | Less contrast around characters and props |
| 4 | Render scale | Directly lowers the number of pixels rendered | Soft card text, small icons, and blurred menus |
| 5 | Textures | Can reduce memory pressure when necessary | Less detail on cards, puppets, and stage assets |
This order is a starting heuristic, not a claim about the final menu implementation. If a released build combines several effects under one slider, use the closest available control and retest.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Input: plan for a mouse-first interface
Steam assigns Deadhand Theater the user-defined “Mouse Only” tag. That does not document every input option in the final build, but it does make a mouse the most defensible primary input for desktop or docked play.
Rank #3
- Operating System: SteamOS 3.0
- On a PC, keep a basic USB gaming mouse available so you can select cards, sigils, and tooltips precisely.
- On Deck, test the built-in trackpads or touchscreen before buying a controller accessory. The final control mapping is not published, so do not assume every action has a comfortable gamepad equivalent.
- If you dock the Deck, use a mouse first when diagnosing a control problem. This separates an input-mapping issue from a performance issue.
- Check that pointer movement and text selection remain responsive at the 30 FPS cap; a lower frame rate should not prevent accurate menu selection.
A repeatable tuning method
Use a short, controlled loop rather than changing the whole graphics menu after one slow scene.
- Record the current resolution, preset, cap, and the individual options you changed.
- Choose a representative sequence containing a battle, card inspection, and a transition or stage scene.
- Play that sequence once without changing anything. Note visible hitching, delayed input, and whether text or icons are hard to read.
- Change exactly one option—such as shadows from Medium to Low—and repeat the same sequence.
- Keep the change only if it improves consistency without harming readability.
- After finding a stable Low profile, raise one setting at a time. Stop when the first repeatable hitch appears, then revert the last change.
Because the game is unreleased, this process is more reliable than copying a claimed “best” FPS setting from another machine. Drivers, Deck power profiles, screen resolution, and future game updates can all change the result.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Can a low-end PC run it?
PC at or above the published minimum
A Windows 10 computer with a Core i3-class processor, 8 GB of RAM, and a GTX 1060-class GPU matches the listed minimum specification. Begin at 1280×720, Low, and 30 FPS. Meeting a minimum list does not establish a particular frame rate or guarantee that every scene will be smooth; it only means the hardware aligns with the developer’s stated baseline.
Free tools Windows power users keep installed
One-click scans. No signup required.
PC near the recommended graphics target
A Windows 10 system with a Core i5-class processor, 8 GB of RAM, and an RTX 2060-class GPU aligns with the recommended specification. You can still begin with the conservative profile, then raise shadows, post-processing, or textures individually if the released build remains stable. The listing does not state a recommended resolution or FPS target.
Older integrated graphics
Do not assume an older integrated GPU will run the game because it has 8 GB of RAM. The only published minimum graphics device is a GTX 1060, and no equivalent integrated-graphics requirement is provided. Such a system needs testing against the released build rather than a promise based on CPU or memory alone.
Steam Deck models
No official Deck rating, Deck preset, or Deck benchmark is published. SteamDB’s Windows-only metadata means SteamOS compatibility is not established by the store listing. If you try the game on Deck after release, start with the native-output Low profile and confirm that it launches, accepts your chosen input, and maintains readable menus before investing time in higher settings.
Rank #4
- Valve is entering the gaming console marketplace with the new Steam Deck, a console geared towards PC gamers. The Steam Deck can be docked to a monitor, and used as a PC, or docked to a TV.
- Players can play a huge variety of games at any time with the comfort of a console and the freedom of a PC. Not anti-glare screen.
- Like the name suggests, the Steam Deck will include upgraded 1TB storage, and will include a carrying case. A micro SD slot will also enable expanded storage.
- Valve partnered with AMD to create a specialized APU optimized for handheld gaming, and Valve says the chip will deliver performance to run AAA gaming titles.
- The Steam Deck is outfitted with a 7-inch touchscreen, and two trackpads under the control sticks that allow gamers to operate games never designed outside of mouse and keyboard capabilities.
Problems you may encounter and what to try
The game launches but the interface is blurry
Restore native output, return render scale to 100%, and check the display mode. Lower effects rather than pixels first. Verify readability on a card description and a talisman screen, not just on the title screen.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Combat feels smooth but transitions hitch
Keep the 30 FPS cap, close capture and overlay software, and test again with post-processing and ambient effects reduced. If the hitch repeats only when a new stage loads, record that pattern separately from continuous gameplay; it may not respond to the same setting changes.
Performance worsens after raising textures
Return textures to Low and repeat the same scene. Texture quality can increase memory pressure even when other options are inexpensive. Raise it again only if the complete sequence remains consistent.
Controls feel awkward on Deck
Use the trackpad or touchscreen as a mouse substitute and test the game with a physical mouse when docked. The “Mouse Only” tag makes pointer input the safest assumption until the final control scheme is documented.
You cannot find a setting named in this guide
Menu labels may differ between the v0.3.1 itch.io build and the eventual Steam release. Match the function rather than the wording: look for controls governing shadows, ambient effects, post-processing, textures, output resolution, render scale, and frame limiting.
Recommended Free Tools
What is known—and what is still unconfirmed
- The game is unreleased on Steam; its release date is listed as “To be announced.”
- Steam lists Windows 10, Core i3, 8 GB RAM, GTX 1060, and 1 GB storage as minimum requirements.
- Steam lists a Core i5, 8 GB RAM, RTX 2060, and 1 GB storage as recommended hardware.
- SteamDB currently reports Windows support and Unreal Engine.
- No official Steam Deck compatibility rating, Deck preset, full graphics-option list, or measured FPS result has been published.
- The 30 FPS Low profiles in this guide are conservative inferences from those facts, not benchmark results.
Pre-release and first-launch checklist
- Confirm that the build you install is the current one; the itch.io page identifies v0.3.1 as updated 9 September 2026.
- On Windows, verify that the machine is running Windows 10 or a later supported configuration and has at least 1 GB of free storage beyond whatever updates require.
- Have a basic USB gaming mouse available for desktop or docked play.
- Start at native Deck output or 1280×720 on PC, Low quality, and a 30 FPS cap.
- Reduce shadows and post-processing before textures.
- Test a battle, a card description, and a menu before raising any setting.
- Change one option per test and keep a note of the result.
Bottom line
For now, the most defensible Deadhand Theater setup is Low quality at 30 FPS: 1280×800 on Steam Deck and 1280×720 on a low-end Windows PC. Cut shadows and post-processing before sacrificing texture detail, and judge every change by both frame pacing and the readability of cards and tooltips. The game has not shipped on Steam, SteamDB lists Windows support only, and no official Deck or FPS testing exists, so treat this as a careful launch profile that must be validated against the released build.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
