FIELD MANUAL / 15
Audit, reports & logs
Use evidence before changing settings. Session reports describe play, System audit checks the machine, and logs record actions and failures.
- Where to find it
- Overview → Previous session / Diagnostic summary; Reports / System audit; Logs
- When it applies / restoration
- Audit collection is read-only. An explicit repair action changes the selected configuration.
Step by step
- Review the target, mode and limits for the previous session and confirm the measurements belong to the intended game.
- Run System audit and review write capability, local measurements, persistent settings and conclusions.
- Consider each evidence level; an explanation of a mechanism is not a measured gain on your own PC.
- Filter warnings or errors in Logs and double-click to copy an entry. Share a reviewed diagnostic summary and reproduction steps when needed.
Audit and manual repairs
Audit can report power/thermal limits, interrupt sources and abnormal scheduling or input-queue settings. Available repairs depend on what is detected; the number of findings is not fixed. Precise measurements take longer than a basic check.
Log levels and diagnostic summaries
Version 2.2.2.2 fixes renderer observations being mislabeled as errors. Low sampling or a non-foreground game is not automatically a failure. The 2.2.2.3 summary includes version, game, relevant settings and recent logs; review it before sharing.
When an option disables itself
Rejected writes, mismatched readback or unsuccessful validation can trigger rollback and stop retries. Re-enabling does not fix the underlying cause. Disabling logging stops new entries; clearing the current log does not delete all archives.
Archived 2.2.2.3 instructions; source references are pinned to the public v2.2.2.3 tag.