FIELD MANUAL / 04 / UI 3.3.1.2
Per-game tuning and CPU scheduling
Open a game card, then use its dedicated configuration dialog.
Step by step
- Open Advanced tuning from Library. Controls are grouped under Scheduling & priority and Other. Game CPU range and render thread scheduling have separate switches and Adjust entries.
- Choose logical CPUs and isolation under Game core range, then click Save for the next game launch. Reload saved restores the stored selection; leaving does not save. The separate Advanced tuning switch controls activation.
- Check P/E cores, CCDs, cache domains and SMT using this PC’s topology. Isolation must leave whole physical cores for the system. Selecting all CPUs without isolation adds no range constraint and retains existing game limits and restoration obligations.
- Render thread scheduling is on by default: games you have not turned off and that have no other saved strategy run Game priority. Turning it on manually warns that frame rate or smoothness may worsen. Choose Game priority (recommended), Render priority, Dedicated rendering, Multicore coordination, Dependency coordination or Enhanced dedicated rendering; existing selections stay. Every strategy except Enhanced dedicated rendering runs the game process at High, restored at game end.
- Every strategy except Dependency coordination and Game priority offers optional Clear core, moving covered game threads off critical cores. Automatic placement stays within legal game ranges and skips threads that cannot be narrowed. Pinning and Clear core do not provide system-wide exclusivity.
- Save GPU and disk I/O resource priority in the same dialog for the next session; it requires render thread scheduling. Game priority already includes both, without a separate switch. With scheduling on, the game is also held at high-performance QoS during matches. Game memory-page priority and high-performance GPU preselection are removed. Existing Windows GPU preferences remain editable in system Graphics settings.
- Back in the game’s Advanced tuning dialog, the Anti-cheat suppression switch is on by default: verified ACE is governed as ordinary background, and turning it off keeps ACE protected during that game’s matches. EAC and BattlEye are protected without suppression.
Keep changes comparable
Change one control at a time and compare the same scene. ReBAR and hard affinity do not suit every game; disable and reassess after problems.
Game priority scope
Only Game priority sets the whole game process to High and pins and prioritizes the identified render thread; an existing Realtime category is retained. Process priority is independent of GPU/disk switches. Other apps may slow down under CPU saturation. Disabling, game exit or a strategy change restores owned values and preserves later external writes.
Saving, verification and restoration
Saving the strategy and resource priority together does not change activation. Disabling immediately revokes old writes and restores owned changes. Role discovery, initial acquisition and restoration have bounded budgets. Acquired affinity, thread priority and existing ideal-processor targets are continually verified; failures back off to at most 30 seconds with rate-limited logs. Unknown identity or legal ranges pause affected writes, and toggling does not refill spent attempts.
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 → How policies execute and restore