Onimusha: Way of the Sword’s PC Benchmark Is Live: Reading Your Score, and Fixing the Crash After Shader Compile

Capcom put the official Onimusha: Way of the Sword benchmark tool on Steam and the Epic Games Store on July 14, 2026, almost two months before the September 4 launch. That is unusually early, and it is the smartest thing you can do before you buy: run it, read the number it spits out, and find out exactly where your rig is going to hurt. The catch is that a lot of players are running it and getting a crash right after the shader-compilation bar finishes, or watching frame times fall apart the moment a fight gets busy. Both problems are fixable, and neither one means the full game is broken.

I have spent enough time inside RE Engine titles to know this pattern. The engine itself is not the villain here. Onimusha is a corridor action game running on the same technology that powered Dragon’s Dogma 2 and Monster Hunter Wilds, and it behaves nothing like either of them because the workload is completely different. Below is what the benchmark score actually tells you, what the early crash reports have in common, and the settings that matter once you are in.

What the benchmark score actually measures

The tool runs a fixed sequence of combat and cinematic scenes, then hands you a single number. Capcom’s scoring bands look like this:

• 0 to 4,999: Insufficient Performance
• 5,000 to 14,999: roughly playable, expect compromises
• 15,000 to 24,999: comfortable at your tested settings
• 25,000 and up: Excellent

Do not stop at the headline number. The result screen also breaks out average FPS and 1% low FPS separately for the combat and cutscene portions, and it lists the exact preset, ray tracing state, upscaling method, and frame-generation status it ran with. The 1% low figure is the one that predicts how the game will actually feel. A rig can post a healthy 90 FPS average and still stutter noticeably if its 1% low drops into the 40s during a parry exchange. When you compare runs, compare the combat 1% low, not the average.

One quirk worth knowing: the benchmark lets you toggle DLSS and FSR, so a big score does not always mean your raw hardware is strong. If you scored 20,000 with DLSS 4.5 set to Performance at 4K, you are leaning hard on upscaling, which is fine, but know that is what is carrying you.

The crash right after shader compilation

This is the most common early complaint, and it has a specific cause. On first boot the game compiles a large batch of shaders. If that process is interrupted, starved of disk space, or fed a stale driver, the executable falls over the instant the bar completes. It reads like a game bug. It is almost always an environment problem.

Work through these in order:

1. Update to a current Game Ready or Adrenalin driver, then let shaders finish. RE Engine compiles shaders up front rather than mid-game, which is why the game runs so cleanly once you are past the loading screen. Do not alt-tab or launch anything else while that bar moves. Give it the two or three minutes it needs. If you are not sure your driver is clean, a proper reinstall solves a surprising number of these; our GPU driver update guide walks through the DDU process.
2. Free up disk and raise your shader cache. The compile step writes a cache. If your drive is nearly full it can fail silently. On NVIDIA, open the Control Panel, go to Manage 3D Settings, and set the Shader Cache Size to 10 GB instead of Driver Default. Then delete the game’s existing cache and let it rebuild.
3. Kill overlays before you launch. Discord, Steam, MSI Afterburner, and RivaTuner all inject into the render path, and any one of them can trip a fresh shader build. Turn them off for the first clean run, then add them back one at a time if you want them.
4. Verify the files. The benchmark download is large and large downloads corrupt. Right-click in Steam, Properties, Installed Files, Verify integrity. This catches a bad shader package that no amount of driver work will fix.

If it still crashes on a machine that clears the minimum spec, delete the GameUserSettings.ini so the game rebuilds a default config, then relaunch. A corrupted settings file from an aborted first run will happily crash every subsequent launch.

The VRAM ceiling on 6GB and 8GB cards

RE Engine has a long history of eating video memory when textures are set high, and it warns you about it. Resident Evil 4 Remake famously flagged that 8GB cards needed to drop texture quality at 4K to avoid stutter, and Onimusha carries the same behavior forward. The published tiers make the pattern obvious: the minimum GPU is a GTX 1660 with 6GB, but the “High” 1440p target jumps to an RTX 4060 Ti with 16GB and an RX 6750 XT with 12GB. That is not about raw shading power. It is about frame buffer.

If your card has 6GB or 8GB and the benchmark stutters in a rhythm, that steady hitch-hitch-hitch as new areas load, you are almost certainly filling VRAM and forcing the engine to stream textures over the PCIe bus. The fix is not to lower everything. Drop Texture Quality one step first and retest. On RE Engine that single setting reclaims more VRAM than shadows, effects, and volumetrics combined, and it costs the least visually. Then, if you still have headroom to lose, trim shadow quality from the top preset to a step down.

Ray tracing is safe to leave off here. The developer who previewed the game said plainly that they could not spot a meaningful visual difference with RT enabled, and side-by-side shots looked identical. On this title RT buys you almost nothing and costs frames and VRAM, so switch it off and reclaim both.

Onimusha is single-player, so a game accelerator will not touch your frame times here. If your evenings also include ranked matches where ping is the enemy, that is where WTFast earns its keep, and the free trial is the easiest way to see whether your route to the server is the problem.

When the stutter is your CPU, not your GPU

There is a second kind of hitch that upscaling and texture cuts will not fix, and it is the one RE Engine is genuinely prone to. Dragon’s Dogma 2 shipped in 2024 and choked in dense city scenes, not because GPUs could not keep up, but because the CPU was pinned processing NPC logic and simulation. Onimusha is far more contained than an open-world game, so it will not be as brutal, but the same principle applies: when several enemies attack at once and particle effects stack, the per-frame CPU cost spikes.

If your benchmark shows a strong GPU average but the combat 1% low collapses, look at your processor and your background load:

• Close what is stealing cores. Browsers with a stack of tabs, Chromium-based apps, and launcher clients all sit in the background burning threads. Shut them before you play. Our rundown of what to kill before you game covers the usual offenders.
• Confirm your RAM is running at its rated speed. RE Engine is sensitive to memory bandwidth. If you never enabled XMP or EXPO in the BIOS, your DDR4 or DDR5 is probably running at a slow JEDEC default and your 1% lows are paying for it. Turn the profile on and retest.
• Cap your frame rate a few frames below your refresh. A stable 58 FPS on a 60Hz panel feels smoother than an 80 FPS number that keeps colliding with your refresh ceiling. Frame pacing beats frame count in an action game where timing your parry is the whole point.

If your CPU is genuinely the bottleneck, the deeper diagnosis in our high CPU usage while gaming guide will tell you whether it is a background process, a thermal throttle, or simply an older chip hitting its limit.

Why the same engine ran so differently in Monster Hunter Wilds

It is worth saying clearly, because the comparison keeps coming up: Monster Hunter Wilds launched earlier in 2026 on RE Engine and ran rough enough that its performance became the story. People saw “RE Engine” attached to Onimusha and braced for a repeat. That is the wrong read.

Wilds is a sprawling, streaming-heavy open world with dense ecosystems and long sightlines, and that workload is exactly what RE Engine handles least gracefully. Onimusha is the opposite: hand-built corridors, tight arenas, controlled enemy counts. On a high-end rig the difference is stark. Early hands-on testing on an RTX 5090 at native 4K held a minimum of 119 FPS with no ray tracing and 98 FPS with it, and the tester described the run as silky smooth with no stutter at all. That is RE Engine doing what it does well. If you struggled through Monster Hunter Wilds’ launch performance, do not assume Onimusha inherits the same problems. It is a different shape of game entirely.

The settings order that gets you to a stable 60

Once the crash is behind you, here is the sequence I would run on a mid-range machine trying to lock 60 FPS at 1080p or 1440p:

1. Set Texture Quality to match your VRAM. 6GB cards stay at Medium, 8GB at High, 12GB and up can push it.
2. Turn ray tracing off. No meaningful visual gain, real cost.
3. Enable DLSS 4.5 (NVIDIA) or FSR 3.1 (AMD) at Quality. At 1440p this is close to free image quality and buys you a comfortable margin.
4. Drop Shadow Quality one step from the preset if your 1% low still dips.
5. Leave frame generation off until your base frame rate is already above roughly 50 to 55 FPS. Generating frames on top of a low base adds latency and makes precise parrying feel worse, which is the last thing you want in this game.
6. Cap the frame rate a few frames under your refresh and retest the benchmark. Chase the 1% low, not the average.

The benchmark being out this far ahead of launch is a gift. Run it now, apply the fixes above, and rerun it. If your combat 1% low climbs into the 50s and holds without the shader crash, you are ready for September 4. If it does not, you have a full month to decide whether the answer is a texture step down, a driver clean, more system RAM, or a card with a bigger frame buffer, rather than finding out the hard way on launch night.