diff --git a/.github/ISSUE_TEMPLATE/1-crash.yml b/.github/ISSUE_TEMPLATE/1-crash.yml index 05366944..14055cc4 100644 --- a/.github/ISSUE_TEMPLATE/1-crash.yml +++ b/.github/ISSUE_TEMPLATE/1-crash.yml @@ -77,7 +77,6 @@ body: - The log of the run that crashed is `logs\totk.log` in the folder of `totk.exe` (F1, Advanced tab, Open log folder). Copy it before you start the game again: the next start renames it to `totk.1.log`, and after five starts it is gone. - Attach the whole file. Do not cut or edit it: the crash report is at the end, the GPU and driver lines are at the start. - The log says `device lost` or `VK_ERROR_DEVICE_LOST` and the GPU is an NVIDIA one: set GPU pass marks to On (F1, Advanced tab, Diagnostics), restart the game, make it crash again and attach that log. The `vk: pass marks` lines then name what the GPU was drawing. - - The crash happens at the same point every time: also attach the input recording and the save described in the Other bug template. - type: textarea id: log attributes: @@ -85,3 +84,17 @@ body: description: Drag totk.log into this field. validations: required: true + - type: markdown + attributes: + value: | + ### Save and input recording + + When the crash comes back at one place in the game (an area, a shrine, a cutscene, a quest step), the save that gets there lets us crash it on our machine. + + 1. Zip the `profile` folder next to `totk.exe` and attach it. Say which slot you load, or that you use the autosave. + 2. If it takes more than walking a few steps from the save: turn on Input recording (F1, Advanced tab, Diagnostics), restart the game, load the save, make it crash, and attach `input-record.txt` from the logs folder together with the `totk.log` of that run. + - type: textarea + id: save + attributes: + label: Save and input recording + description: Drag the zipped profile folder and input-record.txt into this field, when the crash comes back at one place.