Start with the current game build, native output resolution, and the ten values below. Select DLSS, FSR, or XeSS for your GPU, measure native rendering or Quality first, then try Balanced only if GPU load is the limit. Lower reflections, effects, shadows, foliage, and detail before sacrificing lighting or post-processing. Keep Frame Generation off while establishing base performance: it can improve presentation, but it cannot repair a slow rendered frame rate or engine-side hitch.
- Baseline: Medium for the main scalable effects; High for post-processing, light, shading, and volumetrics.
- Upscaling: Native or Quality first; Balanced only after a repeatable test shows a GPU limit.
- Diagnosis: Compare one change on one route instead of chasing a universal FPS number.
Before changing the game, reduce avoidable Windows background load so another process does not distort the comparison.
Best PC settings to start with
These values are a conservative starting line rather than a universal preset. Hold resolution, upscaling, route, weather, and camera movement steady while you test.
Swipe sideways to see every column.
| Exact menu label | Starting value | Why and when to adjust |
|---|---|---|
Reflections Quality | Medium | Cost rises above Medium; raise only after the target is stable. |
Effects Quality | Medium | A practical lever in effects-heavy and foliage-rich scenes. |
Shadow Quality | Medium | If still GPU-limited, test Low and watch draw distance and pop-in. |
Post-Processing Quality | High | Preserves effects quality and avoids an Ultra depth-of-field artifact observed in launch-build testing. |
Detail Quality | Medium | Reduces fine environmental density for a modest, repeatable saving. |
Foliage Quality | Medium | Useful in dense outdoor scenes; judge thinning while moving. |
Texture Quality | Medium | A safe 8 GB-class start; test Low if memory pressure persists. |
Light Quality | High | Retains stronger indirect lighting; Medium showed no compelling extra saving. |
Shading Quality | High | Keep High and tune after the better-established levers. |
Volumetric Quality | High | Tune late, one step at a time. |
Recheck the launch-build post-processing observation after updates. A patch can change both cost and image behavior, so preserve the method even when an individual result changes.
Change these settings first
- Reflections
- Effects
- Shadows
- Foliage and detail
- Textures if memory-limited
- Light and post-processing last
Begin with reflections. Controlled launch-build testing found a large cost above Medium. Effects comes next because combat and vegetation can expose its cost more clearly than quiet interiors. Move shadows down only after checking Medium. Low may help a GPU-bound run, but inspect moving scenes for shorter reach and pop-in.
Next, compare foliage and detail along the same forest or town path. Judge the visual thinning in motion, not from a still menu. Textures chiefly need to fit available video memory and streaming load. Medium is the conservative 8 GB-class start; Low is a troubleshooting step when memory pressure or repeatable hitches persist. It is not a guaranteed average-FPS switch.
Leave light, shading, volumetrics, and post-processing until later. High retains the lighting balance, while stronger measured savings sit earlier in the order. The Ultra post-processing artifact was launch-build behavior, not a permanent diagnosis.
Choose DLSS, FSR, or XeSS
Start at native output resolution, then choose the supported upscaler suited to your GPU: DLSS, FSR, or XeSS. Compare native rendering against Quality to spot foliage shimmer, fine-detail loss, or instability in motion. Move to Balanced when lowering render resolution produces a meaningful improvement and the GPU is clearly the limit.
Do not default to Performance at 1440p. Controlled testing on one launch-build route found only a limited gain over Balanced alongside more foliage noise. That is directional evidence, not a promise for every system or scene. The current Bandai requirements chart measures targets without upscaling or Frame Generation. An older Steam requirements revision used Balanced upscaling; never combine their rows.
Should you use Frame Generation?
Keep Frame Generation off while finding your rendered, or base, frame rate. The evidenced experimental 2× option creates additional displayed frames between rendered ones. It can make camera motion look smoother, but it does not double the underlying simulation or improve base responsiveness.
Test it only after the game feels playable without it. Repeat the same combat and traversal sequence while checking input response, fringing, foliage breakup, and fast-pan artifacts. Generated frames may add latency, so a larger displayed number is not automatically better. Feature status is patch-sensitive; check the official Steam news hub before relying on the experimental label.
Why stutter can remain after lowering settings
A lower preset cannot solve every hitch. If reducing output resolution or moving from Quality to Balanced materially improves the route, GPU load is the likely limit. If resolution barely changes performance while CPU work remains heavy, the bottleneck may sit with CPU or engine work.
Traversal is another case. Asset streaming or entering a new area can create a frame-time spike—a brief delay between displayed frames—even when average FPS looks acceptable. Video memory (VRAM) pressure can produce similar symptoms, so compare Medium textures with Low after a reload. If hitches survive lower resolution and Low settings, stop destroying image quality in search of a graphics-only cure.
Official hotfixes have included performance and stability changes, including Hotfix 1.0.5. Update before diagnosing, but do not assume one patch removes every route-specific spike. Engine-side behavior may remain outside a PC optimizer’s reach.
Find the limiting factor in three tests
Choose the closest bottleneck route
All three routes are shown because JavaScript is unavailable.
GPU-limited
Lower render resolution or move from Quality to Balanced. If the route improves materially, keep upscaling fixed and test reflections, effects, shadows, foliage, and detail in that order.
CPU/engine-limited
If a resolution reduction barely helps, restore image quality, close avoidable background work, and inspect CPU and frame-time behavior instead of lowering every graphics control.
VRAM/stutter
Watch video memory use, reload, and compare Medium textures with Low. If hitches survive that test and lower resolution, treat them as a patch-sensitive streaming or engine symptom.
Current PC requirements and revision note
Bandai’s current chart spans minimum, recommended, high, and ultra targets. Use the tier matching your output resolution and frame-rate goal, then treat listed hardware as a planning reference rather than a guarantee. Its targets were measured without upscaling or Frame Generation, so they are not directly comparable with results produced using either feature.
Confirm the chart through the official Bandai game page and check the official Steam store page before buying or upgrading hardware.
Test each change for 60–90 seconds
Update the game and GPU driver, reboot if appropriate, close avoidable background tasks, and choose a route with dense vegetation, open traversal, and repeatable combat. Warm it once. Run the same weather, time, and camera path at least three times while recording average FPS, frame time, and 1% lows—the slowest one percent of recorded frames. Compare medians, not the best pass.
Keep resolution and upscaling fixed while changing one setting. Reload or restart when a texture-memory comparison requires it. Establish base performance with Frame Generation off, then test generated frames separately. With variable refresh rate (VRR), cap below the monitor’s refresh ceiling rather than prescribing one number. Pick a stable target the slowest repeatable scene supports.
Frequently asked questions
What are the best PC settings for The Blood of Dawnwalker?
Start with Medium reflections, effects, shadows, detail, foliage, and textures. Keep post-processing, light, shading, and volumetrics at High. Test native rendering or Quality upscaling first, then change one control at a time on a repeatable route rather than expecting a universal FPS result.
Should I use DLSS, FSR, or XeSS in The Blood of Dawnwalker?
Choose the supported upscaler appropriate to your GPU. Compare native rendering with Quality first. Move to Balanced only when a resolution reduction shows the GPU is limiting performance. Avoid treating Performance as the automatic 1440p choice because image stability and gains vary by route.
Should I enable Frame Generation in The Blood of Dawnwalker?
Leave Frame Generation off while measuring base performance. Test the experimental 2× option only after the rendered frame rate feels playable. It can improve displayed smoothness, but may add latency, fringing, or camera-pan artifacts and does not double real rendered performance.
Which The Blood of Dawnwalker settings improve FPS first?
Test Reflections Quality first, followed by Effects Quality, Shadow Quality, then Foliage Quality and Detail Quality. Keep the route, resolution, and upscaler unchanged. Adjust textures for memory pressure, while light and post-processing remain later comparisons rather than first cuts.
Why does The Blood of Dawnwalker still stutter after lowering settings?
Stutter can come from CPU or engine work, traversal streaming, or VRAM pressure rather than raw GPU load. If lower resolution and Low settings barely change the hitch, stop sacrificing image quality. Update the game, repeat the same route, and inspect frametimes instead.
How should I set Texture Quality for my GPU’s VRAM?
Medium is the conservative starting point for an 8 GB-class GPU. Watch VRAM use and repeatable hitches, then test Low after a reload if pressure persists. Texture Quality is mainly a memory and streaming decision, not a guaranteed switch for higher average FPS.
Youtube