FIELD MANUAL / 05 / UI 3.3.1.2
How policies execute and restore
Saved choices, target identity and runtime conditions govern execution.
Step by step
- Choose performance and background controls in Tuning, and configure CPU ranges, render scheduling and game resource priority in each game’s Advanced tuning. Detection applies effective settings when their conditions are met.
- Distinguish a selected switch from a successful action. Target identity, privileges, OS or driver support, whitelist rules and failure isolation govern writes.
- Session controls with original-value records are verified and restored on exit. Initial acquisition, write failures and restoration retries have execution limits; exhaustion retains records and ownership and stops active attempts for that phase.
Overview and action state
Overview continues showing live CPU, GPU and memory readings during games and stops reading when hidden or left. Suppressed processes and services are counted separately. Frame-rate monitoring, OSD and game run reports remain unavailable.
Recovery has a defined scope
Persistent system settings use their own restore controls. Cleaned caches and deleted files cannot be reconstructed by restoring configuration.
Earlier demo screenshots for 3.3.0.8 use fictional games and synthetic readings. Current controls follow the 3.3.1.2 manual and your hardware support. Follow actual support status on your machine.
Continue reading → Tuning panel and Laboratory