Loading Atlas data
ASUS · ROG Ally
GamersNexus tested Baldur's Gate 3 on the ASUS ROG Ally Z1 Extreme in its stock Turbo profile on battery (Stock Turbo 25W). The benchmark used 1280 × 720, DirectX 11 and the Low in-game preset, with AMD FSR 2.2 Balanced, while framerate caps and variable-refresh features were disabled and tearing was allowed. The named global preset is directly selectable; GamersNexus did not separately expand every individual sub-setting. The published chart reports 38.7 FPS average, a 24.6 FPS 1% low and a 20.0 FPS 0.1% low. VRAM allocation, exact driver and OS builds, test route, capture tool, capture duration and run count were not published and remain unspecified.
Submitted by HandheldAtlas
Resolution
1280 × 720
TDP
25W
Average FPS
38.7 FPS
1% Low
24.6 FPS
Upscaler
AMD FSR 2.2 Balanced
Battery
Not set
Profile goal
More frames
Settings
26 values
Evidence context
Checked
Sep 1, 2026
Game version
Not set
Driver
Not set
OS
Not set
Before you copy anything
This profile is built for players who prioritize responsiveness and the highest practical frame rate. Reduce the settings that cost the most performance while protecting clarity where it matters.
Expected trade-off
Some visual effects or scene detail may be reduced.
01
ROG Ally
02
25W at 1280 × 720.
03
Apply all values first. Tune further only after the same demanding area stays stable.
Use this preset
The exact value is always visible. Explanations stay tucked underneath, so a first-time visitor can copy the preset without reading a bloody thesis.
4 groups · 26 settings
Open full Settings Guide →11 settings
Game default: The source chart labels this exact handheld configuration. → ASUS ROG Ally Z1 Extreme
Problem: mismatched device target
Reason: Fixes the hardware represented by the result.
Game default: This is the hardware variant represented by the source. → Original ROG Ally with Ryzen Z1 Extreme
Problem: model mismatch
Reason: Prevents mixing lower-spec or later-generation models.
Game default: The source row identifies this processor class. → AMD Ryzen Z1 Extreme
Problem: APU mismatch
Reason: Separates materially different handheld variants.
Game default: The tested handheld uses this physical memory configuration. → 16GB LPDDR5-6400
Problem: memory mismatch
Reason: Records system memory without inventing an unreported VRAM allocation.
Game default: The tested handheld is a Windows 11 device; the exact build was not published. → Windows 11 (exact build not reported)
Problem: OS mismatch
Reason: Preserves the OS family without fabricating a version.
Game default: This is the native panel resolution of the tested handheld. → 1920 × 1080
Problem: display mismatch
Reason: Distinguishes panel capability from the 720p render target.
Game default: This is the panel refresh capability of the tested handheld. → 120Hz
Problem: display mismatch
Reason: Records device capability without claiming an unreported selected refresh rate.
Game default: GamersNexus used this stock manufacturer profile for the chart row. → Turbo
Problem: non-comparable power profile
Reason: Reproduces the named operating mode.
Game default: The chart and manufacturer profile table define this battery power target. → Stock Turbo 25W
Problem: non-comparable TDP or PL limit
Reason: Preserves the exact tested power budget.
Game default: GamersNexus used battery power unless a row is explicitly marked otherwise. → Battery
Problem: wall-power boost mismatch
Reason: Keeps the handheld in the published operating state.
Game default: The methodology used manufacturer-defined profiles only. → Stock manufacturer-defined profile
Problem: hidden manual tuning
Reason: Avoids unreported manual clock or power tuning.
7 settings
Game default: GamersNexus used 1280 × 720 for this chart. → 1280 × 720
Problem: resolution mismatch
Reason: Matches the fixed cross-device render target.
4 settings
Game default: This API is named by the source for the game test. → DirectX 11
Problem: API mismatch
Reason: Matches the exact rendering path.
General guidance: Selects a renderer such as DirectX 11, DirectX 12 or Vulkan.
4 settings
Game default: The source chart reports onPresent FPS. → onPresent frames per second
Problem: ambiguous capture statistic
Reason: Identifies the presentation-stage stream behind the metrics.
Trust & evidence
Optional proof for people who want to inspect the data instead of just copying the values.
The important target and settings are documented, with room for more validation.
Test data
28/30
Frame rate, target resolution and power data are well documented.
Configuration depth
18/20
26 settings across 4 groups.
Explanation coverage
25/25
100% explained · 100% include a default baseline.
Community proof
0/15
0 matching-setup confirmations · 0 upvotes.
Atlas review
0/10
Not yet marked Atlas Verified by an editor.
Worked for me
0
Matching setup confirmations
Upvotes
0
Found useful
Rating
—
Community score
Editorial
No
Awaiting review
Explained
26/26
Settings with know-how
Guide linked
3/26
Knowledge-base matches
Game default: 1280 × 720 is a 16:9 target. → 16:9
Problem: framing or scaling mismatch
Reason: Preserves the source framing.
General guidance: Controls the width-to-height shape of the rendered image.
Game default: All framerate caps were disabled in the published method. → Off
Problem: capped benchmark output
Reason: Allows unrestricted measurement.
Game default: Variable-refresh features were disabled for all gaming tests. → Off
Problem: inconsistent synchronization state
Reason: Keeps comparison conditions fixed.
Game default: The source explicitly allowed tearing. → Allowed
Problem: synchronization mismatch
Reason: Matches the uncapped measurement method.
Game default: The source baseline is uncapped and allows tearing. → Off
Problem: hidden refresh-rate cap
Reason: V-Sync must remain disabled to reproduce that behavior.
General guidance: Synchronizes frame presentation to the display refresh cycle to prevent tearing.
Game default: GamersNexus standardized these chart rows to 720p. → Like-for-like 1280 × 720 across devices
Problem: incomparable device resolution
Reason: Makes the results directly comparable.
Game default: This named in-game preset is shown in the benchmark chart. → Low
Problem: mismatched graphics baseline
Reason: Selecting it reproduces the complete global graphics baseline without inventing sub-values.
Game default: This reconstruction method is named for the device in the source chart. → AMD FSR 2.2
Problem: reconstruction mismatch
Reason: Matches the tested rendering path.
Game default: This quality mode is listed by GamersNexus. → Balanced
Problem: quality-mode mismatch
Reason: Fixes the internal render target.
Game default: The chart publishes all three performance statistics. → Average, 1% low and 0.1% low
Problem: incomplete performance evidence
Reason: Preserves the complete result instead of quoting only average FPS.
Game default: The direct chart is the primary evidence artifact. → GamersNexus benchmark chart
Problem: unverifiable performance claim
Reason: Keeps the exact device row and all three values independently inspectable.
Game default: GamersNexus states the original and adapted article publication dates. → Original video April 14, 2024; article May 2, 2024
Problem: missing source date
Reason: Preserves the age and patch context of the evidence.