ROG Xbox Ally X

Why: Set to the tester's neutral visibility preference; it does not materially change GPU performance.

Why: Native 16:9 matches the 1920 × 1080 test output without stretching.

Why: Native 1920 × 1080 defines the measured target and preserves panel clarity.

Why: 100% keeps the internal render resolution fixed at the stated 1080p target.

Why: 180 Hz leaves the display uncapped while CapFrameX measures the game's actual output.

Why: Disabled so synchronization does not cap or reshape the benchmark result.

Why: Disabled during capture so the measured average and lows reflect the profile rather than a limiter.

Why: Disabled so resolution remains reproducible throughout all three runs.

Why: High improves edge stability at native resolution while retaining the 40 FPS target.

Why: Medium reduces one of the heavier GPU costs without removing useful scene depth.

Why: Medium controls open-world detail cost in dense areas and traversal.

Why: High preserves texture clarity; the Ally X memory budget can support it at this target.

Why: High retains surface geometry detail while the profile reduces cost elsewhere.

Why: High keeps landscape detail clear in the open-world test target.

Why: 16:9 matches the 1920 × 1080 output used for all three captures.

Why: Native 1080p is the fixed output target for this docked profile.

Why: Windowed Full-screen keeps overlays and capture switching reliable during testing.

Why: Custom is required because the measured profile mixes quality levels instead of using a stock preset.

Why: 240 keeps the game effectively uncapped for measurement while preventing runaway menu output.

Why: Disabled so synchronization does not cap the CapFrameX capture.

Why: Disabled so the benchmark records the profile's actual output.

Why: AMD FSR is the selected reconstruction path for the 1080p performance target.

Why: Performance mode supplies the GPU headroom needed for the high-output target.

Why: Basic reduces distant-scene CPU and GPU load during traversal.

Why: Basic reduces a costly effect to protect frame-time lows.

Why: Basic is the tested internal quality control within this custom profile.

Why: Quality retains clarity and effects where the profile has remaining headroom.

Why: Balanced limits memory pressure while preserving readable surfaces at 1080p.

Why: Basic reduces combat-effects load during heavier scenes.

Why: Basic lowers foliage density and protects performance outdoors.

Default: 1920x1080 | Problem: image clarity | Why: Native 1080p keeps the image sharp on a 1080p display | FPS: -4 | Visual: High | Restart: No

Default: Borderless Window | Problem: alt-tab stability / capture compatibility | Why: Borderless improves convenience and works well with overlays and recording tools | FPS: 0 | Visual: Low | Restart: No

Default: Variable | Problem: FPS limit | Why: Variable allows the game to use all available performance instead of forcing a fixed cap | FPS: +2 | Visual: Low | Restart: No

Default: 180.00Hz | Problem: display smoothness / input latency | Why: 180Hz allows lower latency and smoother frame delivery even with variable FPS | FPS: 0 | Visual: Low | Restart: No

Default: Off | Problem: input latency | Why: Off reduces input lag and avoids performance stalls, especially on handheld hardware | FPS: +1 | Visual: Low | Restart: No

Default: Normal | Problem: rendering compatibility | Why: Normal keeps the game stable and avoids unnecessary experimental rendering behavior | FPS: 0 | Visual: Low | Restart: No

Default: 100% | Problem: blurry image / upscaling artifacts | Why: 100% keeps native internal resolution with no upscaling or image softness | FPS: -4 | Visual: High | Restart: No

Default: Ultra | Problem: low texture detail | Why: Ultra keeps character, weapon and environment textures sharp | FPS: -2 | Visual: High | Restart: No

Default: Ultra | Problem: blurry textures at angles | Why: Ultra keeps surfaces sharper with almost no major FPS cost | FPS: -1 | Visual: Medium | Restart: No

Default: Ultra | Problem: object detail / geometry quality | Why: Ultra keeps models and environment detail cleaner | FPS: -2 | Visual: High | Restart: No

Default: FXAA+TAA | Problem: jagged edges / shimmering | Why: FXAA+TAA smooths edges and improves image stability | FPS: -2 | Visual: High | Restart: No

Default: On | Problem: blurred motion / reduced clarity | Why: Off keeps the image sharper during fast combat | FPS: +1 | Visual: Medium | Restart: No

Default: High | Problem: combat effects quality | Why: High keeps attacks, particles and visual effects looking strong without going full GPU murder mode | FPS: -3 | Visual: High | Restart: No

Default: Medium | Problem: heavy GPU load | Why: Low saves GPU time while retaining usable shadow definition on the handheld | FPS: +4 | Visual: Medium | Restart: No

Default: Off | Problem: VRAM / memory usage | Why: Off avoids extra memory pressure on handheld hardware | FPS: 0 | Visual: Low | Restart: No

Default: Off | Problem: GPU load / darkening cost | Why: Off improves performance and avoids extra shadowing cost | FPS: +3 | Visual: Medium | Restart: No

Default: Off | Problem: glow / overbright highlights | Why: Off keeps the image cleaner and slightly sharper | FPS: +1 | Visual: Low | Restart: No

Default: On | Problem: cinematic light glare | Why: On keeps the intended flashy DMC look with minimal performance cost | FPS: 0 | Visual: Low | Restart: No

Default: High | Problem: lighting atmosphere quality | Why: High keeps fog and volumetric lighting looking richer | FPS: -3 | Visual: High | Restart: No Screen Space Reflections

Default: Variable | Problem: reflection quality / GPU load | Why: Variable balances reflection quality depending on scene demand | FPS: 0 | Visual: Medium | Restart: No

Default: Variable | Problem: skin/material light softness | Why: Variable keeps character materials more natural without forcing max cost | FPS: 0 | Visual: Medium | Restart: No

Default: Off | Problem: color fringing / image clarity | Why: Off removes fake lens distortion and keeps the image cleaner | FPS: 0 | Visual: Low | Restart: No

Why: The measured profile used a 10GB UMA allocation to support 1080p textures and the game's memory demand.

Why: Disabled so synchronization does not cap the measured output.

Why: 144 keeps the game effectively uncapped relative to this profile's measured range.

Why: 1920 × 1080 is the exact output target used for the recorded result.

Why: Custom is required because the profile mixes its own scaling, effects and quality values.

Why: AMD FidelityFX Super Resolution 2.1 is the in-game reconstruction path recorded for this test.

Why: Auto allows the game to select its FSR 2.1 render ratio for the 1080p output target.

Why: 0.50 restores some edge clarity after FSR reconstruction.

Why: FSR 3.1 Frame Generation is enabled; reported output FPS therefore includes generated frames.

Why: Disabled to avoid the large GPU cost on the handheld.

Why: Low reduces CPU and GPU load in dense Night City scenes.