The original ASUS handheld that brought strong Windows gaming performance into a compact form.
Presets
12
Benchmarks
46
Best FPS
117.6
Avg FPS
46

Operating system
Windows 11
Processor
AMD Ryzen Z1 Extreme
Memory
16 GB LPDDR5
Display
7 inch
Battery
40 Wh
Weight
608 g
Hardware
Operating system
Windows 11
Processor
AMD Ryzen Z1 Extreme
Memory
16 GB LPDDR5
Storage
512 GB NVMe SSD
Display size
7 inch
Resolution
1920 × 1080
Refresh rate
120 Hz VRR
Battery
40 Wh
Weight
608 g
Atlas data
Highest tested
117.6 FPS
Average tested
46 FPS
Published presets
12
Published benchmarks
46
Device profile
Performance data and presets shown below are loaded directly from the live HandheldAtlas database.
Game settings
GamersNexus tested Red Dead Redemption 2 on the ASUS ROG Ally Z1 Extreme in its stock Turbo profile on battery (Stock Turbo 25W). The benchmark used 1280 × 720, Vulkan and the Favor Performance in-game preset, 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. Its earlier write-up of the same 720p Favor Performance benchmark explicitly states that the test runs without help from upscaling. The published chart reports 65.9 FPS average, a 42.2 FPS 1% low and a 32.9 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.
Confidence 71/100 · 0 confirmed
Resolution
1280 × 720
TDP
25W
Average
65.9 FPS
1% Low
42.2 FPS
Default: The source chart labels this exact handheld configuration. | Why: Fixes the hardware represented by the result. | Problem: mismatched device target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the hardware variant represented by the source. | Why: Prevents mixing lower-spec or later-generation models. | Problem: model mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The source row identifies this processor class. | Why: Separates materially different handheld variants. | Problem: APU mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld uses this physical memory configuration. | Why: Records system memory without inventing an unreported VRAM allocation. | Problem: memory mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld is a Windows 11 device; the exact build was not published. | Why: Preserves the OS family without fabricating a version. | Problem: OS mismatch | FPS: Software-dependent | Visual: Indirect | Restart: Not applicable
GamersNexus tested Cyberpunk 2077 v2.12 on the ASUS ROG Ally Z1 Extreme in its stock Silent profile on battery (Stock Silent 10W). The benchmark used 1280 × 720, DirectX 12 and the Low in-game preset, with AMD FSR 2.1 Quality at a 66% horizontal and vertical source scale, 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 18.8 FPS average, a 11.0 FPS 1% low and a 7.9 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.
Confidence 71/100 · 0 confirmed
Resolution
1280 × 720
TDP
10W
Average
18.8 FPS
1% Low
GamersNexus tested Cyberpunk 2077 v2.12 on the ASUS ROG Ally Z1 Extreme in its stock Turbo profile on battery (Stock Turbo 25W). The benchmark used 1280 × 720, DirectX 12 and the Low in-game preset, with AMD FSR 2.1 Quality at a 66% horizontal and vertical source scale, 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 59.3 FPS average, a 34.3 FPS 1% low and a 25.1 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.
Confidence 71/100 · 0 confirmed
Resolution
1280 × 720
TDP
25W
Average
59.3 FPS
1% Low
GamersNexus tested Resident Evil 4 on the ASUS ROG Ally Z1 Extreme in its stock Silent profile on battery (Stock Silent 10W). The benchmark used 1280 × 720, DirectX 12 and the Prioritize Performance in-game preset, with AMD FSR 2 Quality, 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 20.7 FPS average, a 14.2 FPS 1% low and a 10.9 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.
Confidence 71/100 · 0 confirmed
Resolution
1280 × 720
TDP
10W
Average
20.7 FPS
1% Low
GamersNexus tested Resident Evil 4 on the ASUS ROG Ally Z1 Extreme in its stock Performance profile on battery (Stock Performance 15W). The benchmark used 1280 × 720, DirectX 12 and the Prioritize Performance in-game preset, with AMD FSR 2 Quality, 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 48.4 FPS average, a 34.0 FPS 1% low and a 29.1 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.
Confidence 71/100 · 0 confirmed
Resolution
1280 × 720
TDP
15W
Average
48.4 FPS
1% Low
GamersNexus tested Resident Evil 4 on the ASUS ROG Ally Z1 Extreme in its stock Turbo profile on battery (Stock Turbo 25W). The benchmark used 1280 × 720, DirectX 12 and the Prioritize Performance in-game preset, with AMD FSR 2 Quality, 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 56.8 FPS average, a 42.6 FPS 1% low and a 37.9 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.
Confidence 71/100 · 0 confirmed
Resolution
1280 × 720
TDP
25W
Average
56.8 FPS
1% Low
GamersNexus tested Baldur's Gate 3 on the ASUS ROG Ally Z1 Extreme in its stock Silent profile on battery (Stock Silent 10W). 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 17.3 FPS average, a 9.0 FPS 1% low and a 7.6 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.
Confidence 71/100 · 0 confirmed
Resolution
1280 × 720
TDP
10W
Average
17.3 FPS
1% Low
GamersNexus tested Baldur's Gate 3 on the ASUS ROG Ally Z1 Extreme in its stock Performance profile on battery (Stock Performance 15W). 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 30.3 FPS average, a 19.3 FPS 1% low and a 16.7 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.
Confidence 71/100 · 0 confirmed
Resolution
1280 × 720
TDP
15W
Average
30.3 FPS
1% Low
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.
Confidence 71/100 · 0 confirmed
Resolution
1280 × 720
TDP
25W
Average
38.7 FPS
1% Low
GamersNexus tested Red Dead Redemption 2 on the ASUS ROG Ally Z1 Extreme in its stock Silent profile on battery (Stock Silent 10W). The benchmark used 1280 × 720, Vulkan and the Favor Performance in-game preset, 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. Its earlier write-up of the same 720p Favor Performance benchmark explicitly states that the test runs without help from upscaling. The published chart reports 24.3 FPS average, a 15.1 FPS 1% low and a 10.8 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.
Confidence 71/100 · 0 confirmed
Resolution
1280 × 720
TDP
10W
Average
24.3 FPS
GamersNexus tested Red Dead Redemption 2 on the ASUS ROG Ally Z1 Extreme in its stock Performance profile on battery (Stock Performance 15W). The benchmark used 1280 × 720, Vulkan and the Favor Performance in-game preset, 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. Its earlier write-up of the same 720p Favor Performance benchmark explicitly states that the test runs without help from upscaling. The published chart reports 58.0 FPS average, a 36.5 FPS 1% low and a 34.1 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.
Confidence 71/100 · 0 confirmed
Resolution
1280 × 720
TDP
15W
Average
58 FPS
GamersNexus tested Cyberpunk 2077 v2.12 on the original ASUS ROG Ally Z1 Extreme in its stock Performance 15W profile on battery. The benchmark used 1280 × 720, DirectX 12, the Low preset and FSR 2.1 Quality at a 66% source scale, with frame caps and variable refresh disabled and tearing allowed. The published chart reports 41.4 FPS average, a 23.7 FPS 1% low and a 17.9 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.
Confidence 71/100 · 0 confirmed
Resolution
1280 × 720
TDP
15W
Average
41.4 FPS
1% Low
23.7 FPS
Performance data
| Game | Preset | Resolution | TDP | Average | 1% Low | Battery |
|---|---|---|---|---|---|---|
| F1® 23 | Custom | 1280 × 720 | 25W (Turbo; battery) | 117.6 FPS | 49 FPS | Not set |
| Shadow of the Tomb Raider: Definitive Edition | Custom | 1280 × 720 | 28W | 93 FPS | — | Not set |
| F1® 23 | Custom | 1280 × 720 | 15W (Performance; battery) | 84.1 FPS | 33.2 FPS | Not set |
| Cyberpunk 2077 | Custom | 1280 × 720 | 28W | 74.35 FPS | — | Not set |
| Shadow of the Tomb Raider: Definitive Edition | Custom | 1920 × 1080 | 28W | 69 FPS | — | Not set |
| Cyberpunk 2077 | Custom | 1280x720 | 30W | 66 FPS | — | Not set |
| Red Dead Redemption 2 | Performance · GamersNexus 720p Favor Performance — Turbo 25W | 1280 × 720 | 25W | 65.9 FPS | 42.2 FPS | Not set |
| Cyberpunk 2077 | Performance · GamersNexus 720p Low AMD FSR 2.1 Quality — Turbo 25W | 1280 × 720 | 25W | 59.3 FPS | 34.3 FPS | Not set |
| The Witcher 3: Wild Hunt | Custom | 1600x900 | 30W | 59 FPS | 43 FPS | Not set |
| Red Dead Redemption 2 | Balanced · GamersNexus 720p Favor Performance — Performance 15W | 1280 × 720 | 15W | 58 FPS | 36.5 FPS | Not set |
| Resident Evil 4 | Performance · GamersNexus 720p Prioritize Performance AMD FSR 2 Quality — Turbo 25W | 1280 × 720 | 25W | 56.8 FPS | 42.6 FPS | Not set |
| Dying Light 2 Stay Human: Reloaded Edition | Custom | 1280 × 720 | 25W (Turbo; battery) | 56.3 FPS | 25.8 FPS | Not set |
| Cyberpunk 2077 | Custom | 1280x720 | 30W | 56 FPS | — | Not set |
| Cyberpunk 2077 | Custom | 1600x900 | 30W | 54 FPS | — | Not set |
| Cyberpunk 2077 | Custom | 1920 × 1080 | 28W | 53.35 FPS | — | Not set |
| The Witcher 3: Wild Hunt | Custom | 1280x720 | 15W | 51 FPS | 28 FPS | Not set |
| Resident Evil 4 | Balanced · GamersNexus 720p Prioritize Performance AMD FSR 2 Quality — Performance 15W | 1280 × 720 | 15W | 48.4 FPS | 34 FPS | Not set |
| The Witcher 3: Wild Hunt | Custom | 1920x1080 | 30W | 47 FPS | 34 FPS | Not set |
| Cyberpunk 2077 | Custom | 1920x1080 | 30W | 46 FPS | — | Not set |
| Resident Evil 4 | Custom | 1920 × 1080 | 30W (Turbo; wall power) | 44.1 FPS | 33.4 FPS | Not set |
| Cyberpunk 2077 | Custom | 1920 × 1080 | 30W (Turbo; wall power) | 44.1 FPS | 28.6 FPS | Not set |
| Resident Evil 4 | Custom | 1920 × 1080 | 25W (Turbo; battery) | 43.2 FPS | 33.5 FPS | Not set |
| Red Dead Redemption 2 | Custom | 1920 × 1080 | 30W (Turbo; wall power) | 43 FPS | 26.5 FPS | Not set |
| Red Dead Redemption 2 | Custom | 1920 × 1080 | 25W (Turbo; battery) | 42.4 FPS | 26 FPS | Not set |
| Cyberpunk 2077 | Custom | 1920 × 1080 | 25W (Turbo; battery) | 41.7 FPS | 26.3 FPS | Not set |
| Cyberpunk 2077 | Balanced · GamersNexus 720p Low FSR Quality — 15W | 1280 × 720 | 15W | 41.4 FPS | 23.7 FPS | Not set |
| Dying Light 2 Stay Human: Reloaded Edition | Custom | 1280 × 720 | 15W (Performance; battery) | 41.3 FPS | 15.6 FPS | Not set |
| Baldur's Gate 3 | Performance · GamersNexus 720p Low AMD FSR 2.2 Balanced — Turbo 25W | 1280 × 720 | 25W | 38.7 FPS | 24.6 FPS | Not set |
| F1® 23 | Custom | 1280 × 720 | 10W (Silent; battery) | 38 FPS | 14.3 FPS | Not set |
| Dying Light 2 Stay Human: Reloaded Edition | Custom | 1920 × 1080 | 30W (Turbo; wall power) | 37.5 FPS | 14.6 FPS | Not set |
| Dying Light 2 Stay Human: Reloaded Edition | Custom | 1920 × 1080 | 25W (Turbo; battery) | 36.5 FPS | 16.1 FPS | Not set |
| Red Dead Redemption 2 | Custom | 1920 × 1080 | 15W (Performance; battery) | 35.2 FPS | 20.4 FPS | Not set |
| Cyberpunk 2077 | Custom | 1920x1080 | 30W | 35 FPS | — | Not set |
| Resident Evil 4 | Custom | 1920 × 1080 | 15W (Performance; battery) | 33.9 FPS | 25.6 FPS | Not set |
| Street Fighter™ 6 | Custom | 1920 × 1080 | 28W | 32.87 FPS | — | Not set |
| Street Fighter™ 6 | Custom | 1920 × 1080 | 28W | 32.74 FPS | — | Not set |
| Baldur's Gate 3 | Balanced · GamersNexus 720p Low AMD FSR 2.2 Balanced — Performance 15W | 1280 × 720 | 15W | 30.3 FPS | 19.3 FPS | Not set |
| Dying Light 2 Stay Human: Reloaded Edition | Custom | 1920 × 1080 | 15W (Performance; battery) | 29.2 FPS | 12.5 FPS | Not set |
| Street Fighter™ 6 | Custom | 1920 × 1080 | 28W | 28.15 FPS | — | Not set |
| Cyberpunk 2077 | Custom | 1920 × 1080 | 15W (Performance; battery) | 27.8 FPS | 17.8 FPS | Not set |
| Red Dead Redemption 2 | Battery · GamersNexus 720p Favor Performance — Silent 10W | 1280 × 720 | 10W | 24.3 FPS | 15.1 FPS | Not set |
| Resident Evil 4 | Battery · GamersNexus 720p Prioritize Performance AMD FSR 2 Quality — Silent 10W | 1280 × 720 | 10W | 20.7 FPS | 14.2 FPS | Not set |
| Dying Light 2 Stay Human: Reloaded Edition | Custom | 1280 × 720 | 10W (Silent; battery) | 20.2 FPS | 7.3 FPS | Not set |
| Cyberpunk 2077 | Battery · GamersNexus 720p Low AMD FSR 2.1 Quality — Silent 10W | 1280 × 720 | 10W | 18.8 FPS | 11 FPS | Not set |
| Baldur's Gate 3 | Battery · GamersNexus 720p Low AMD FSR 2.2 Balanced — Silent 10W | 1280 × 720 | 10W | 17.3 FPS | 9 FPS | Not set |
| Resident Evil 4 | Custom | 1920 × 1080 | 10W (Silent; battery) | 14.8 FPS | 11.6 FPS | Not set |
Default: This is the native panel resolution of the tested handheld. | Why: Distinguishes panel capability from the 720p render target. | Problem: display mismatch | FPS: None for the fixed test target | Visual: Indirect | Restart: Not applicable
Default: This is the panel refresh capability of the tested handheld. | Why: Records device capability without claiming an unreported selected refresh rate. | Problem: display mismatch | FPS: None for the published measurement | Visual: Indirect | Restart: Not applicable
Default: GamersNexus used this stock manufacturer profile for the chart row. | Why: Reproduces the named operating mode. | Problem: non-comparable power profile | FPS: High impact | Visual: Indirect | Restart: No
Default: The chart and manufacturer profile table define this battery power target. | Why: Preserves the exact tested power budget. | Problem: non-comparable TDP or PL limit | FPS: High impact | Visual: Indirect | Restart: No
Default: GamersNexus used battery power unless a row is explicitly marked otherwise. | Why: Keeps the handheld in the published operating state. | Problem: wall-power boost mismatch | FPS: High impact | Visual: None | Restart: No
Default: The methodology used manufacturer-defined profiles only. | Why: Avoids unreported manual clock or power tuning. | Problem: hidden manual tuning | FPS: High impact | Visual: None | Restart: No
Default: GamersNexus used 1280 × 720 for this chart. | Why: Matches the fixed cross-device render target. | Problem: resolution mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: 1280 × 720 is a 16:9 target. | Why: Preserves the source framing. | Problem: framing or scaling mismatch | FPS: Low impact | Visual: Medium impact | Restart: No
Default: All framerate caps were disabled in the published method. | Why: Allows unrestricted measurement. | Problem: capped benchmark output | FPS: High impact | Visual: None | Restart: No
Default: Variable-refresh features were disabled for all gaming tests. | Why: Keeps comparison conditions fixed. | Problem: inconsistent synchronization state | FPS: Measurement-dependent | Visual: Low impact | Restart: No
Default: The source explicitly allowed tearing. | Why: Matches the uncapped measurement method. | Problem: synchronization mismatch | FPS: Measurement-dependent | Visual: Medium impact | Restart: No
Default: The source baseline is uncapped and allows tearing. | Why: V-Sync must remain disabled to reproduce that behavior. | Problem: hidden refresh-rate cap | FPS: High impact | Visual: Medium impact | Restart: No
Default: GamersNexus standardized these chart rows to 720p. | Why: Makes the results directly comparable. | Problem: incomparable device resolution | FPS: High impact | Visual: High impact | Restart: No
Default: This API is named by the source for the game test. | Why: Matches the exact rendering path. | Problem: API mismatch | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: This named in-game preset is shown in the benchmark chart. | Why: Selecting it reproduces the complete global graphics baseline without inventing sub-values. | Problem: mismatched graphics baseline | FPS: High impact | Visual: High impact | Restart: Follow the game prompt
Default: GamersNexus states that this same 720p Favor Performance benchmark runs without help from upscaling. | Why: Preserves the native render path rather than assuming FSR. | Problem: upscaler mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: The source chart reports onPresent FPS. | Why: Identifies the presentation-stage stream behind the metrics. | Problem: ambiguous capture statistic | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The chart publishes all three performance statistics. | Why: Preserves the complete result instead of quoting only average FPS. | Problem: incomplete performance evidence | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The direct chart is the primary evidence artifact. | Why: Keeps the exact device row and all three values independently inspectable. | Problem: unverifiable performance claim | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: GamersNexus states the original and adapted article publication dates. | Why: Preserves the age and patch context of the evidence. | Problem: missing source date | FPS: Measurement only | Visual: None | Restart: Not applicable
11 FPS
Default: The source chart labels this exact handheld configuration. | Why: Fixes the hardware represented by the result. | Problem: mismatched device target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the hardware variant represented by the source. | Why: Prevents mixing lower-spec or later-generation models. | Problem: model mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The source row identifies this processor class. | Why: Separates materially different handheld variants. | Problem: APU mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld uses this physical memory configuration. | Why: Records system memory without inventing an unreported VRAM allocation. | Problem: memory mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld is a Windows 11 device; the exact build was not published. | Why: Preserves the OS family without fabricating a version. | Problem: OS mismatch | FPS: Software-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the native panel resolution of the tested handheld. | Why: Distinguishes panel capability from the 720p render target. | Problem: display mismatch | FPS: None for the fixed test target | Visual: Indirect | Restart: Not applicable
Default: This is the panel refresh capability of the tested handheld. | Why: Records device capability without claiming an unreported selected refresh rate. | Problem: display mismatch | FPS: None for the published measurement | Visual: Indirect | Restart: Not applicable
Default: GamersNexus used this stock manufacturer profile for the chart row. | Why: Reproduces the named operating mode. | Problem: non-comparable power profile | FPS: High impact | Visual: Indirect | Restart: No
Default: The chart and manufacturer profile table define this battery power target. | Why: Preserves the exact tested power budget. | Problem: non-comparable TDP or PL limit | FPS: High impact | Visual: Indirect | Restart: No
Default: GamersNexus used battery power unless a row is explicitly marked otherwise. | Why: Keeps the handheld in the published operating state. | Problem: wall-power boost mismatch | FPS: High impact | Visual: None | Restart: No
Default: The methodology used manufacturer-defined profiles only. | Why: Avoids unreported manual clock or power tuning. | Problem: hidden manual tuning | FPS: High impact | Visual: None | Restart: No
Default: GamersNexus used 1280 × 720 for this chart. | Why: Matches the fixed cross-device render target. | Problem: resolution mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: 1280 × 720 is a 16:9 target. | Why: Preserves the source framing. | Problem: framing or scaling mismatch | FPS: Low impact | Visual: Medium impact | Restart: No
Default: All framerate caps were disabled in the published method. | Why: Allows unrestricted measurement. | Problem: capped benchmark output | FPS: High impact | Visual: None | Restart: No
Default: Variable-refresh features were disabled for all gaming tests. | Why: Keeps comparison conditions fixed. | Problem: inconsistent synchronization state | FPS: Measurement-dependent | Visual: Low impact | Restart: No
Default: The source explicitly allowed tearing. | Why: Matches the uncapped measurement method. | Problem: synchronization mismatch | FPS: Measurement-dependent | Visual: Medium impact | Restart: No
Default: The source baseline is uncapped and allows tearing. | Why: V-Sync must remain disabled to reproduce that behavior. | Problem: hidden refresh-rate cap | FPS: High impact | Visual: Medium impact | Restart: No
Default: This API is named by the source for the game test. | Why: Matches the exact rendering path. | Problem: API mismatch | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: This named in-game preset is shown in the benchmark chart. | Why: Selecting it reproduces the complete global graphics baseline without inventing sub-values. | Problem: mismatched graphics baseline | FPS: High impact | Visual: High impact | Restart: Follow the game prompt
Default: This reconstruction method is named for the device in the source chart. | Why: Matches the tested rendering path. | Problem: reconstruction mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: This quality mode is listed by GamersNexus. | Why: Fixes the internal render target. | Problem: quality-mode mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: GamersNexus normalized the source width to 66%. | Why: Matches the exact FSR and XeSS comparison ratio. | Problem: horizontal source-scale mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: GamersNexus normalized the source height to 66%. | Why: Matches the exact FSR and XeSS comparison ratio. | Problem: vertical source-scale mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: The source chart reports onPresent FPS. | Why: Identifies the presentation-stage stream behind the metrics. | Problem: ambiguous capture statistic | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The chart publishes all three performance statistics. | Why: Preserves the complete result instead of quoting only average FPS. | Problem: incomplete performance evidence | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The direct chart is the primary evidence artifact. | Why: Keeps the exact device row and all three values independently inspectable. | Problem: unverifiable performance claim | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: GamersNexus states the original and adapted article publication dates. | Why: Preserves the age and patch context of the evidence. | Problem: missing source date | FPS: Measurement only | Visual: None | Restart: Not applicable
34.3 FPS
Default: The source chart labels this exact handheld configuration. | Why: Fixes the hardware represented by the result. | Problem: mismatched device target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the hardware variant represented by the source. | Why: Prevents mixing lower-spec or later-generation models. | Problem: model mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The source row identifies this processor class. | Why: Separates materially different handheld variants. | Problem: APU mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld uses this physical memory configuration. | Why: Records system memory without inventing an unreported VRAM allocation. | Problem: memory mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld is a Windows 11 device; the exact build was not published. | Why: Preserves the OS family without fabricating a version. | Problem: OS mismatch | FPS: Software-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the native panel resolution of the tested handheld. | Why: Distinguishes panel capability from the 720p render target. | Problem: display mismatch | FPS: None for the fixed test target | Visual: Indirect | Restart: Not applicable
Default: This is the panel refresh capability of the tested handheld. | Why: Records device capability without claiming an unreported selected refresh rate. | Problem: display mismatch | FPS: None for the published measurement | Visual: Indirect | Restart: Not applicable
Default: GamersNexus used this stock manufacturer profile for the chart row. | Why: Reproduces the named operating mode. | Problem: non-comparable power profile | FPS: High impact | Visual: Indirect | Restart: No
Default: The chart and manufacturer profile table define this battery power target. | Why: Preserves the exact tested power budget. | Problem: non-comparable TDP or PL limit | FPS: High impact | Visual: Indirect | Restart: No
Default: GamersNexus used battery power unless a row is explicitly marked otherwise. | Why: Keeps the handheld in the published operating state. | Problem: wall-power boost mismatch | FPS: High impact | Visual: None | Restart: No
Default: The methodology used manufacturer-defined profiles only. | Why: Avoids unreported manual clock or power tuning. | Problem: hidden manual tuning | FPS: High impact | Visual: None | Restart: No
Default: GamersNexus used 1280 × 720 for this chart. | Why: Matches the fixed cross-device render target. | Problem: resolution mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: 1280 × 720 is a 16:9 target. | Why: Preserves the source framing. | Problem: framing or scaling mismatch | FPS: Low impact | Visual: Medium impact | Restart: No
Default: All framerate caps were disabled in the published method. | Why: Allows unrestricted measurement. | Problem: capped benchmark output | FPS: High impact | Visual: None | Restart: No
Default: Variable-refresh features were disabled for all gaming tests. | Why: Keeps comparison conditions fixed. | Problem: inconsistent synchronization state | FPS: Measurement-dependent | Visual: Low impact | Restart: No
Default: The source explicitly allowed tearing. | Why: Matches the uncapped measurement method. | Problem: synchronization mismatch | FPS: Measurement-dependent | Visual: Medium impact | Restart: No
Default: The source baseline is uncapped and allows tearing. | Why: V-Sync must remain disabled to reproduce that behavior. | Problem: hidden refresh-rate cap | FPS: High impact | Visual: Medium impact | Restart: No
Default: This API is named by the source for the game test. | Why: Matches the exact rendering path. | Problem: API mismatch | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: This named in-game preset is shown in the benchmark chart. | Why: Selecting it reproduces the complete global graphics baseline without inventing sub-values. | Problem: mismatched graphics baseline | FPS: High impact | Visual: High impact | Restart: Follow the game prompt
Default: This reconstruction method is named for the device in the source chart. | Why: Matches the tested rendering path. | Problem: reconstruction mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: This quality mode is listed by GamersNexus. | Why: Fixes the internal render target. | Problem: quality-mode mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: GamersNexus normalized the source width to 66%. | Why: Matches the exact FSR and XeSS comparison ratio. | Problem: horizontal source-scale mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: GamersNexus normalized the source height to 66%. | Why: Matches the exact FSR and XeSS comparison ratio. | Problem: vertical source-scale mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: The source chart reports onPresent FPS. | Why: Identifies the presentation-stage stream behind the metrics. | Problem: ambiguous capture statistic | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The chart publishes all three performance statistics. | Why: Preserves the complete result instead of quoting only average FPS. | Problem: incomplete performance evidence | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The direct chart is the primary evidence artifact. | Why: Keeps the exact device row and all three values independently inspectable. | Problem: unverifiable performance claim | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: GamersNexus states the original and adapted article publication dates. | Why: Preserves the age and patch context of the evidence. | Problem: missing source date | FPS: Measurement only | Visual: None | Restart: Not applicable
14.2 FPS
Default: The source chart labels this exact handheld configuration. | Why: Fixes the hardware represented by the result. | Problem: mismatched device target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the hardware variant represented by the source. | Why: Prevents mixing lower-spec or later-generation models. | Problem: model mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The source row identifies this processor class. | Why: Separates materially different handheld variants. | Problem: APU mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld uses this physical memory configuration. | Why: Records system memory without inventing an unreported VRAM allocation. | Problem: memory mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld is a Windows 11 device; the exact build was not published. | Why: Preserves the OS family without fabricating a version. | Problem: OS mismatch | FPS: Software-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the native panel resolution of the tested handheld. | Why: Distinguishes panel capability from the 720p render target. | Problem: display mismatch | FPS: None for the fixed test target | Visual: Indirect | Restart: Not applicable
Default: This is the panel refresh capability of the tested handheld. | Why: Records device capability without claiming an unreported selected refresh rate. | Problem: display mismatch | FPS: None for the published measurement | Visual: Indirect | Restart: Not applicable
Default: GamersNexus used this stock manufacturer profile for the chart row. | Why: Reproduces the named operating mode. | Problem: non-comparable power profile | FPS: High impact | Visual: Indirect | Restart: No
Default: The chart and manufacturer profile table define this battery power target. | Why: Preserves the exact tested power budget. | Problem: non-comparable TDP or PL limit | FPS: High impact | Visual: Indirect | Restart: No
Default: GamersNexus used battery power unless a row is explicitly marked otherwise. | Why: Keeps the handheld in the published operating state. | Problem: wall-power boost mismatch | FPS: High impact | Visual: None | Restart: No
Default: The methodology used manufacturer-defined profiles only. | Why: Avoids unreported manual clock or power tuning. | Problem: hidden manual tuning | FPS: High impact | Visual: None | Restart: No
Default: GamersNexus used 1280 × 720 for this chart. | Why: Matches the fixed cross-device render target. | Problem: resolution mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: 1280 × 720 is a 16:9 target. | Why: Preserves the source framing. | Problem: framing or scaling mismatch | FPS: Low impact | Visual: Medium impact | Restart: No
Default: All framerate caps were disabled in the published method. | Why: Allows unrestricted measurement. | Problem: capped benchmark output | FPS: High impact | Visual: None | Restart: No
Default: Variable-refresh features were disabled for all gaming tests. | Why: Keeps comparison conditions fixed. | Problem: inconsistent synchronization state | FPS: Measurement-dependent | Visual: Low impact | Restart: No
Default: The source explicitly allowed tearing. | Why: Matches the uncapped measurement method. | Problem: synchronization mismatch | FPS: Measurement-dependent | Visual: Medium impact | Restart: No
Default: The source baseline is uncapped and allows tearing. | Why: V-Sync must remain disabled to reproduce that behavior. | Problem: hidden refresh-rate cap | FPS: High impact | Visual: Medium impact | Restart: No
Default: This API is named by the source for the game test. | Why: Matches the exact rendering path. | Problem: API mismatch | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: This named in-game preset is shown in the benchmark chart. | Why: Selecting it reproduces the complete global graphics baseline without inventing sub-values. | Problem: mismatched graphics baseline | FPS: High impact | Visual: High impact | Restart: Follow the game prompt
Default: This reconstruction method is named for the device in the source chart. | Why: Matches the tested rendering path. | Problem: reconstruction mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: This quality mode is listed by GamersNexus. | Why: Fixes the internal render target. | Problem: quality-mode mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: The source chart reports onPresent FPS. | Why: Identifies the presentation-stage stream behind the metrics. | Problem: ambiguous capture statistic | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The chart publishes all three performance statistics. | Why: Preserves the complete result instead of quoting only average FPS. | Problem: incomplete performance evidence | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The direct chart is the primary evidence artifact. | Why: Keeps the exact device row and all three values independently inspectable. | Problem: unverifiable performance claim | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: GamersNexus states the original and adapted article publication dates. | Why: Preserves the age and patch context of the evidence. | Problem: missing source date | FPS: Measurement only | Visual: None | Restart: Not applicable
34 FPS
Default: The source chart labels this exact handheld configuration. | Why: Fixes the hardware represented by the result. | Problem: mismatched device target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the hardware variant represented by the source. | Why: Prevents mixing lower-spec or later-generation models. | Problem: model mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The source row identifies this processor class. | Why: Separates materially different handheld variants. | Problem: APU mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld uses this physical memory configuration. | Why: Records system memory without inventing an unreported VRAM allocation. | Problem: memory mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld is a Windows 11 device; the exact build was not published. | Why: Preserves the OS family without fabricating a version. | Problem: OS mismatch | FPS: Software-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the native panel resolution of the tested handheld. | Why: Distinguishes panel capability from the 720p render target. | Problem: display mismatch | FPS: None for the fixed test target | Visual: Indirect | Restart: Not applicable
Default: This is the panel refresh capability of the tested handheld. | Why: Records device capability without claiming an unreported selected refresh rate. | Problem: display mismatch | FPS: None for the published measurement | Visual: Indirect | Restart: Not applicable
Default: GamersNexus used this stock manufacturer profile for the chart row. | Why: Reproduces the named operating mode. | Problem: non-comparable power profile | FPS: High impact | Visual: Indirect | Restart: No
Default: The chart and manufacturer profile table define this battery power target. | Why: Preserves the exact tested power budget. | Problem: non-comparable TDP or PL limit | FPS: High impact | Visual: Indirect | Restart: No
Default: GamersNexus used battery power unless a row is explicitly marked otherwise. | Why: Keeps the handheld in the published operating state. | Problem: wall-power boost mismatch | FPS: High impact | Visual: None | Restart: No
Default: The methodology used manufacturer-defined profiles only. | Why: Avoids unreported manual clock or power tuning. | Problem: hidden manual tuning | FPS: High impact | Visual: None | Restart: No
Default: GamersNexus used 1280 × 720 for this chart. | Why: Matches the fixed cross-device render target. | Problem: resolution mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: 1280 × 720 is a 16:9 target. | Why: Preserves the source framing. | Problem: framing or scaling mismatch | FPS: Low impact | Visual: Medium impact | Restart: No
Default: All framerate caps were disabled in the published method. | Why: Allows unrestricted measurement. | Problem: capped benchmark output | FPS: High impact | Visual: None | Restart: No
Default: Variable-refresh features were disabled for all gaming tests. | Why: Keeps comparison conditions fixed. | Problem: inconsistent synchronization state | FPS: Measurement-dependent | Visual: Low impact | Restart: No
Default: The source explicitly allowed tearing. | Why: Matches the uncapped measurement method. | Problem: synchronization mismatch | FPS: Measurement-dependent | Visual: Medium impact | Restart: No
Default: The source baseline is uncapped and allows tearing. | Why: V-Sync must remain disabled to reproduce that behavior. | Problem: hidden refresh-rate cap | FPS: High impact | Visual: Medium impact | Restart: No
Default: This API is named by the source for the game test. | Why: Matches the exact rendering path. | Problem: API mismatch | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: This named in-game preset is shown in the benchmark chart. | Why: Selecting it reproduces the complete global graphics baseline without inventing sub-values. | Problem: mismatched graphics baseline | FPS: High impact | Visual: High impact | Restart: Follow the game prompt
Default: This reconstruction method is named for the device in the source chart. | Why: Matches the tested rendering path. | Problem: reconstruction mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: This quality mode is listed by GamersNexus. | Why: Fixes the internal render target. | Problem: quality-mode mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: The source chart reports onPresent FPS. | Why: Identifies the presentation-stage stream behind the metrics. | Problem: ambiguous capture statistic | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The chart publishes all three performance statistics. | Why: Preserves the complete result instead of quoting only average FPS. | Problem: incomplete performance evidence | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The direct chart is the primary evidence artifact. | Why: Keeps the exact device row and all three values independently inspectable. | Problem: unverifiable performance claim | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: GamersNexus states the original and adapted article publication dates. | Why: Preserves the age and patch context of the evidence. | Problem: missing source date | FPS: Measurement only | Visual: None | Restart: Not applicable
42.6 FPS
Default: The source chart labels this exact handheld configuration. | Why: Fixes the hardware represented by the result. | Problem: mismatched device target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the hardware variant represented by the source. | Why: Prevents mixing lower-spec or later-generation models. | Problem: model mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The source row identifies this processor class. | Why: Separates materially different handheld variants. | Problem: APU mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld uses this physical memory configuration. | Why: Records system memory without inventing an unreported VRAM allocation. | Problem: memory mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld is a Windows 11 device; the exact build was not published. | Why: Preserves the OS family without fabricating a version. | Problem: OS mismatch | FPS: Software-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the native panel resolution of the tested handheld. | Why: Distinguishes panel capability from the 720p render target. | Problem: display mismatch | FPS: None for the fixed test target | Visual: Indirect | Restart: Not applicable
Default: This is the panel refresh capability of the tested handheld. | Why: Records device capability without claiming an unreported selected refresh rate. | Problem: display mismatch | FPS: None for the published measurement | Visual: Indirect | Restart: Not applicable
Default: GamersNexus used this stock manufacturer profile for the chart row. | Why: Reproduces the named operating mode. | Problem: non-comparable power profile | FPS: High impact | Visual: Indirect | Restart: No
Default: The chart and manufacturer profile table define this battery power target. | Why: Preserves the exact tested power budget. | Problem: non-comparable TDP or PL limit | FPS: High impact | Visual: Indirect | Restart: No
Default: GamersNexus used battery power unless a row is explicitly marked otherwise. | Why: Keeps the handheld in the published operating state. | Problem: wall-power boost mismatch | FPS: High impact | Visual: None | Restart: No
Default: The methodology used manufacturer-defined profiles only. | Why: Avoids unreported manual clock or power tuning. | Problem: hidden manual tuning | FPS: High impact | Visual: None | Restart: No
Default: GamersNexus used 1280 × 720 for this chart. | Why: Matches the fixed cross-device render target. | Problem: resolution mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: 1280 × 720 is a 16:9 target. | Why: Preserves the source framing. | Problem: framing or scaling mismatch | FPS: Low impact | Visual: Medium impact | Restart: No
Default: All framerate caps were disabled in the published method. | Why: Allows unrestricted measurement. | Problem: capped benchmark output | FPS: High impact | Visual: None | Restart: No
Default: Variable-refresh features were disabled for all gaming tests. | Why: Keeps comparison conditions fixed. | Problem: inconsistent synchronization state | FPS: Measurement-dependent | Visual: Low impact | Restart: No
Default: The source explicitly allowed tearing. | Why: Matches the uncapped measurement method. | Problem: synchronization mismatch | FPS: Measurement-dependent | Visual: Medium impact | Restart: No
Default: The source baseline is uncapped and allows tearing. | Why: V-Sync must remain disabled to reproduce that behavior. | Problem: hidden refresh-rate cap | FPS: High impact | Visual: Medium impact | Restart: No
Default: This API is named by the source for the game test. | Why: Matches the exact rendering path. | Problem: API mismatch | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: This named in-game preset is shown in the benchmark chart. | Why: Selecting it reproduces the complete global graphics baseline without inventing sub-values. | Problem: mismatched graphics baseline | FPS: High impact | Visual: High impact | Restart: Follow the game prompt
Default: This reconstruction method is named for the device in the source chart. | Why: Matches the tested rendering path. | Problem: reconstruction mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: This quality mode is listed by GamersNexus. | Why: Fixes the internal render target. | Problem: quality-mode mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: The source chart reports onPresent FPS. | Why: Identifies the presentation-stage stream behind the metrics. | Problem: ambiguous capture statistic | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The chart publishes all three performance statistics. | Why: Preserves the complete result instead of quoting only average FPS. | Problem: incomplete performance evidence | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The direct chart is the primary evidence artifact. | Why: Keeps the exact device row and all three values independently inspectable. | Problem: unverifiable performance claim | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: GamersNexus states the original and adapted article publication dates. | Why: Preserves the age and patch context of the evidence. | Problem: missing source date | FPS: Measurement only | Visual: None | Restart: Not applicable
9 FPS
Default: The source chart labels this exact handheld configuration. | Why: Fixes the hardware represented by the result. | Problem: mismatched device target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the hardware variant represented by the source. | Why: Prevents mixing lower-spec or later-generation models. | Problem: model mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The source row identifies this processor class. | Why: Separates materially different handheld variants. | Problem: APU mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld uses this physical memory configuration. | Why: Records system memory without inventing an unreported VRAM allocation. | Problem: memory mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld is a Windows 11 device; the exact build was not published. | Why: Preserves the OS family without fabricating a version. | Problem: OS mismatch | FPS: Software-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the native panel resolution of the tested handheld. | Why: Distinguishes panel capability from the 720p render target. | Problem: display mismatch | FPS: None for the fixed test target | Visual: Indirect | Restart: Not applicable
Default: This is the panel refresh capability of the tested handheld. | Why: Records device capability without claiming an unreported selected refresh rate. | Problem: display mismatch | FPS: None for the published measurement | Visual: Indirect | Restart: Not applicable
Default: GamersNexus used this stock manufacturer profile for the chart row. | Why: Reproduces the named operating mode. | Problem: non-comparable power profile | FPS: High impact | Visual: Indirect | Restart: No
Default: The chart and manufacturer profile table define this battery power target. | Why: Preserves the exact tested power budget. | Problem: non-comparable TDP or PL limit | FPS: High impact | Visual: Indirect | Restart: No
Default: GamersNexus used battery power unless a row is explicitly marked otherwise. | Why: Keeps the handheld in the published operating state. | Problem: wall-power boost mismatch | FPS: High impact | Visual: None | Restart: No
Default: The methodology used manufacturer-defined profiles only. | Why: Avoids unreported manual clock or power tuning. | Problem: hidden manual tuning | FPS: High impact | Visual: None | Restart: No
Default: GamersNexus used 1280 × 720 for this chart. | Why: Matches the fixed cross-device render target. | Problem: resolution mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: 1280 × 720 is a 16:9 target. | Why: Preserves the source framing. | Problem: framing or scaling mismatch | FPS: Low impact | Visual: Medium impact | Restart: No
Default: All framerate caps were disabled in the published method. | Why: Allows unrestricted measurement. | Problem: capped benchmark output | FPS: High impact | Visual: None | Restart: No
Default: Variable-refresh features were disabled for all gaming tests. | Why: Keeps comparison conditions fixed. | Problem: inconsistent synchronization state | FPS: Measurement-dependent | Visual: Low impact | Restart: No
Default: The source explicitly allowed tearing. | Why: Matches the uncapped measurement method. | Problem: synchronization mismatch | FPS: Measurement-dependent | Visual: Medium impact | Restart: No
Default: The source baseline is uncapped and allows tearing. | Why: V-Sync must remain disabled to reproduce that behavior. | Problem: hidden refresh-rate cap | FPS: High impact | Visual: Medium impact | Restart: No
Default: This API is named by the source for the game test. | Why: Matches the exact rendering path. | Problem: API mismatch | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: This named in-game preset is shown in the benchmark chart. | Why: Selecting it reproduces the complete global graphics baseline without inventing sub-values. | Problem: mismatched graphics baseline | FPS: High impact | Visual: High impact | Restart: Follow the game prompt
Default: This reconstruction method is named for the device in the source chart. | Why: Matches the tested rendering path. | Problem: reconstruction mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: This quality mode is listed by GamersNexus. | Why: Fixes the internal render target. | Problem: quality-mode mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: The source chart reports onPresent FPS. | Why: Identifies the presentation-stage stream behind the metrics. | Problem: ambiguous capture statistic | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The chart publishes all three performance statistics. | Why: Preserves the complete result instead of quoting only average FPS. | Problem: incomplete performance evidence | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The direct chart is the primary evidence artifact. | Why: Keeps the exact device row and all three values independently inspectable. | Problem: unverifiable performance claim | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: GamersNexus states the original and adapted article publication dates. | Why: Preserves the age and patch context of the evidence. | Problem: missing source date | FPS: Measurement only | Visual: None | Restart: Not applicable
19.3 FPS
Default: The source chart labels this exact handheld configuration. | Why: Fixes the hardware represented by the result. | Problem: mismatched device target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the hardware variant represented by the source. | Why: Prevents mixing lower-spec or later-generation models. | Problem: model mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The source row identifies this processor class. | Why: Separates materially different handheld variants. | Problem: APU mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld uses this physical memory configuration. | Why: Records system memory without inventing an unreported VRAM allocation. | Problem: memory mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld is a Windows 11 device; the exact build was not published. | Why: Preserves the OS family without fabricating a version. | Problem: OS mismatch | FPS: Software-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the native panel resolution of the tested handheld. | Why: Distinguishes panel capability from the 720p render target. | Problem: display mismatch | FPS: None for the fixed test target | Visual: Indirect | Restart: Not applicable
Default: This is the panel refresh capability of the tested handheld. | Why: Records device capability without claiming an unreported selected refresh rate. | Problem: display mismatch | FPS: None for the published measurement | Visual: Indirect | Restart: Not applicable
Default: GamersNexus used this stock manufacturer profile for the chart row. | Why: Reproduces the named operating mode. | Problem: non-comparable power profile | FPS: High impact | Visual: Indirect | Restart: No
Default: The chart and manufacturer profile table define this battery power target. | Why: Preserves the exact tested power budget. | Problem: non-comparable TDP or PL limit | FPS: High impact | Visual: Indirect | Restart: No
Default: GamersNexus used battery power unless a row is explicitly marked otherwise. | Why: Keeps the handheld in the published operating state. | Problem: wall-power boost mismatch | FPS: High impact | Visual: None | Restart: No
Default: The methodology used manufacturer-defined profiles only. | Why: Avoids unreported manual clock or power tuning. | Problem: hidden manual tuning | FPS: High impact | Visual: None | Restart: No
Default: GamersNexus used 1280 × 720 for this chart. | Why: Matches the fixed cross-device render target. | Problem: resolution mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: 1280 × 720 is a 16:9 target. | Why: Preserves the source framing. | Problem: framing or scaling mismatch | FPS: Low impact | Visual: Medium impact | Restart: No
Default: All framerate caps were disabled in the published method. | Why: Allows unrestricted measurement. | Problem: capped benchmark output | FPS: High impact | Visual: None | Restart: No
Default: Variable-refresh features were disabled for all gaming tests. | Why: Keeps comparison conditions fixed. | Problem: inconsistent synchronization state | FPS: Measurement-dependent | Visual: Low impact | Restart: No
Default: The source explicitly allowed tearing. | Why: Matches the uncapped measurement method. | Problem: synchronization mismatch | FPS: Measurement-dependent | Visual: Medium impact | Restart: No
Default: The source baseline is uncapped and allows tearing. | Why: V-Sync must remain disabled to reproduce that behavior. | Problem: hidden refresh-rate cap | FPS: High impact | Visual: Medium impact | Restart: No
Default: This API is named by the source for the game test. | Why: Matches the exact rendering path. | Problem: API mismatch | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: This named in-game preset is shown in the benchmark chart. | Why: Selecting it reproduces the complete global graphics baseline without inventing sub-values. | Problem: mismatched graphics baseline | FPS: High impact | Visual: High impact | Restart: Follow the game prompt
Default: This reconstruction method is named for the device in the source chart. | Why: Matches the tested rendering path. | Problem: reconstruction mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: This quality mode is listed by GamersNexus. | Why: Fixes the internal render target. | Problem: quality-mode mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: The source chart reports onPresent FPS. | Why: Identifies the presentation-stage stream behind the metrics. | Problem: ambiguous capture statistic | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The chart publishes all three performance statistics. | Why: Preserves the complete result instead of quoting only average FPS. | Problem: incomplete performance evidence | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The direct chart is the primary evidence artifact. | Why: Keeps the exact device row and all three values independently inspectable. | Problem: unverifiable performance claim | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: GamersNexus states the original and adapted article publication dates. | Why: Preserves the age and patch context of the evidence. | Problem: missing source date | FPS: Measurement only | Visual: None | Restart: Not applicable
24.6 FPS
Default: The source chart labels this exact handheld configuration. | Why: Fixes the hardware represented by the result. | Problem: mismatched device target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the hardware variant represented by the source. | Why: Prevents mixing lower-spec or later-generation models. | Problem: model mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The source row identifies this processor class. | Why: Separates materially different handheld variants. | Problem: APU mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld uses this physical memory configuration. | Why: Records system memory without inventing an unreported VRAM allocation. | Problem: memory mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld is a Windows 11 device; the exact build was not published. | Why: Preserves the OS family without fabricating a version. | Problem: OS mismatch | FPS: Software-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the native panel resolution of the tested handheld. | Why: Distinguishes panel capability from the 720p render target. | Problem: display mismatch | FPS: None for the fixed test target | Visual: Indirect | Restart: Not applicable
Default: This is the panel refresh capability of the tested handheld. | Why: Records device capability without claiming an unreported selected refresh rate. | Problem: display mismatch | FPS: None for the published measurement | Visual: Indirect | Restart: Not applicable
Default: GamersNexus used this stock manufacturer profile for the chart row. | Why: Reproduces the named operating mode. | Problem: non-comparable power profile | FPS: High impact | Visual: Indirect | Restart: No
Default: The chart and manufacturer profile table define this battery power target. | Why: Preserves the exact tested power budget. | Problem: non-comparable TDP or PL limit | FPS: High impact | Visual: Indirect | Restart: No
Default: GamersNexus used battery power unless a row is explicitly marked otherwise. | Why: Keeps the handheld in the published operating state. | Problem: wall-power boost mismatch | FPS: High impact | Visual: None | Restart: No
Default: The methodology used manufacturer-defined profiles only. | Why: Avoids unreported manual clock or power tuning. | Problem: hidden manual tuning | FPS: High impact | Visual: None | Restart: No
Default: GamersNexus used 1280 × 720 for this chart. | Why: Matches the fixed cross-device render target. | Problem: resolution mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: 1280 × 720 is a 16:9 target. | Why: Preserves the source framing. | Problem: framing or scaling mismatch | FPS: Low impact | Visual: Medium impact | Restart: No
Default: All framerate caps were disabled in the published method. | Why: Allows unrestricted measurement. | Problem: capped benchmark output | FPS: High impact | Visual: None | Restart: No
Default: Variable-refresh features were disabled for all gaming tests. | Why: Keeps comparison conditions fixed. | Problem: inconsistent synchronization state | FPS: Measurement-dependent | Visual: Low impact | Restart: No
Default: The source explicitly allowed tearing. | Why: Matches the uncapped measurement method. | Problem: synchronization mismatch | FPS: Measurement-dependent | Visual: Medium impact | Restart: No
Default: The source baseline is uncapped and allows tearing. | Why: V-Sync must remain disabled to reproduce that behavior. | Problem: hidden refresh-rate cap | FPS: High impact | Visual: Medium impact | Restart: No
Default: This API is named by the source for the game test. | Why: Matches the exact rendering path. | Problem: API mismatch | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: This named in-game preset is shown in the benchmark chart. | Why: Selecting it reproduces the complete global graphics baseline without inventing sub-values. | Problem: mismatched graphics baseline | FPS: High impact | Visual: High impact | Restart: Follow the game prompt
Default: This reconstruction method is named for the device in the source chart. | Why: Matches the tested rendering path. | Problem: reconstruction mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: This quality mode is listed by GamersNexus. | Why: Fixes the internal render target. | Problem: quality-mode mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: The source chart reports onPresent FPS. | Why: Identifies the presentation-stage stream behind the metrics. | Problem: ambiguous capture statistic | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The chart publishes all three performance statistics. | Why: Preserves the complete result instead of quoting only average FPS. | Problem: incomplete performance evidence | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The direct chart is the primary evidence artifact. | Why: Keeps the exact device row and all three values independently inspectable. | Problem: unverifiable performance claim | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: GamersNexus states the original and adapted article publication dates. | Why: Preserves the age and patch context of the evidence. | Problem: missing source date | FPS: Measurement only | Visual: None | Restart: Not applicable
1% Low
15.1 FPS
Default: The source chart labels this exact handheld configuration. | Why: Fixes the hardware represented by the result. | Problem: mismatched device target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the hardware variant represented by the source. | Why: Prevents mixing lower-spec or later-generation models. | Problem: model mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The source row identifies this processor class. | Why: Separates materially different handheld variants. | Problem: APU mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld uses this physical memory configuration. | Why: Records system memory without inventing an unreported VRAM allocation. | Problem: memory mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld is a Windows 11 device; the exact build was not published. | Why: Preserves the OS family without fabricating a version. | Problem: OS mismatch | FPS: Software-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the native panel resolution of the tested handheld. | Why: Distinguishes panel capability from the 720p render target. | Problem: display mismatch | FPS: None for the fixed test target | Visual: Indirect | Restart: Not applicable
Default: This is the panel refresh capability of the tested handheld. | Why: Records device capability without claiming an unreported selected refresh rate. | Problem: display mismatch | FPS: None for the published measurement | Visual: Indirect | Restart: Not applicable
Default: GamersNexus used this stock manufacturer profile for the chart row. | Why: Reproduces the named operating mode. | Problem: non-comparable power profile | FPS: High impact | Visual: Indirect | Restart: No
Default: The chart and manufacturer profile table define this battery power target. | Why: Preserves the exact tested power budget. | Problem: non-comparable TDP or PL limit | FPS: High impact | Visual: Indirect | Restart: No
Default: GamersNexus used battery power unless a row is explicitly marked otherwise. | Why: Keeps the handheld in the published operating state. | Problem: wall-power boost mismatch | FPS: High impact | Visual: None | Restart: No
Default: The methodology used manufacturer-defined profiles only. | Why: Avoids unreported manual clock or power tuning. | Problem: hidden manual tuning | FPS: High impact | Visual: None | Restart: No
Default: GamersNexus used 1280 × 720 for this chart. | Why: Matches the fixed cross-device render target. | Problem: resolution mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: 1280 × 720 is a 16:9 target. | Why: Preserves the source framing. | Problem: framing or scaling mismatch | FPS: Low impact | Visual: Medium impact | Restart: No
Default: All framerate caps were disabled in the published method. | Why: Allows unrestricted measurement. | Problem: capped benchmark output | FPS: High impact | Visual: None | Restart: No
Default: Variable-refresh features were disabled for all gaming tests. | Why: Keeps comparison conditions fixed. | Problem: inconsistent synchronization state | FPS: Measurement-dependent | Visual: Low impact | Restart: No
Default: The source explicitly allowed tearing. | Why: Matches the uncapped measurement method. | Problem: synchronization mismatch | FPS: Measurement-dependent | Visual: Medium impact | Restart: No
Default: The source baseline is uncapped and allows tearing. | Why: V-Sync must remain disabled to reproduce that behavior. | Problem: hidden refresh-rate cap | FPS: High impact | Visual: Medium impact | Restart: No
Default: This API is named by the source for the game test. | Why: Matches the exact rendering path. | Problem: API mismatch | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: This named in-game preset is shown in the benchmark chart. | Why: Selecting it reproduces the complete global graphics baseline without inventing sub-values. | Problem: mismatched graphics baseline | FPS: High impact | Visual: High impact | Restart: Follow the game prompt
Default: GamersNexus states that this same 720p Favor Performance benchmark runs without help from upscaling. | Why: Preserves the native render path rather than assuming FSR. | Problem: upscaler mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: The source chart reports onPresent FPS. | Why: Identifies the presentation-stage stream behind the metrics. | Problem: ambiguous capture statistic | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The chart publishes all three performance statistics. | Why: Preserves the complete result instead of quoting only average FPS. | Problem: incomplete performance evidence | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The direct chart is the primary evidence artifact. | Why: Keeps the exact device row and all three values independently inspectable. | Problem: unverifiable performance claim | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: GamersNexus states the original and adapted article publication dates. | Why: Preserves the age and patch context of the evidence. | Problem: missing source date | FPS: Measurement only | Visual: None | Restart: Not applicable
1% Low
36.5 FPS
Default: The source chart labels this exact handheld configuration. | Why: Fixes the hardware represented by the result. | Problem: mismatched device target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the hardware variant represented by the source. | Why: Prevents mixing lower-spec or later-generation models. | Problem: model mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The source row identifies this processor class. | Why: Separates materially different handheld variants. | Problem: APU mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld uses this physical memory configuration. | Why: Records system memory without inventing an unreported VRAM allocation. | Problem: memory mismatch | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The tested handheld is a Windows 11 device; the exact build was not published. | Why: Preserves the OS family without fabricating a version. | Problem: OS mismatch | FPS: Software-dependent | Visual: Indirect | Restart: Not applicable
Default: This is the native panel resolution of the tested handheld. | Why: Distinguishes panel capability from the 720p render target. | Problem: display mismatch | FPS: None for the fixed test target | Visual: Indirect | Restart: Not applicable
Default: This is the panel refresh capability of the tested handheld. | Why: Records device capability without claiming an unreported selected refresh rate. | Problem: display mismatch | FPS: None for the published measurement | Visual: Indirect | Restart: Not applicable
Default: GamersNexus used this stock manufacturer profile for the chart row. | Why: Reproduces the named operating mode. | Problem: non-comparable power profile | FPS: High impact | Visual: Indirect | Restart: No
Default: The chart and manufacturer profile table define this battery power target. | Why: Preserves the exact tested power budget. | Problem: non-comparable TDP or PL limit | FPS: High impact | Visual: Indirect | Restart: No
Default: GamersNexus used battery power unless a row is explicitly marked otherwise. | Why: Keeps the handheld in the published operating state. | Problem: wall-power boost mismatch | FPS: High impact | Visual: None | Restart: No
Default: The methodology used manufacturer-defined profiles only. | Why: Avoids unreported manual clock or power tuning. | Problem: hidden manual tuning | FPS: High impact | Visual: None | Restart: No
Default: GamersNexus used 1280 × 720 for this chart. | Why: Matches the fixed cross-device render target. | Problem: resolution mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: 1280 × 720 is a 16:9 target. | Why: Preserves the source framing. | Problem: framing or scaling mismatch | FPS: Low impact | Visual: Medium impact | Restart: No
Default: All framerate caps were disabled in the published method. | Why: Allows unrestricted measurement. | Problem: capped benchmark output | FPS: High impact | Visual: None | Restart: No
Default: Variable-refresh features were disabled for all gaming tests. | Why: Keeps comparison conditions fixed. | Problem: inconsistent synchronization state | FPS: Measurement-dependent | Visual: Low impact | Restart: No
Default: The source explicitly allowed tearing. | Why: Matches the uncapped measurement method. | Problem: synchronization mismatch | FPS: Measurement-dependent | Visual: Medium impact | Restart: No
Default: The source baseline is uncapped and allows tearing. | Why: V-Sync must remain disabled to reproduce that behavior. | Problem: hidden refresh-rate cap | FPS: High impact | Visual: Medium impact | Restart: No
Default: This API is named by the source for the game test. | Why: Matches the exact rendering path. | Problem: API mismatch | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: This named in-game preset is shown in the benchmark chart. | Why: Selecting it reproduces the complete global graphics baseline without inventing sub-values. | Problem: mismatched graphics baseline | FPS: High impact | Visual: High impact | Restart: Follow the game prompt
Default: GamersNexus states that this same 720p Favor Performance benchmark runs without help from upscaling. | Why: Preserves the native render path rather than assuming FSR. | Problem: upscaler mismatch | FPS: High impact | Visual: High impact | Restart: No
Default: The source chart reports onPresent FPS. | Why: Identifies the presentation-stage stream behind the metrics. | Problem: ambiguous capture statistic | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The chart publishes all three performance statistics. | Why: Preserves the complete result instead of quoting only average FPS. | Problem: incomplete performance evidence | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The direct chart is the primary evidence artifact. | Why: Keeps the exact device row and all three values independently inspectable. | Problem: unverifiable performance claim | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: GamersNexus states the original and adapted article publication dates. | Why: Preserves the age and patch context of the evidence. | Problem: missing source date | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The source labels this result as ROG Ally Z1X. | Why: Fixes the exact hardware represented by the chart. | Problem: mismatched device or power target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: Z1 Extreme is the processor named for this chart row. | Why: Separates this result from the lower-spec Ryzen Z1 model. | Problem: mismatched device or power target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The ROG Ally Performance profile is the source baseline for this row. | Why: Reproduces the stock profile selected by GamersNexus. | Problem: mismatched device or power target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: Stock Performance is 15W on battery in this test. | Why: Matches the exact manufacturer profile power shown in the chart. | Problem: mismatched device or power target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: GamersNexus used battery power unless a chart row says otherwise. | Why: Keeps the profile within the tested handheld operating state. | Problem: mismatched device or power target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The methodology uses manufacturer-defined profiles only. | Why: Avoids unreported manual PL or clock tuning. | Problem: mismatched device or power target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The ROG Ally ships with Windows 11; the exact tested build was not published. | Why: Preserves the tested OS family without inventing a build number. | Problem: mismatched device or power target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: 1920 × 1080 is the original ROG Ally panel resolution. | Why: Distinguishes the device panel from the lower 1280 × 720 render target. | Problem: mismatched device or power target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The original ROG Ally panel supports 120Hz. | Why: Records the exact display capability of the tested handheld without claiming a source-selected refresh rate. | Problem: mismatched device or power target | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: The original ROG Ally uses 16GB of LPDDR5-6400 memory. | Why: Records the tested memory configuration without inventing a VRAM allocation. | Problem: mismatched device memory | FPS: Hardware-dependent | Visual: Indirect | Restart: Not applicable
Default: 720p is the standardized handheld benchmark target in this chart. | Why: Matches the fixed comparison resolution used by GamersNexus. | Problem: mismatched output or synchronization behavior | FPS: Setting-dependent | Visual: Setting-dependent | Restart: No
Default: The source chart uses the 720p 16:9 target. | Why: 1280 × 720 is a 16:9 output. | Problem: mismatched output or synchronization behavior | FPS: Setting-dependent | Visual: Setting-dependent | Restart: No
Default: All framerate caps were disabled by the source methodology. | Why: Allows the benchmark to measure unrestricted output. | Problem: mismatched output or synchronization behavior | FPS: Setting-dependent | Visual: Setting-dependent | Restart: No
Default: Variable-refresh features were disabled for all gaming tests. | Why: Prevents VRR from changing the comparison conditions. | Problem: mismatched output or synchronization behavior | FPS: Setting-dependent | Visual: Setting-dependent | Restart: No
Default: The source explicitly allowed tearing. | Why: Matches the uncapped comparison method. | Problem: mismatched output or synchronization behavior | FPS: Setting-dependent | Visual: Setting-dependent | Restart: No
Default: DX12 is the API used by the source test. | Why: Matches the rendering API stated for Cyberpunk 2077 v2.12. | Problem: mismatched render configuration | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: Low is the source benchmark preset. | Why: Reproduces the named in-game preset shown in the source chart. | Problem: mismatched render configuration | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: The chart uses FSR 2.1 on the ROG Ally. | Why: Matches the reconstruction path used for AMD handhelds. | Problem: mismatched render configuration | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: Quality is the source benchmark mode. | Why: Matches the quality mode listed by GamersNexus. | Problem: mismatched render configuration | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: GamersNexus used a 66% horizontal source-resolution ratio. | Why: Records the exact FSR and XeSS normalization stated by the source. | Problem: mismatched render configuration | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: The source chart reports onPresent FPS. | Why: Identifies the presentation-stage frame stream behind the average and percentile data. | Problem: non-reproducible measurement conditions | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: The chart publishes all three performance statistics. | Why: Preserves the complete result set instead of quoting only average FPS. | Problem: non-reproducible measurement conditions | FPS: Measurement only | Visual: None | Restart: Not applicable
Default: GamersNexus standardized these chart rows to 720p. | Why: Makes the results directly comparable. | Problem: incomparable device resolution | FPS: High impact | Visual: High impact | Restart: No
Default: The source chart explicitly identifies this game build. | Why: Preserves patch-level context for the result. | Problem: patch mismatch | FPS: Software-dependent | Visual: Software-dependent | Restart: Not applicable
Default: GamersNexus standardized these chart rows to 720p. | Why: Makes the results directly comparable. | Problem: incomparable device resolution | FPS: High impact | Visual: High impact | Restart: No
Default: The source chart explicitly identifies this game build. | Why: Preserves patch-level context for the result. | Problem: patch mismatch | FPS: Software-dependent | Visual: Software-dependent | Restart: Not applicable
Default: GamersNexus standardized these chart rows to 720p. | Why: Makes the results directly comparable. | Problem: incomparable device resolution | FPS: High impact | Visual: High impact | Restart: No
Default: GamersNexus standardized these chart rows to 720p. | Why: Makes the results directly comparable. | Problem: incomparable device resolution | FPS: High impact | Visual: High impact | Restart: No
Default: GamersNexus standardized these chart rows to 720p. | Why: Makes the results directly comparable. | Problem: incomparable device resolution | FPS: High impact | Visual: High impact | Restart: No
Default: GamersNexus standardized these chart rows to 720p. | Why: Makes the results directly comparable. | Problem: incomparable device resolution | FPS: High impact | Visual: High impact | Restart: No
Default: GamersNexus standardized these chart rows to 720p. | Why: Makes the results directly comparable. | Problem: incomparable device resolution | FPS: High impact | Visual: High impact | Restart: No
Default: GamersNexus standardized these chart rows to 720p. | Why: Makes the results directly comparable. | Problem: incomparable device resolution | FPS: High impact | Visual: High impact | Restart: No
Default: GamersNexus standardized these chart rows to 720p. | Why: Makes the results directly comparable. | Problem: incomparable device resolution | FPS: High impact | Visual: High impact | Restart: No
Default: GamersNexus standardized these chart rows to 720p. | Why: Makes the results directly comparable. | Problem: incomparable device resolution | FPS: High impact | Visual: High impact | Restart: No
Default: The chart baseline is uncapped with tearing allowed. | Why: V-Sync must remain disabled for the source method to allow tearing and uncapped output. | Problem: mismatched output or synchronization behavior | FPS: Setting-dependent | Visual: Setting-dependent | Restart: No
Default: GamersNexus standardized handheld game tests to 1280 × 720. | Why: Makes the cross-device chart directly comparable. | Problem: mismatched output or synchronization behavior | FPS: Setting-dependent | Visual: Setting-dependent | Restart: No
Default: GamersNexus used a 66% vertical source-resolution ratio. | Why: Records the exact FSR and XeSS normalization stated by the source. | Problem: mismatched render configuration | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt
Default: The published chart is explicitly for Cyberpunk 2077 v2.12. | Why: Preserves the exact tested build identified by the source. | Problem: mismatched render configuration | FPS: Setting-dependent | Visual: Setting-dependent | Restart: Follow the game prompt