ForgeTax performance: System Specs, FPS Cap, and Fixes

ForgeTax performance depends heavily on visual effect handling during forging streaks and sword breaks, but developer GraveYardDev has deployed dedicated patches to stabilize frame pacing. While the lightweight indie roguelite demands relatively modest hardware on paper, initial release builds showed frame-time spikes during rapid hammer strikes, relic activations, and dragon penalty sequences. Recent updates have introduced an adjustable frame rate limiter, visual debris optimizations, and anonymous diagnostic tools to ensure steady gameplay across various PC configurations.

ForgeTax System Requirements

Before troubleshooting frame drops or visual hitches, ensure your hardware meets the official requirements published on Steam by GraveYardDev.

Both tiers require a 64-bit processor and operating system. While storage overhead is small at just 2 GB, graphics processing requirements demand dedicated VRAM to handle real-time lighting, sword materials, and particle fragmentation on the anvil.

Recent Engine and Performance Optimizations

Player feedback highlighted stuttering during critical smithing moments shortly after launch. In response, the developer rolled out two targeted updates that overhauled visual and system load:

• Fragment and Salvage Cleanup: The 21-Day Contract update restructured how blade fragments and salvage particles render when a sword shatters, removing the sudden frame freeze that previously accompanied failed attempts.
• Default Frame Rate Limit: The game now defaults to a 60 FPS cap. This change prevents GPUs from running at maximum power in menus or rendering unnecessary frames when the game window is inactive.
• Frenzy and Interface Work: The October update optimized repetitive rendering routines triggered during Frenzy hammering, reducing micro-stutter when striking weapons in rapid succession.
• Debris and Tail Sequences: Debris processing during the dragon's penalty tail animation received a performance pass, cutting sudden load spikes when replacement swords are dropped into the chamber.
• Asset and Build Compression: General build compression and texture handling were revised to smooth out asset loading between contract days and merchant visits.

Optimizing In-Game Settings for Smoother Framerates

If you encounter inconsistent frame times, several built-in options can help stabilize your session:

1. Adjust the Display Frame Limit: Navigate to your display settings in the main or pause menu. If your monitor runs at a higher refresh rate but your system drops frames during intense particle bursts, lock the cap to 60 FPS to maintain smooth pacing.
2. Reduce Viewport Movement: In the accessibility and controls section, you can disable excessive head bob. Hotfixes lowered the default working viewpoint at the anvil, removing previous camera jumps that caused visual disorientation during mode transitions.
3. Prevent Inactive Background Drain: The engine throttles load when ForgeTax is minimized or unfocused. Avoid using third-party borderless window forcing tools that might override this built-in power-saving behavior.

Steam Deck and Handheld Performance

ForgeTax has not received an official compatibility rating from Valve and remains untested in the official Steam Deck verification program.

According to third-party hardware assessments from CanIRun.gg, the Steam Deck's integrated RDNA 2 GPU theoretically scores below the desktop Radeon RX 560 listed in the game's minimum desktop requirements. While the system's 16 GB LPDDR5 memory easily clears the game's minimum specifications, visual stuttering can occur on handheld hardware if framerates are left uncapped. Handheld players testing the game through Proton should start at native resolution (1280x800) with the in-game 60 FPS cap engaged to prevent rapid battery drain and GPU thermal throttling.

Reporting Performance Issues and Diagnostic Logs

The developer actively collects anonymous performance diagnostics to address remaining frame-time spikes across varying hardware setups.

• Anonymous Play Records: Under settings, players can opt into sending anonymous play data. This telemetry measures frame-stutter metrics, relic setups, and round progress. Data is routed through Cloudflare, stored for up to 90 days, and excludes Steam IDs, account names, and save file contents. You can toggle this feature off at any time.
• Direct Bug Reports: If you experience persistent crashes, freezing, or severe frame drops, GraveYardDev accepts diagnostic logs and save files directly at dev.graveyard.games@gmail.com or via the pinned Bug Reports & Feedback thread on the Steam Community forums. When sending a report, include your PC specifications, current day, active sword type, and equipped relics.