ForgeTax Stuttering & Low FPS Fix: Ultimate Performance Optimization Guide
ForgeTax from GraveYardDev is one of those games that grabs you by the collar. You heat a blade, haul it to the anvil, and hammer away to snowball your fortune, all while the dragon’s tribute breathes down your neck. It’s a first-person sim, a risk-reward gamble and a roguelite rolled into one, and it works.
It also lives and dies on timing. Landing a perfect strike or riding Frenzy mode needs your inputs to hit right now. So when the game hitches at the wrong moment, you don’t just lose a few frames. You lose the blade, the run and the gold you were about to cash in. Plenty of players are hitting aggressive stuttering, micro-freezes, low average FPS and wonky frame pacing. A big chunk of the mixed Steam reviews comes from exactly this: people mad at frame drops, not at the game design.
The cause is easy to see once you look at what’s on screen. Physics, dynamic lighting from the forge fire and sparks bursting off every anvil hit all pile onto your CPU and GPU at once. I dug through community threads, hardware discussions and dev patch notes, and this guide collects the fixes that actually work. Work through it top to bottom and your forge should run buttery.
How to Fix ForgeTax Crash on Launch, Freezing, and Black Screen Issues on PC
Step 1: Check Your Rig Against the Specs
Roguelite sims often ship a bit rough in early patches, so your hardware headroom matters more than it should. Compare your PC to the official requirements first.
| Component | Minimum | Recommended |
|---|---|---|
| OS | Windows 10 64-bit | Windows 10/11 64-bit |
| CPU | Intel Core i5-6600 / AMD Ryzen 3 1200 | Intel Core i5-8400 / AMD Ryzen 5 2600 |
| RAM | 8 GB | 16 GB |
| GPU | GTX 960 / RX 560 | GTX 1060 / RX 580 |
| DirectX | 11 | 11 |
| Storage | 2 GB | 2 GB (SSD highly recommended) |
The Two Sneaky Culprits
RAM. If you’re sitting near the minimum, 8 GB is the usual suspect behind sudden hitching. ForgeTax tracks relic effects, sword synergies and visual asset states all at once. When your memory fills up, Windows dumps data onto the drive as virtual memory (the page file), and you feel it as nasty micro-stutters. Close your browser and any other background junk before you launch.
Your drive. The game is only 2 GB, but if it sits on a mechanical HDD you’ll get loading hitches when you flip between menus or roll items at the relic machine. Move it to an SSD and those latency spikes vanish. It’s the cheapest fix on this list if you own a spare SSD.
Step 2: In-Game Graphics Settings That Matter
Start here. It’s the quickest way to take pressure off your GPU, and you can keep the dark, moody look the game is known for.
| Setting | Recommended | Why |
|---|---|---|
| Display Mode | Fullscreen | Borderless makes Windows render background windows alongside the game, which adds input lag and micro-stutter |
| Resolution | Native (usually 1920×1080) | On an old or integrated GPU, 1600×900 can give roughly 20-30% more performance |
| V-Sync | Off | Adds noticeable input delay on anvil strikes; use a driver-level cap or G-Sync/FreeSync instead |
| Shadow Quality | Medium or Low | Real-time shadows from the forge fire are brutal on resources |
| Anti-Aliasing | SMAA or low FXAA | Skip heavy supersampling on a GTX 1060 or weaker |
| Particles / Volumetrics | Medium | Sparks and furnace heat distortion tank frames during Frenzy |
| Texture Quality | High at 4 GB+ VRAM, Medium at 2 GB | Prevents texture-swapping lag |
Shadows first. Dropping shadow quality gives the biggest FPS jump for the least visual damage, and the forge still looks properly menacing. Particles come second. Hammering during Frenzy throws a huge number of sparks at your GPU, and trimming the count keeps frame delivery steady when you’re mashing the strike.
Step 3: Driver Control Panel Tweaks
Driver-level settings can override or back up the in-game options, and they give indie games a solid baseline boost.
NVIDIA Control Panel
- Right-click your desktop and open NVIDIA Control Panel.
- Go to Manage 3D Settings → Program Settings, then pick ForgeTax from the dropdown (or hit Add and point to the game’s .exe).
- Set Power Management Mode to Prefer Maximum Performance. This stops the GPU from dropping into low-power states during quiet moments, so it doesn’t lag behind when the action ramps up.
- Set Shader Cache Size to Unlimited or 10 GB. This is the big one. A tiny cache makes Windows toss old shader data, and then the game recompiles and reloads it over and over, which is a constant micro-stutter factory.
- Set Low Latency Mode to On or Ultra. This shrinks the frame queue the CPU builds, and hammer swings feel snappier.
- Set Texture Filtering – Quality to High Performance.
AMD Radeon Software
- Open AMD Software and go to Gaming → Games → ForgeTax.
- Turn on Radeon Anti-Lag to cut input buffering latency.
- Turn off Radeon Chill unless you really need to cap thermals.
- Set Texture Filtering Quality to Performance.
- Make sure Surface Format Optimization is on.
Step 4: Windows Fixes That Clear Out the Noise
Background tasks, power delivery and driver mess all affect frame pacing. These four fixes clean that up.
1. Hardware-Accelerated GPU Scheduling (HAGS). It lets your graphics card manage its own video memory instead of leaning on the OS scheduler. Press the Windows key, type Graphics Settings, open it, switch HAGS On, then restart.
2. Windows Game Mode. Go to Settings → Gaming → Game Mode and make sure it’s On. It prioritizes resources for the running game and keeps Windows Update from kicking in mid-session.
3. Clean driver install with DDU. Broken or outdated display drivers cause weird, hard-to-trace problems.
- Download Display Driver Uninstaller (DDU) plus the newest standalone driver from NVIDIA or AMD.
- Boot into Safe Mode.
- Run DDU to wipe every trace of the old driver.
- Restart into normal Windows and install the fresh driver pack.
4. Audio device conflict. This one is odd but common. Windows keeps polling inactive audio profiles, and that can cause micro-freezes. Right-click Start, open Device Manager, expand Sound, video and game controllers, and disable any unused outputs, old motherboard sound drivers or leftover virtual audio devices.
Step 5: Fix Your 1% Lows With a Frame Cap
You’ve seen it: the counter says 60 FPS, but the game feels like a slideshow. That’s bad frame pacing. If one frame takes 16 ms and the next takes 50 ms, you feel a visible hitch, and that’s what a bad 1% low is. Your average looks fine while the experience is rough.
The fix is a flat cap with RivaTuner Statistics Server (RTSS), which is known for very accurate frame limiting:
- Download and open RTSS.
- Add the ForgeTax executable to the profile list.
- Find your stable average FPS in normal play, then set the Framerate limit about 5-10% under your realistic maximum. For example, if you average 75 FPS but dip to 50, lock it at 60.
- The flat limit shrinks the gap between peaks and valleys, so frames arrive at an even, linear rhythm.
A steady 60 beats a jumpy 75 every time, especially in a game where a single missed strike can wreck a run.
Final Verdict
ForgeTax is a great little time-sink, and a few simple changes get rid of most of the stutter. Free up RAM, move the game to an SSD, trim shadows and particles, set an unlimited shader cache, and cap your frames with RTSS. Do that and the forge runs smooth, the blades stay in one piece and the dragon gets paid. Now go hit that perfect strike.
