Tested settings.Zero guesswork.

GamersNexus tested Resident Evil 4 on the MSI Claw A1M Core Ultra 7 155H in its stock Super Battery profile on battery (DC PL1 20W / PL2 20W). 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 49.8 FPS average, a 27.5 FPS 1% low and a 20.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.

GamersNexus tested Resident Evil 4 on the MSI Claw A1M Core Ultra 7 155H in its stock Balanced profile on battery (DC PL1 30W / PL2 30W). 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 59.3 FPS average, a 28.8 FPS 1% low and a 14.5 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.

GamersNexus tested Resident Evil 4 on the MSI Claw A1M Core Ultra 7 155H in its stock Performance (Extreme Performance) profile on battery (DC PL1 35W / PL2 35W). 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 59.0 FPS average, a 21.9 FPS 1% low and a 5.2 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.

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.

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.

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.