FIELD MANUAL / 07
Core scheduling & exclusivity
Core selection now has its own page. Start with all cores and restrict the game only after understanding CPU topology and workload.
- Where to find it
- Advanced → Core scheduling; also available in game profiles
- When it applies / restoration
- Save the plan explicitly. It applies next session and original affinity is restored on exit where possible.
Step by step
- Read the CPU name, physical/logical core counts and topology notices. Resolve conflicts before selecting cores; do not copy another machine’s CPU numbers.
- Use all cores, invert, SMT-off or CCD shortcuts to select at least two valid logical CPUs.
- Enable exclusivity only when needed and read the spare-core requirements. Handheld does not offer exclusivity.
- Save and inspect the effective state next session. Follow notices for failed application, pending recovery or topology changes.
Working alongside other scheduling tools
Since 2.2.2.2, changes made by another process are kept by default and repeated placement stops for that session. The separate “Correct immediately when another process changes affinity” option is off by default.
Exclusivity has limits
Isolation keeps eligible ordinary background processes away from a range; it cannot exclude every system interrupt. Select whole physical cores and leave at least two full physical cores outside isolation. Unsupported topologies are not handled with partial masks.
Reverting a regression
Return to all cores or disable exclusivity, save and start a new session for comparison. Fewer cores do not guarantee lower latency; some games need more parallelism. Preserve the app and logs if recovery remains unconfirmed.
Core selection, exclusivity and hard locking
Core selection changes the game’s allowed CPU range. Exclusivity steers ordinary background work away from whole selected physical cores while game priority is active. Hard background-affinity locking is a separate, default-off control. Baseline suppression preserves original affinity rather than packing all background work onto one E-core.
Archived 2.2.2.3 instructions; source references are pinned to the public v2.2.2.3 tag.