Record the draw replay on three replay workers by default, and start the draft notes after 0.9.0.

replay_workers = 0 records everything on the submitting thread, as before.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-12 06:20:05 -05:00
parent 6ccd1e224d
commit 2f39b27fb6
4 changed files with 18 additions and 6 deletions

View File

@@ -66,10 +66,11 @@
# of latency, and can show a dark or flickering frame now and then: the other thread reads vertex and buffer memory
# the game has sometimes rewritten by then.
# replay_async = 0
# EXPERIMENTAL, work in progress. Record the draws of a submission on replay worker threads, 0 to 16. Default: 0, the
# replay records everything on one thread. With 1 a worker records each long run of draws while the submitting thread
# waits for it: no faster yet, it checks that the pictures stay the same before several workers record at once.
# replay_workers = 0
# Record the large groups of draws of a submission on this many replay worker threads beside the submitting one, 0 to
# 16. Default: 3 (Hyrule Field standing on an RX 7900 XT: 51.7 instead of 43.6 fps). 0: the replay records everything
# on one thread, as before; try it if a picture looks wrong. With 1 a worker records each long run of draws while the
# submitting thread waits for it: no faster, it checks that the pictures stay the same.
# replay_workers = 3
# EXPERIMENTAL, THE GAME CRASHES WITH 1. 1 lifts the virtual core gate: guest threads run without the console's limit
# of one thread per core, and the game keeps per-core data without locks. With 1 the game crashes or hangs,
# usually at start. Keep 0 to play.