War in the North Steam Deck Settings and Performance
Set up War in the North Legacy Edition on Steam Deck after its Verified update, with Patch 2 controller glyphs and a repeatable frame-pacing check.
Patch 1 Steam Deck Verified and Patch 2 controller prompts
The official September 15 Patch 1 announcement marks Legacy Edition as Steam Deck Verified. That replaces the launch-week picture of the game having only a Windows listing; it is a compatibility status, not a promise of a particular frame rate in every chapter or split-screen scene.
Patch 2 adds Steam controller glyphs for Steam and Steam Deck, repairs loading/joining crashes and fixes several display and audio faults. Update first, choose the input method you will actually use and check that the prompts follow it. Start with a repeatable combat section and a loading transition before raising image quality; keep frame pacing, text readability and battery use as separate choices.
Use the settings below as a test sequence. Change one setting, repeat the same scene and keep the result that fits your handheld session. No fixed FPS, resolution preset or battery duration is implied by the verification badge.
Quick answer
Legacy Edition was marked Steam Deck Verified in the September 15 Patch 1 announcement. Update to Patch 2 for Steam/Deck controller glyphs, then tune a repeatable combat scene for the frame pacing and battery use you prefer.
Conservative starting profile
| Setting | Starting point | Why |
|---|---|---|
| Display | Native handheld resolution | Gives a stable reference before upscaling variables are added |
| Frame limit | 30 FPS | A realistic first target for a launch-week port with unknown frame pacing |
| Effects | Low or medium | Reduces the number of heavy variables during diagnosis |
| Refresh rate | Match the cap | Prevents a mismatch from making frame pacing look worse than it is |
| TDP and fan | Default | Record custom power settings only after a baseline exists |
| Proton | Start with the default compatible layer | Test one alternative at a time, not a collection of tweaks |
Do not call the profile “optimal.” It is a controlled starting point that can be reverted.
Measure a scene, not a menu
- Record SteamOS version, Proton version, game version, resolution, frame cap, TDP, and display refresh.
- Use the same save and the same route each time: leave the menu, enter a combat encounter, rotate the camera, and cross one transition.
- Capture average frame rate, 1% lows if available, frame pacing, loading time, fan noise, and battery drain.
- Repeat the same route after changing one setting.
- Stop if the game begins saving abnormally or the device becomes unstable.
The most useful result is not a single peak number. It is “30 FPS cap, scene X, stable/unstable, after Y minutes.” Local split screen should be tested separately because it changes rendering and input load.
How to interpret a slowdown report
If performance collapses only after leaving menus, first repeat the same route with the default profile. If the drop returns, note the exact transition and report it. Do not infer that a different Proton layer or a lower resolution fixed the game unless the same scene is repeatable.
Sources
Recommended guide route