Many players are reporting low FPS in Where Winds Meet even with high-end GPUs like the RTX 4090, especially when entering dense cities, crowded hubs, or large villages.
Even with graphics set to Low, the game may drop to 30–40 FPS, which feels shocking for a 4090 owner.
This happens because the game’s engine is CPU-heavy, streaming-heavy, and still poorly optimized in urban regions.
The GPU isn’t the bottleneck — the world-streaming system is. But with the right tweaks, you can stabilize performance and reduce stutter significantly.
Here’s how to improve FPS and fix heavy framerate dips in cities.
Quick Fix
Switch Graphics Mode → Balanced, disable Frame Generation, and cap FPS to 90 — this instantly stabilizes the 4090’s performance and removes the worst city stutters.
Fix 1 – Disable Frame Generation to Fix CPU Bottleneck Stutter
Frame Generation helps only when the GPU is the bottleneck.
In Where Winds Meet, dense cities cause a CPU bottleneck, which makes FG behave poorly.
Turning it off stabilizes performance immediately in crowded zones.
Steps:
- Graphics → Turn off Frame Generation
- Restart game
How it helps: Removes artificial stutter caused by mismatched render timings.
Fix 2 – Switch From Ultra to Balanced Textures for City Streaming
The Low FPS in Where Winds Meet problem comes from aggressive texture streaming.
Balanced mode reduces memory pressure while still looking sharp.
Ultra textures force constant streaming in cities, causing FPS drops.
How it helps: Prevents heavy streaming spikes on 4090 VRAM channels.
Fix 3 – Turn Off SSR, SSAO, and Volumetric Fog
These three settings cause the biggest drops in villages and city centers.
SSR and SSAO hammer the CPU, not the GPU.
Volumetric fog is extremely inefficient in this engine.
How it helps: Removes major CPU-side render tasks that choke framerate.
Fix 4 – Set Shadows to Medium (Massive CPU Saver)
Shadows in Where Winds Meet scale with physically simulated light sources.
Cities contain hundreds of shadow-casting objects.
Lowering shadows to Medium removes over 50% of the CPU load.
How it helps: Gives the largest FPS increase in urban hubs.
Fix 5 – Turn Off Motion Blur and Depth of Field
Both features cause micro-stutters when transitioning between small spaces.
Disabling them reduces frame latency and eliminates the “sluggish” feel.
How it helps: Makes the 4090 run smoother by reducing post-processing load.
Fix 6 – Set the Game to Fullscreen, Not Borderless
Borderless mode introduces extra frametime spikes.
Fullscreen allows exclusive GPU control, improving stability in busy areas.
How it helps: Reduces drops from 40 FPS → 55–70 FPS in worst spots.
Fix 7 – Update NVIDIA Drivers and Disable NVIDIA Overlay
Outdated drivers can cause inconsistent CPU usage.
NVIDIA overlay also adds latency spikes in CPU-heavy titles.
Steps:
- Update drivers
- NVIDIA GeForce Experience → Disable Overlay
How it helps: Reduces frametime instability.
Fix 8 – Increase Shader Cache Size in NVIDIA Control Panel
Where Winds Meet constantly compiles shaders during movement.
A larger shader cache prevents duplication and improves load speed.
How it helps: Reduces stutter during fast traversal and city transitions.
Fix 9 – Enable DLSS Quality Instead of DLSS Performance
DLSS Performance looks worse and can increase stutter on a 4090.
DLSS Quality reduces CPU load while retaining image clarity.
This setting is ideal for hub areas.
How it helps: Smooths FPS while keeping visuals crisp.
Fix 10 – Lower Crowds/NPC Density in Settings
Cities contain the highest number of simulations and NPC updates.
Reducing crowd density cuts CPU strain dramatically.
How it helps: Boosts FPS where the worst drops happen (cities, markets, shrines).
Fix 11 – Disable Ray Tracing Completely (Hidden FPS Killer)
Even if you think Ray Tracing is off, some presets re-enable partial RT features.
RT in Where Winds Meet is extremely unoptimized and tanks FPS even on a 4090.
Fully disabling it removes a huge amount of lighting calculations in cities.
How it helps: Frees the GPU/CPU from unnecessary RT load and boosts FPS in dense regions.
Fix 12 – Reduce Physics Quality (Major CPU Saver in Cities)
Physics objects — cloth, banners, wind effects — overload the CPU in crowded hubs.
Setting Physics to Medium or Low massively increases stability.
This setting matters more in cities than in open fields.
How it helps: Cuts CPU strain from interactive objects that cause FPS drops.
Fix 13 – Turn Off Cloth Simulation (4090 Still CPU-Bound Here)
Cloth simulation updates dozens of capes, banners, and decorations in cities.
This simulation is CPU-driven, not GPU-driven.
Turning it off removes a major bottleneck.
How it helps: Smooths movement near crowds, markets, and guild hubs.
Fix 14 – Reduce Particles to Medium (Helps in Villages With Smoke/Fog)
Villages often use complex smoke and dust particle effects.
Particles on Ultra cause large frametime spikes.
Medium or Low keeps visuals stable without tanking FPS.
How it helps: Reduces stutter in foggy or smoky village environments.
Fix 15 – Disable Screen Space Reflections in NVIDIA Control Panel
Sometimes the in-game SSR setting doesn’t fully turn off.
Disabling it through NVIDIA Control Panel forces complete removal.
This stops city puddles and wet surfaces from causing FPS drops.
How it helps: Eliminates heavier-than-usual reflection calculations.
Fix 16 – Turn Off Ambient Occlusion in NVIDIA Control Panel
Like SSR, the AO override can remain active even when disabled in-game.
Turning AO fully off improves CPU performance around clustered buildings.
It’s one of the biggest hidden FPS drains in hubs.
How it helps: Lightens the shading workload dramatically.
Fix 17 – Cap FPS to Your Monitor’s Refresh Rate
Unlocked FPS causes micro-stutters due to fluctuating frame timings.
Capping to 90, 120, or 144 stabilizes frametimes, especially in cities.
The 4090 benefits more from stability than raw numbers here.
How it helps: Smooths gameplay by preventing chaotic frame spikes.
Fix 18 – Increase Windows Pagefile Size (Prevents Streaming Stall)
Where Winds Meet streams massive world chunks constantly.
A small pagefile makes this process stutter even with strong hardware.
Larger pagefile (20–30GB) improves loading and reduces drops.
How it helps: Prevents memory bottlenecks during dense city traversal.
Fix 19 – Disable Intel/AMD E-core Scheduling Issues (If Using Hybrid CPU)
Games that aren’t optimized for hybrid CPUs sometimes schedule threads incorrectly.
This causes huge FPS drops in cities even with a 4090.
Using Process Lasso or Windows Game Mode can correct thread allocation.
How it helps: Ensures the game runs on performance cores, restoring FPS.
Fix 20 – Avoid Using Ultra Draw Distance (One of the Worst Offenders)
Draw Distance on Ultra loads too many props, shadows, and geometry.
Even a 4090 paired with a strong CPU struggles in large cities.
Set Draw Distance to High—not Ultra—for huge FPS gains.
How it helps: Cuts excessive world loading while keeping visuals nearly identical.
Why is Where Winds Meet running at 30–40 FPS on my RTX 4090?
Where Winds Meet can run at shockingly low FPS even on an RTX 4090 because the game is not GPU-limited — it is heavily CPU-bound in dense areas. The engine uses extremely high draw-call counts for crowds, shadows, foliage simulation, and physics, which saturates a single thread before the GPU even reaches full load.
This means your 4090 sits at 40–60% usage while your CPU spikes to 90–100% on one core.
Cities, markets, villages, and boss arenas are the worst offenders because of dynamic AI density and streaming grids.
Even dropping to Low settings doesn’t help because your GPU isn’t the problem — the engine’s simulation thread is. Until the developers release deeper CPU optimizations, a high-end GPU cannot brute-force FPS past the bottleneck.
Why are cities so laggy even on low settings?
Cities are laggy because Where Winds Meet’s world simulation is extremely heavy:
- Dense NPC pathfinding
- Real-time shadow projections
- Dynamic geometry loading
- Cloth physics on crowds
- Ambient audio layers
- High traffic scripting
All of these run on the CPU, not the GPU.
Lower graphics settings only reduce GPU load — they do nothing to reduce the city-level simulation.
This is why players see:
- 35–50 FPS in towns
- 90–140 FPS in wilderness
- 160–200+ FPS indoors
The engine simply wasn’t optimized to scale NPC-heavy regions for PC hardware yet.
Is Where Winds Meet badly optimized on PC?
Yes — the current PC version is poorly optimized, especially in populated regions. Several issues contribute to this:
- Heavy single-thread dependence
- No proper multithreading for NPC AI
- Inefficient culling in cities
- High VRAM requests from texture streaming
- Lack of shader pre-compilation
- DLSS/FSR not fixing CPU bottlenecks
Even high-end hardware (4090 + 13900K) can’t maintain 100 FPS in major towns.
The open world feels smooth because the engine has fewer simulation tasks there, but cities reveal the optimization gaps immediately.
Until a major patch addresses CPU load, even top-tier rigs will experience drops.
Why does my FPS drop in villages but not in open world?
Villages cause FPS drops because they contain static + dynamic assets packed together, unlike the open world where objects are more spaced out. The engine must process:
- Interior lighting from multiple homes
- NPC schedules and patrols
- Market stalls with physics items
- Dense structural shadows
- Ambient crowd audio
- Dynamic LOD swaps at close range
Even small villages act like CPU stress zones.
Meanwhile, open-world areas have fewer pathfinding tasks and use simpler culling, so the GPU can finally stretch its legs and push higher FPS.
This is why your 4090 gives 140 FPS in fields but 40–55 FPS in settlements.
Does WWMeet have CPU bottleneck issues?
Yes — Where Winds Meet suffers from severe CPU bottlenecking, especially on the main simulation thread. Symptoms include:
- High CPU core 0 usage
- Low GPU usage even at 4K
- Big FPS drops in cities or camps
- Delayed texture streaming
- Animation stutter despite high VRAM headroom
The underlying issue is that Where Winds Meet uses a heavy NPC simulation system similar to an MMO, but without full multithread support. This causes one CPU thread to cap out long before the GPU can be utilized.
Players with 4090s, 7900 XTXs, and even 14900Ks report the same bottleneck.
Only future patches can meaningfully fix these frame pacing issues.
Final Thought
The Low FPS in Where Winds Meet issue on an RTX 4090 is caused by CPU-heavy world streaming, dense city simulations, and unoptimized shadow/volumetric systems — not GPU weakness. By disabling Frame Generation, lowering shadows, switching to Balanced textures, using DLSS Quality, and reducing NPC density, you can stabilize performance and eliminate harsh drops in dense regions. A future optimization patch will likely improve this, but these fixes give you a clean, smooth experience today.