Repository navigation
Tools: the in-game run script and the offline create preflight (config-driven) - #158
Merged
Merged
Conversation
…g-driven tools/ingame: one in-game run of a candidate build with evidence and a byte-for-byte restore (run.py), as used for Model L in two games (#89). Every path comes from a game config (examples/*.json, placeholders only) or from arguments; nothing is specific to one PC. - run.py: preflight, prepare (manifest, backups, aside / hash-only files, the launcher's update, the model choice in runtime_options and OptiScaler's UpscalerIndex, the model in the game's data folder, settings), launch (the GPU flag per game run, released by game_hold.py in finally), hold, shot, collect (our logs only, proof.json, launch trace counts), restore (verified against the manifest), all --dry-run. - offline_create.py: the harness create test of Model L on D3D12 before any game run, and the L / M synthetic timing; an optional GPU-slot wrapper after "--". - make_record.py: the timing record from the runtime's own timing lines, scenes from a JSON file. - settings_edit.py: graphics settings backup / stage / restore (ini and Cyberpunk 2077's UserSettings.json). - The helpers: game_manifest, game_backup, game_restore, game_hold, aside, check_record, set_upscaler_index, vram_log. Refs #89 Signed-off-by: phantoslayer21 <156617979+phantoslayer21@users.noreply.github.com>
phantoslayer21
marked this pull request as ready for review
November 14, 2026 08:18
… trace per choice - run.py: runtime_options_extra in the config and --extra on prepare / use-m / use-l (e.g. l_post=own, then --extra '' for the default post in the same session); set_options replaces the items it added before (timing, launch trace, the previous extra) instead of appending them again. - run.py: each model choice writes its own launch-trace-<time>.txt; collect summarises every trace on its own. - offline_create.py: --extra adds runtime options to Model L's runs. Used for the Model L own-reconstruction game run (#162). Refs #89 Signed-off-by: phantoslayer21 <156617979+phantoslayer21@users.noreply.github.com>
Signed-off-by: phantoslayer21 <156617979+phantoslayer21@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #89
tools/ingame/: the in-game run of a candidate build used for Model L in Cyberpunk 2077 and Resident Evil Requiem, generalised so no PC-specific path is in the repo. Every path comes from a game config (examples/*.json, placeholders only; an unfilled<placeholder>is an error) or from arguments.run.py --config <game>.json: preflight / prepare / launch / hold / shot / collect / restore /all --dry-run. The GPU flag is taken per game run and released bygame_hold.pyinfinally; the model goes into the game's data folder and stays until the game exits; restore is verified against the manifest.offline_create.py: the harness create test (model=L, executor=dx12, launch trace) before any game run, and the L / M synthetic timing; GPU-slot wrapper after--.make_record.py: the timing record from the runtime's own timing lines; scenes from JSON.settings_edit.pyand the helpers (manifest, backup, restore, hold, aside, record check, UpscalerIndex, VRAM log).Checked:
all --dry-runagainst a real Cyberpunk 2077 install passes;collect --logson the earlier Model L run's logs gives verdict PASS;make_record.pyreproduces the earlier Cyberpunk record's scene numbers exactly. No runtime or build change (Model M untouched).