Where Winds Meet PC Settings & Performance

PC system requirements and storage packages (what you actually need)

Before you touch any settings, make sure your PC matches the version you installed—because Where Winds Meet has different install package sizes and requirements depending on where you download it.

Steam / Standard build requirements (common baseline)

Steam lists these requirements for the PC version on its store page:

• Minimum: Windows 10/11 (64-bit), i7-7700K / Ryzen 5 1600, 16GB RAM, GTX 1060 (6GB) / RX 480 (8GB), DX12, 100GB storage, SSD recommended.
• Recommended: i7-10700 / Ryzen 7 3700X, 32GB RAM, RTX 2070 SUPER / RX 6700 XT / Intel Arc A750, DX12, 100GB storage, SSD recommended.

Official PC launcher requirements (Quick vs Standard packages)

The official PC launcher installation guide lists:

• Minimum (PC): i7-4770K / Ryzen 5 2400G, GTX 750 Ti / RX 550 / Arc A380, 8GB RAM, 60GB storage (HDD allowed; SSD recommended).
• Recommended (PC): i7-10700 / Ryzen 7 3700X, RTX 2070 SUPER / RX 6700 XT / Arc A750, 32GB RAM, 100GB SSD.
• High (PC): i7-12700K / Ryzen 9 5950X, RTX 3080 / RX 6800 XT, 32GB RAM, 100GB SSD.

And the same official guide explains the package sizes you can choose:

• Standard Package: reserve 100GB+
• Quick Package: reserve 60GB+
• Ultimate Package: not available at launch (details later)

What this means in real life (simple rule):

• If you installed the Standard build (common on Steam), plan around 100GB storage and target 16GB+ RAM, ideally 32GB.
• If your PC is older or storage-limited, the official launcher’s Quick package may run on much lower hardware, but you should expect more compromises and be more careful with settings.

The 5-minute first launch checklist (do this before tweaking graphics)

These are the “boring” steps that prevent 80% of the problems people blame on graphics settings.

1) Install on an SSD (not an HDD)

Both Steam and the official guide explicitly recommend installing on an SSD for a better experience.

2) Leave extra free space on the drive

Open-world streaming games hate nearly-full drives. Keep a healthy buffer so the game can write cache files smoothly.

3) Update GPU drivers

New drivers often include game-specific fixes for stutter or crashes (especially around DX12).

4) Turn off extra overlays (temporarily)

Overlays can cause unexpected frametime spikes. If you’re troubleshooting performance, disable them first, then re-enable later.

5) Don’t “stack” performance apps

Avoid running multiple FPS boosters, “optimizers,” and overlays at the same time. One is already too many when troubleshooting.

DX11 vs DX12: the most important performance choice

Where Winds Meet supports multiple rendering APIs, and this is the fork in the road that decides what features you can use.

What’s confirmed by PC performance testing

A DSOGaming performance write-up reports:

• The game defaults to DX11
• To use Intel XeSS, AMD FSR, or NVIDIA DLSS, you must run the game in DX12

They specifically describe choosing the DX12 version from Steam at launch (and note there is no built-in benchmark tool).

What players commonly report

Steam community replies also echo the same idea: “start the game with DX12” to access DLSS (and some mention frame generation).

When to choose DX11

Pick DX11 if:

• Your PC is older and DX12 causes crashes
• You want maximum stability and don’t care about DLSS/FSR/XeSS
• You’re troubleshooting and want a clean baseline

When to choose DX12

Pick DX12 if:

• You want DLSS / FSR / XeSS upscaling
• You’re trying to raise FPS without lowering resolution
• You’re aiming for high refresh gameplay (60/120/144+)

Practical tip:

If DX12 runs smoothly for you, it’s usually the best long-term option because upscalers are the single biggest FPS tool in a modern open-world game.

Upscaling explained: DLSS vs FSR vs XeSS (what to use and why)

Upscaling means the game renders internally at a lower resolution, then reconstructs the image to look close to native. The upside: more FPS with less image loss than dropping resolution normally.

Confirmed support

DSOGaming confirms support for XeSS, FSR, and DLSS (with DX12 required to use them).

If you have an NVIDIA RTX GPU

Use DLSS first (Quality/Balanced are the usual sweet spots). DLSS is NVIDIA’s AI upscaling stack, designed specifically for RTX cards.

If you have an AMD GPU

Use FSR (Quality or Balanced to start). It’s widely supported and can be a huge performance lift in dense areas.

If you have an Intel Arc GPU

Use XeSS, which is designed to work especially well on Intel hardware but can also work on others depending on implementation.

The “best looking” rule

• If you’re at 1080p and the image looks too soft, try a higher quality mode first (Quality > Balanced > Performance) before changing other graphics settings.
• If you’re at 1440p/4K and want big FPS gains, Balanced or Performance can be worth it.

Frame generation: huge FPS, but use it the smart way

Frame generation creates extra “in-between” frames to raise displayed FPS. It can feel amazing—especially on high refresh monitors—but it’s not a free win. The key is using it under the right conditions.

What’s confirmed in performance analysis

DSOGaming reports that enabling frame generation increased performance significantly in their test scenario, and they also mention that Where Winds Meet supports DLSS/FSR/XeSS under DX12.

The DLSS 4 / Multi Frame Generation confusion (important in 2025)

NVIDIA published a post stating Where Winds Meet is among titles featuring DLSS 4 with Multi Frame Generation.

However, DSOGaming also noted that while NVIDIA stated DLSS 4 Multi-Frame Gen would be supported, they didn’t see an in-game setting to enable it at the time and couldn’t force certain MFG modes via the NVIDIA App due to profile limitations.

What you should do (simple):

• If you see Frame Generation in-game: try it.
• If you don’t see it: update drivers, confirm you’re running DX12, then check again.
• If you have a newer RTX card and expected “Multi Frame Gen” specifically, assume availability can vary by patch and profile support.

Latency rule that makes frame generation feel good:

Frame generation feels best when your base FPS is already decent (example: 60+). If your base FPS is too low, frame generation can look smooth but feel less responsive.

Display settings: the clean setup for smooth combat

Your display settings decide both performance and “feel.” In a wuxia action RPG, feel matters.

Display Mode

• Use Fullscreen when possible for the most stable performance and lowest input delay (especially on older setups).
• If your game supports borderless properly and you alt-tab a lot, borderless can be fine—but test it.

Refresh Rate

• Set the game to your monitor’s maximum refresh rate (60/120/144/165/240).
• If you forget this, the game can silently run at 60 even on a 144Hz screen.

V-Sync

• If you have VRR (G-Sync/FreeSync): turn V-Sync off in-game, use VRR, and set a small FPS cap slightly below refresh rate (example: 141 cap for 144Hz).
• If you don’t have VRR: V-Sync can prevent tearing but may increase input delay. In parry-focused combat, many players prefer V-Sync off and tolerate minor tearing.

Frame cap (highly recommended)

A stable cap often feels better than wild FPS swings. If your PC can hit 120 but dips to 70 in cities, consider capping at 90 or 100 for steadier frametimes.

HDR (if available and if your monitor supports it well)

HDR can look amazing in scenic areas, but it can also expose banding or “washed” images if your Windows HDR setup is messy. If HDR looks wrong, disable it first before blaming graphics settings.

Graphics settings: what actually impacts FPS the most

Not all graphics sliders are equal. These are the usual “big hitters” in open-world games—and the safest things to lower first when you need performance.

Shadows

High shadows are expensive because they update dynamically and affect huge areas. Dropping shadows one step often gives noticeable FPS back with minimal visual loss.

Volumetrics (fog, god rays, heavy atmosphere)

These can be brutal in forests, storms, or dense city lighting. If your FPS collapses in certain weather/time-of-day scenarios, volumetrics are a top suspect.

Reflections

If reflections are screen-space or ray-traced (depending on implementation), they can be one of the most expensive features. Lower reflections if you notice city FPS drops near water, wet stone, or shiny interiors.

Foliage / vegetation density

This matters a lot in big open zones. If your GPU is fine but your CPU is struggling, foliage density can also hit CPU due to draw calls and culling.

View distance / LOD

This affects how much the game keeps “detailed” in the distance. Lowering it can help both CPU and GPU and reduce streaming pressure.

Textures (VRAM-dependent)

Textures don’t always change FPS directly—but if you exceed VRAM, the game can stutter horribly.

• If you have 6GB VRAM, be careful with ultra textures. Steam’s minimum GPU spec includes a GTX 1060 6GB, which is workable but not “infinite.”

Best settings presets (copy-paste your starting point)

Use these as your baseline, then tweak based on how your game behaves in the areas that cause problems (cities, crowded fights, dense forests).

Preset A: Competitive combat (most stable parry timing)

Goal: best responsiveness and smooth frametimes.

• API: DX12 (if stable)
• Upscaling: DLSS/FSR/XeSS Quality
• Frame Generation: Off (turn on only if base FPS is already high and input still feels good)
• Shadows: Medium
• Volumetrics: Low/Medium
• Reflections: Medium
• Foliage density: Medium
• Motion blur: Off
• Depth of field: Off or Low
• Frame cap: cap to a stable number your PC can hold (example: 90)

Preset B: Balanced (best “looks good, plays good” setup)

Goal: strong visuals without stutter spikes.

• API: DX12
• Upscaling: Balanced
• Frame Generation: On (if it feels responsive)
• Shadows: Medium/High
• Volumetrics: Medium
• Reflections: Medium/High
• Foliage density: High (drop to Medium if cities tank)
• Frame cap: optional (cap if you get spikes)

Preset C: Cinematic (for screenshots and slow exploration)

Goal: visuals first, accept lower FPS.

• API: DX12 (or DX11 if DX12 gets unstable)
• Upscaling: Quality (or native if you have the GPU headroom)
• Shadows: High
• Volumetrics: High
• Reflections: High
• Foliage density: High
• Frame cap: match your monitor refresh or cap to 60 for smooth capture

Hardware-based tuning: what to change for your exact PC

Instead of guessing, match your tweaks to the bottleneck you actually have.

If your GPU is the bottleneck (high GPU usage, low FPS)

Do this order:

1. Enable an upscaler (DLSS/FSR/XeSS) and choose Quality/Balanced
2. Lower shadows
3. Lower volumetrics
4. Lower reflections
5. Lower resolution as a last resort (upscaling usually beats raw resolution drops)

If your CPU is the bottleneck (low GPU usage, stutter in cities)

Do this order:

1. Lower foliage density
2. Lower view distance / LOD
3. Reduce crowd/NPC density if there’s a slider for it
4. Cap FPS (capping reduces CPU spikes)
5. Close background apps (browsers can eat CPU/RAM)

If VRAM is the bottleneck (stutter, texture pop, hitching)

Do this order:

1. Lower textures one step
2. Reduce resolution scale / choose Balanced/Performance upscaling
3. Avoid “ultra” texture packs if your GPU is near the minimum tier listed on Steam

If RAM is the bottleneck (random freezes, heavy hitching)

Steam recommends 32GB RAM for the recommended tier.

If you only have 16GB, you can still play—but:

• keep background apps closed
• consider the Quick package if you’re extremely constrained (official launcher)
• cap FPS and avoid ultra settings that push streaming hard

Stutter and hitching fixes (the stuff that ruins immersion)

Even with high average FPS, stutter can make the game feel bad. DSOGaming notes there can be some traversal stutters depending on scenario.

Use this checklist in order:

Fix 1: Install on SSD and keep it there

This is the #1 fix because open-world games stream constantly. Steam and the official guide both recommend SSD installation for better experience.

Fix 2: Use DX12 + upscaling (if stable)

If you’re on DX11 and struggling, moving to DX12 can unlock DLSS/FSR/XeSS, which often stabilizes performance without sacrificing sharpness.

Fix 3: Cap FPS

Capping reduces “spikes” and helps stabilize frame pacing—especially in city zones.

Fix 4: Reduce the streaming-heavy sliders

Lower:

• view distance / LOD
• foliage density
• shadows (shadow maps can update frequently)

Fix 5: Rebuild shader cache (only if stutter is extreme)

Shader compilation hitches happen in a lot of DX12 games, especially after updates. If your stutter is severe after patching, clearing relevant caches can help—but do it carefully and expect the first session after clearing to recompile and run rougher temporarily.

Crashes, freezes, and “weird” bugs: stability checklist

If the game won’t install or launcher errors happen

The official install guide warns that the launcher installation path must be in the system language or English (and notes using unsupported characters can cause errors).

If the game crashes on startup

• Try DX11 first to confirm stability (then move back to DX12 later)
• Update drivers
• Verify files (Steam/Epic) or repair via launcher if available
• Disable overlays

If the game hard-stutters when entering cities

• Make sure you’re on SSD
• Reduce foliage/view distance
• Cap FPS
• Use DLSS/FSR/XeSS Balanced

Controller and input settings (PC quality-of-life)

If you play controller on PC, the official beta announcement stated controller support (Xbox and PlayStation controllers) was supported in testing.

For low input delay (mouse or controller):

• Keep FPS stable (cap if needed)
• Avoid heavy post-processing that adds blur
• Prefer fullscreen when troubleshooting

Online requirement (important for troubleshooting “lag vs FPS”)

The official beta FAQ states the game requires a consistent internet connection to play.

So if you feel “lag,” separate the problem:

• FPS drops / stutter = PC performance issue
• rubberbanding / delayed interactions = network issue
• Both can happen, but they are fixed differently.

BoostRoom: smooth performance, better combat, less frustration

If you want Where Winds Meet to feel clean and responsive—especially for precision combat—BoostRoom helps you get there faster.

BoostRoom can help with:

• PC settings tuning for your exact hardware (stable FPS for better parry timing)
• Build guidance so you don’t over-invest in effects-heavy setups that tank performance
• Co-op prep and combat coaching so fights feel smoother, not chaotic
• Practical “what to lower first” advice so you stop wasting time changing random settings

The goal is simple: more smooth sessions, less troubleshooting, and a setup that stays stable even when you reach dense city areas.

FAQ

Does Where Winds Meet run better on DX11 or DX12

DX11 is the default according to PC performance testing, but DX12 is required to use DLSS/FSR/XeSS upscalers—so DX12 is usually the best option if it’s stable on your PC.

Why don’t I see DLSS / FSR / XeSS in my settings

A PC performance report says those upscalers require DX12. If you’re on DX11, switch to DX12 and check again.

How much storage do I need

Steam lists 100GB available space for the standard PC version.

The official launcher also mentions a Quick Package that needs 60GB+ and a Standard Package that needs 100GB+.

Is an SSD really required

It’s not always strictly required, but it’s strongly recommended by both Steam and the official launcher guide for a better experience, and it’s one of the biggest fixes for hitching in large open worlds.

Is there a built-in benchmark

A PC performance report notes the game does not have a built-in benchmark tool.

Does the game support DLSS 4 / Multi Frame Generation

NVIDIA has published a post listing Where Winds Meet among titles featuring DLSS 4 with Multi Frame Generation.

But a PC performance report also notes that availability of specific MFG toggles/settings can vary and was not clearly exposed in-game at the time they tested