ROG Ally settings · Source check completed September 10, 2026

The Witcher 3 ROG Ally settings: start at 900p and 30 FPS

The Witcher 3 can move from quiet interiors to foliage-heavy travel, combat, weather, and dense city crowds. This Ally and Ally X profile starts at 900p/30 with ray tracing off, then uses a controlled 720p comparison to identify resolution pressure. It is an official-source-informed baseline—not a personally tested benchmark.

Official The Witcher 3 Wild Hunt Complete Edition Steam header artwork showing Geralt, Ciri, and Yennefer
Official Steam store header image saved locally from CD PROJEKT RED’s Steam page. Artwork and trademarks belong to their owners; use does not imply endorsement.

Starting target

900p / 30

Clarity-first conservative baseline

Fallback test

720p / 30

Change resolution alone

Expensive effects

Off

Ray tracing and HairWorks

Storage floor

50GB

Current Steam listing; add headroom

Build one repeatable route before chasing a higher number. Include horseback travel, rapid camera turns, vegetation, combat, and a populated settlement. Record the Ally model, charger state, operating mode, renderer, driver, game version, and cap before comparing changes.

Recommended The Witcher 3 ROG Ally baseline

SettingStart hereWhy
Ally operating modePerformance; compare Turbo while plugged inCreates a known power condition. Do not compare battery Performance against plugged-in Turbo as if they were one test.
Display mode / resolutionFullscreen / 1600×900Reduces render load from native 1080p while retaining more detail than 720p.
Frame-rate cap30 FPSProvides a conservative first target for cities, traversal, weather, and combat.
RendererCurrent launcher defaultProves the standard route before DirectX 11 and DirectX 12 troubleshooting.
Ray tracingOffRemoves optional next-gen effects with a high rendering cost.
Upscaling / anti-aliasingQuality-oriented modeStarts with clarity; compare a more aggressive mode only on the same route.
Texture qualityMediumPreserves useful character and world detail; lower only after repeatable memory symptoms.
Shadow qualityLowCreates headroom in foliage-heavy areas and settlements.
Terrain / water qualityMediumA balanced visual starting point to validate independently.
Foliage visibility rangeLowReduces distant vegetation load during fast traversal.
Background charactersLowPrioritizes city consistency over crowd density.
NVIDIA HairWorksOffRemoves an optional effect before sacrificing broad image clarity.
Motion blur / blurPersonal preferenceChoose for comfort, not as the primary performance fix.

Option labels can change. If the current build does not expose one of these controls, leave it alone rather than copying an old configuration-file edit. Steam currently says its requirements will change on September 29, 2026; recheck the live listing after that date.

Use two profiles to isolate the real limit

Profile A · start here

900p / 30 FPS

Use Medium textures, Low shadows, foliage, and crowds, Medium terrain and water, ray tracing off, and HairWorks off. Repeat one demanding route twice before judging it.

Profile B · diagnosis

720p / 30 FPS

Keep the same renderer, power mode, cap, quality controls, and route; lower only resolution. If pacing barely changes, look beyond pixel load before reducing clarity again.

A repeatable tuning order

  1. Update deliberately. Finish the stable game, Windows, Armoury Crate SE, BIOS, and graphics-driver updates offered for the exact Ally model, then restart.
  2. Remove stale variables. Disable mods, unexplained launch flags, and old configuration-file overrides for the first pass.
  3. Apply 900p/30. Turn ray tracing and HairWorks off, use the baseline table, and keep one frame-limiting path.
  4. Repeat a real route twice. Include travel, foliage, combat, weather, and a populated location. A menu or empty room is not a performance test.
  5. Compare 720p alone. Do not change operating mode, cap, renderer, and graphics at the same time.
  6. Reduce scene cost before textures. Keep shadows, foliage visibility, and background characters low; lower water and terrain only if the repeatable route still benefits.
  7. Raise the target last. Once the route is stable, test 40 or 60 FPS as a separate experiment and record where the result stops being consistent.

30, 40, or 60 FPS?

TargetWhen to try itDecision rule
30 FPSFirst playthrough baseline, battery-aware use, or demanding city/traversal scenesPrefer consistent pacing over an unstable higher cap.
40 FPSAfter 900p/30 is repeatable under the same power and renderer conditionsKeep only if the whole route—not just interiors—remains acceptably paced.
60 FPSAs a performance-focused experiment after lower targets are understoodDo not describe it as locked unless measured across representative scenes on the recorded configuration.

No target in this table is presented as a Handheld Settings Lab measurement. The purpose is to change one constraint at a time and avoid mistaking a brief high reading for whole-game behavior.

DirectX 11 vs DirectX 12 troubleshooting

Start with the current launcher default because game and driver updates can change renderer behavior. If a clean, updated setup still has a repeatable crash or severe stutter, DirectX 11 is a useful one-variable comparison because it excludes DirectX 12-only ray-tracing paths. It is not guaranteed to be universally faster.

SymptomCheck firstNext controlled step
Crash at launchRemove mods and flags, restart, verify files, and restore current defaultsCompare DirectX 11 without changing driver or graphics at the same time
Severe traversal stutterRepeat the route after updates and shader work; pause downloads and overlaysLower foliage, shadows, and background characters, then compare 720p alone
Image looks too softReturn to 900p and a quality-oriented upscale modeKeep scene-cost settings low rather than adding excessive sharpening
Wrong prompts or mouse inputSet Armoury Crate SE control mode to Gamepad or AutoRestore the standard gamepad layout before remapping individual actions
Turbo unavailable through a dockTest the compatible charger directly on the AllyIsolate dock and cable ratings with the dock checklist
Menus differ from an old guideReset to current defaults and use the controls actually presentDo not import stale configuration files

If both clean renderer routes fail reproducibly, use CD PROJEKT RED’s official PC support and include the game version, Ally model, Windows build, graphics driver, renderer, and exact reproduction steps.

Storage, battery, and dock planning

Steam listed 50GB of available space on September 10, 2026. That is a requirement floor, not a complete capacity budget. Leave room for game patches, temporary download files, shader data, Windows, screenshots, and saves. Use the storage planner, and check the ROG Ally SSD compatibility guide before opening the device.

No battery runtime is claimed here. Record total system draw from your own stable route—not only an APU limit—and enter it in the battery estimator. For TV play, validate the charger directly first, then use the ROG Ally dock and display checklist to isolate power, cable, and display-handshake problems.

Optional gear after the game is stable

Disclosure: these are broad Amazon searches marked sponsored/nofollow, not hands-on endorsements. Compare exact model fit, electrical and storage specifications, seller traceability, warranty, and return terms. No current price, compatibility, performance, or runtime claim is made; a real Associates tag is appended only when configured.

Compare categories in the spec-based gear library, or set a limit with the accessory budget calculator.

Frequently asked questions

What settings should I use for The Witcher 3 on ROG Ally?

Start at 1600×900, a 30 FPS cap, ray tracing off, medium textures, low shadows, low foliage visibility, low background characters, medium terrain and water, and HairWorks off. Test a repeatable city-and-traversal route before raising quality. This is a conservative editorial baseline, not a measured guarantee.

Can the ROG Ally run The Witcher 3 at 60 FPS?

A 60 FPS target may be worth testing under some model, power, renderer, and quality combinations, but this page does not claim a measured lock. Prove a stable 30 FPS profile first, then test 40 or 60 without changing resolution, power mode, and graphics at the same time.

Should I use 900p or 720p for The Witcher 3 on ROG Ally?

Begin at 900p for a useful clarity-first baseline. If the same demanding route remains uneven after ray tracing, HairWorks, crowds, foliage, and shadows are reduced, compare 720p while keeping the cap and power mode fixed. Return to 900p if 720p does not materially help.

Should I use DirectX 11 or DirectX 12 on ROG Ally?

Start with the current launcher default and ray tracing off. If crashes or severe repeatable stutter remain after updates and a clean configuration, compare DirectX 11 as one isolated variable. Do not change renderer, driver, operating mode, and graphics preset together.

Should ray tracing be enabled on ROG Ally?

No for this baseline. Disable ray-traced global illumination, reflections, shadows, and ambient occlusion. Establish stable frame pacing and acceptable image quality before considering optional effects with a high rendering cost.

How much storage does The Witcher 3 need on ROG Ally?

Steam listed 50GB of available space when checked. Leave additional capacity for patches, temporary download files, Windows, shader data, captures, and saves. Steam also says the requirements are scheduled to change on September 29, 2026, so recheck the live listing after that date.

Were these settings tested by Handheld Settings Lab?

No. Handheld Settings Lab did not personally benchmark the current game, Ally model, Windows build, graphics driver, Armoury Crate version, power mode, or thermals. This is an official-source-informed starting profile and repeatable tuning method.

Sources and methodology

Sources were checked on September 10, 2026. Steam’s public app data returned HTTP 200 and supplied the title, current 50GB Windows storage listing, DirectX context, scheduled-requirements-change note, and official header image. ASUS’s original Ally and Ally X specification pages and its first-party tuning guide returned HTTP 200 and supply device and workflow context. CD PROJEKT RED’s official PC support route also returned HTTP 200. The settings profile is conservative editorial guidance informed by those official constraints and common graphics-cost relationships. Handheld Settings Lab did not personally benchmark the current game, device, Windows build, driver, power mode, battery, or thermals, and does not claim a locked frame rate or measured runtime.

Browse more games in the ROG Ally settings hub, compare the Steam Deck Witcher 3 baseline, or plan around your own inputs with the battery, storage, and accessory calculators.