Dawnwalker Best PC Settings: Fix Svartrau FPS Drops & Stuttering

Launch-week performance warning

This is a spoiler-free retail-build guide. Multiple launch-day players report micro-stutter or unexpectedly low performance, but results vary even across similar GPUs; others report stable play. There is no verified universal stutter fix yet, so the steps below prioritize reversible changes and repeatable testing.

Do not apply registry edits, page-file recipes or copied engine configuration files as a first response. Record the game build, GPU driver, resolution, preset, upscaler and exact problem area before changing one setting at a time.

Hotfix 1.0.5: shader-pipeline improvement, not a blanket cure

Rebel Wolves released Hotfix 1.0.5 on Steam and GOG on September 10, 2026. Its only listed change improves the shader-compilation pipeline and can fix stuttering for some users. Install it, let compilation finish, then repeat the same route twice before changing graphics settings.

The patch does not name camera-motion, Svartrau City or Borderless stutter. Independent RTX 5080 and RTX 5090 testing still reproduced camera stutter after 1.0.5. That is useful negative evidence for the universal-fix question, not proof that no PC can benefit.

Hotfix 1.0.4: two specific PC performance fixes

Rebel Wolves released Hotfix 1.0.4 on September 9, 2026. On Steam, outdated GameInput controllers should no longer cause FPS drops. On PC, FSR Frame Generation should now work correctly with V-sync.

These are specific fixes, not a blanket performance patch. If the slowdown happens only when a controller is connected on Steam, compare the same stationary scene connected and disconnected after updating. If it happens throughout Svartrau regardless of input method, continue with the area-specific tests below.

Best starting point by GPU tier

The official targets assume Balanced upscaling. Use the closest row as a baseline rather than starting at Ultra and lowering everything blindly.

Change these settings first

Choose the upscaler supported by your GPU and begin at Balanced. PC Gamer's repeatable Briar Sloughs run found that changing DLSS from Balanced to Performance gained only 6 FPS while increasing foliage noise. That makes individual quality settings the better first compromise at 1440p on the tested RTX 4060.

Two independent test passes point to Shadows, Lighting and scene-detail controls as the useful levers. PC Gamer reached 62 FPS average and a 46 FPS 1% low by setting Shadows to Low and Lighting, Foliage and Detail to Medium. GameGPU's separate RTX 4070 Ti scene also measured gains from lowering Lighting, Reflections and Shadows. These are hardware- and scene-specific results, not guaranteed gains.

What the repeatable 1440p test measured

PC Gamer tested a 90-second loop through Briar Sloughs on an RTX 4060 and Ryzen 7 7700X at 2560×1440. The custom settings improved both average FPS and the 1% low, while simply switching DLSS to Performance recovered less performance and reduced image clarity.

Use the figures as a comparison of settings on one machine, not as a promise for every forest, settlement or combat encounter. The same tester reported a heavier nighttime multi-character fight averaging 53 FPS even with the custom values.

Svartrau City FPS drops: diagnose the area, not just the preset

Svartrau is emerging as a repeatable worst-case area. Independent PC reports describe large drops on entering the city, including systems that run the open world smoothly. One fresh RX 9070 XT report found almost no difference between High and Low at 1440p FSR Balanced; an earlier multi-user thread includes city results falling from roughly 80–90 FPS outside to about 45 FPS inside. A Steam report also reproduces severe city stutter on an RTX 5080.

Those reports confirm an area-specific performance signal, but they do not prove one CPU, GPU or engine cause. Treat a small High-to-Low gain as a diagnostic result: avoid destroying image quality for no measurable benefit, establish a clean baseline, and preserve exact before/after numbers for a patch report.

Safe stuttering checklist

Run the checklist in order and repeat the same short route after each change. A higher average FPS does not prove smoother frame pacing.

• Install the latest stable driver for your GPU, then reboot
• Confirm the game is on an SSD and verify its files in Steam
• Let first-launch shader compilation finish; retest after driver or game updates
• Disable Frame Generation for one comparison run
• Close recording, monitoring and overlay tools one at a time
• Remove GPU or CPU overclocks while diagnosing
• Try a stable FPS cap below your repeatable minimum rather than chasing a fluctuating peak
• If stutter survives every setting tier, preserve your save and wait for an official patch instead of stacking unverified tweaks

Official fix for Windowed or Borderless stutter

Rebel Wolves lists stuttering in Windowed and Borderless modes as a known launch issue and recommends Full Screen as the current workaround. Change only Display Mode, apply the setting and repeat the same 60-second route before adjusting quality options.

This workaround is symptom-specific. It does not establish that every hitch is caused by the window mode, and it may not help shader-compilation or traversal stutter. If Full Screen makes no difference, restore your preferred mode and continue the checklist instead of stacking unrelated changes.

Why some cutscenes are capped at 30 FPS

Retail PC testing and repeated launch-day reports show two different presentation paths: cinematic sequences can be capped at 30 FPS, while interactive dialogue and gameplay return to the normal game frame rate. If the counter drops only when a cinematic starts and immediately recovers afterward, lowering every graphics setting will not remove that specific cap.

Use a repeatable gameplay scene to tune performance. A 30 FPS cinematic does not mean the entire game is running at 30 FPS, and an uncapped dialogue scene does not prove traversal stutter is fixed. Rebel Wolves has not yet published an official cutscene-unlock option or workaround.

Cutscene mods and Engine.ini edits: provisional only

Community mods now advertise uncapped rendered cutscenes, animation changes and optional vignette or film-grain removal. They are third-party modifications, not official fixes, and can require an additional injection framework. DawnwalkerHelp does not recommend installing them as the first diagnostic step.

If you choose to experiment, back up saves and configuration files, use the mod author's documented removal path and retest after every game update. Do not mark broad Engine.ini changes read-only while troubleshooting: that can preserve obsolete values and make later patches harder to evaluate. Restore a clean configuration before filing a reproducible bug report.

• Official cutscene unlock: not announced
• Third-party unlock: available, but provisional
• Save and config backup: required before testing
• After a patch: remove the modification and establish a clean baseline

Frame Generation, V-sync and VRR

Frame Generation is available alongside DLSS, FSR and XeSS. Hotfix 1.0.4 specifically fixes FSR Frame Generation working incorrectly with V-sync on PC. Establish a clean post-patch baseline before reusing an old workaround or configuration file.

In the same RTX 4060 route, 2× Frame Generation increased the reported average from 50 to 73 FPS and added about 4 ms of measured PC latency. The tester also saw more character fringing and camera-pan artifacts. That makes it a reasonable smoothness option below 60 FPS, but clarity is usually better with it Off once native or upscaled output already exceeds 60.

The 1.0.4 fix does not prove that Frame Generation removes CPU-side or traversal hitching. Change only one of V-sync, the FPS cap or VRR per test, and compare Off versus On on the same route.

How to capture a useful benchmark

Use the same 60-second route, ideally one with traversal and camera movement. Record average FPS, 1% low if available, and visible hitches. Include CPU, GPU, RAM, driver version, resolution, preset, upscaler mode and Frame Generation state when reporting an issue.

A reproducible report is more useful than 'it stutters': it separates shader compilation, VRAM pressure, GPU load and area-specific traversal hitching, and gives Rebel Wolves enough detail to compare systems.

Confirmed versus provisional

Confirmed: Hotfix 1.0.5 improves the shader-compilation pipeline on Steam and GOG and may fix stutter for some users. Hotfix 1.0.4 fixed the outdated GameInput-controller FPS-drop cause on Steam and FSR Frame Generation with V-sync on PC. The retail options include DLSS, FSR, XeSS, Frame Generation, a frame-rate cap, V-sync and granular quality controls.

Provisional: the exact cause of remaining camera stutter and Svartrau slowdowns, the best cap/VRR combination, and whether any unlisted controller or storefront case shares a fixed cause. Player and independent hardware tests establish real symptoms, not one universal diagnosis.