Where Winds Meet: PC Performance & FPS Guide

Where Winds Meet · Performance

In Where Winds Meet your frame rate is part of your reaction time. Parries and perfect dodges land in a narrow window, and every dropped frame is a moment your screen isn't telling you the truth. The enemy's swing shows up late, your input lands late, and you eat a hit you should have read. Smooth FPS won't make you good, but a choppy frame rate will absolutely make you worse, and most of that is fixable in twenty minutes. Here's how I'd sort it out.

Measure first, then guess less

Don't touch a slider until you can see your frame rate. Turn on an overlay. The Steam one works, so does your GPU vendor's (NVIDIA, AMD, or Intel), and MSI Afterburner if you want more. The good ones show GPU usage, CPU usage, and frame times next to the FPS number, and that's the part you actually care about.

The one question worth answering is whether you're GPU-bound or CPU-bound. GPU usage near 100% with low FPS means the graphics card is your wall, and lowering visual settings will help. GPU usage well under 100% with FPS still stuck low means the CPU is your wall, usually one overloaded core, and dropping shadows does basically nothing. Those need different fixes, down at the bottom.

Test where it hurts, too. An empty field renders almost nothing and makes any settings look great. A packed town or a real fight is where frames fall apart and where you need them. Tune for the worst case, not the screenshot.

The settings worth cutting first

Graphics options aren't equal. A few of them burn huge performance while changing almost nothing you'll notice mid-fight, and those go first. Names differ between games, but the categories don't:

Shadows. Shadow quality and resolution are usually the single most expensive thing in a modern game. High to medium often buys a fat chunk of FPS and looks near identical once you're moving.
Volumetrics, global illumination, particles and effects. Fog, god rays, bounced light, dense effects. All heavy. Pulling these down is some of the cleanest free performance you'll find.
Anti-aliasing. Smooths jagged edges, costs frames. Temporal modes are the cheap option, and plenty of upscalers fold AA in at no extra cost.
View distance and LOD. How far out the game draws full detail. Pull it back for open areas, and pull it back hard if you're CPU-bound, since draw calls scale with whatever's on screen.
Foliage and clutter. Grass, leaves, little props. Shockingly expensive in dense scenes for something you never look at.
Ambient occlusion. Soft contact shadows. The fancy modes get pricey for a subtle effect, so dial them down.
Motion blur. Off. Always off. It smears a fast action game, kills your read on enemy attacks, and turning it off is free FPS on top.

The big lever, if the game gives it to you, is resolution scaling and upscaling. Render at a lower internal resolution and let an upscaler rebuild the image: DLSS on NVIDIA, FSR on AMD (and supported almost everywhere), or XeSS on Intel. You get a large FPS jump for a small hit to sharpness, a better trade than gutting six individual settings. If you only touch one thing, touch this. Dropping your output resolution outright works too, but upscaling looks better at the same frame rate.

Stutter and low FPS are not the same bug

People lump these together and fix the wrong one. Low FPS is the whole game feeling sluggish but steady. Stutter is a sharp hitch inside an otherwise fine frame rate, where the screen freezes for a split second and then snaps back. Different causes, different fixes, and lowering settings often won't touch stutter at all. Where it usually comes from:

Shader compilation. Lots of games build shaders the first time you hit a new effect, so your first run through an area hitches and then smooths out as the cache fills. Don't judge a fresh install. Play an area twice before you decide anything.
Streaming and traversal. Sprint across the world and the game pulls fresh geometry and textures off your drive. A slow drive makes this ugly, which is the whole argument for an SSD.
Background apps. A browser, Discord, a launcher quietly updating, some overlay. Any of them can grab the CPU at the wrong moment and hitch you. Close what you don't need.
Thermal throttling. An overheating CPU or GPU slows itself down to cool off, and that shows up as stutter or sudden drops a few minutes in.
VRAM overflow. Push textures and resolution past your card's video memory and the system spills into slower system RAM, which stutters badly. Drop texture quality or resolution until it fits.

Drivers and a frame cap

Keep your GPU drivers current. Vendors ship game-ready updates that fix performance and crashes, and a stale driver is one of those invisible reasons your frames are bad for no obvious reason. Grab them from NVIDIA's app, AMD's Adrenalin, or Intel's driver tool, not whatever Windows decides to install on its own.

You don't need to live in the vendor control panel. The one change almost everyone benefits from is a frame rate cap. Set it a few frames below your monitor's refresh rate and your frame times steady out, those ugly 1%-low dips shrink, and the card runs cooler and quieter because it stops rendering frames you'll never see. Cooler card means less throttling, which means a cap can actually raise your lows. Set it in the driver, in the game, or with RTSS, whichever you trust.

Tip: Watch your 1% lows, not your average. A steady 80 feels miles better than an average of 110 that craters to 45 every fight. When you're comparing settings, keep an eye on the frame-time graph and the lows, because that's what your hands actually feel.

Windows and system tweaks

A handful of system changes free up headroom before the game even launches:

Turn on Game Mode in Windows Settings. It nudges the OS to favor your game over background junk.
Use a high-performance power plan. Mostly a laptop thing, where balanced and battery-saver modes throttle your hardware on purpose.
Kill background apps and overlays. Forty browser tabs, cloud sync, three overlays. They all skim CPU and RAM. Quit them before you play.
Put the game on an SSD, never a spinning hard drive. Faster loads and far less streaming stutter as you move around.
Leave memory headroom. Starve the game for RAM or VRAM and it stutters or swaps to disk. Modern titles want 16 GB of system RAM or more, and a card with enough VRAM to hold your settings.
Run your monitor at its real refresh rate. Check Display settings, because Windows occasionally parks a high-refresh monitor at 60. Then sort out V-Sync versus G-Sync/FreeSync. V-Sync kills tearing but can add input lag. A variable-refresh display with a cap just under the refresh rate gives you tear-free, low-lag motion, which is exactly what a timing game wants.

Heat quietly eats your frames

When a CPU or GPU gets too hot it throttles, dropping its own clock speed to survive, and your performance falls off a cliff a few minutes in even though you changed nothing. Classic tell: great for the first five minutes, then it sags. When that happens, suspect heat before anything else.

On a desktop, clear the case airflow and blow the dust out of your fans and heatsinks. A gunked-up cooler is a really common cause of slowdowns that creep in over time. On a laptop the advice is blunter. Plug it in, because most laptops throttle hard on battery. Play on a hard flat surface or a cooling pad so you're not smothering the intake vents, and keep those vents clean. Laptops run hot by design, so this is often the difference between playable and not.

When it's the CPU or RAM instead

If your baseline test showed low FPS with GPU usage sitting well under 100%, lowering graphics settings is mostly wasted effort. You're CPU- or memory-bound, and the playbook changes:

Cut the CPU-heavy settings specifically. View distance, crowd and NPC density, physics detail. These lean on the CPU and pay off in packed towns and big fights, which is exactly where CPU-bound stutter lives.
Free up cores. Close background apps so the game gets its CPU time, and check that nothing's quietly pinning a core in the background.
Sort out your RAM. Too little and the system swaps to disk constantly and hitches. While you're in there, enable your memory's XMP or EXPO profile in the BIOS so the RAM runs at its rated speed, which genuinely helps CPU-bound frames.
Don't wait on upscaling to save you. DLSS and friends cut GPU load, so they barely budge anything when the CPU is your bottleneck.

Quick FPS Checklist

Choppy or stuttering? Run down this list in order. Each step rules out a cause before the next one:

Measure it. Turn on an FPS and frame-time overlay, then test in a busy town or fight, not an empty field.
Find the bottleneck. Is GPU usage near 100% (GPU-bound) or well under (CPU-bound)? Fix the right side.
Update your GPU driver from the vendor's app before you change anything else.
Turn on upscaling. DLSS, FSR, or XeSS if it's there. Biggest single FPS lever you have.
Cut the expensive settings. Shadows, volumetrics and effects, view distance. Motion blur off.
Cap your frame rate a few frames under your refresh rate to steady frame times and lower heat.
Close background apps, turn on Game Mode and a high-performance power plan.
Check thermals. If FPS sags after a few minutes, clean your fans, fix airflow, and on a laptop plug in and lift the vents.
Confirm the basics. SSD, monitor at full refresh, enough RAM and VRAM for your settings.

Get these dialed in and the game runs the way it's meant to. Frames hold steady through the busiest fight and your timing comes down to your reflexes instead of your hardware. One thing to keep separate, though: performance and connection are different problems. A rock-solid frame rate won't save you if your inputs are vanishing to lag, and the lowest ping in the world can't smooth out a stuttering frame rate. If fights still feel off after all this, it might be your network. Check the connection & ping guide and run the ping checker to rule it out. New here? Start with the beginner's guide, or browse everything on all guides.