Proper Logging and Issue hunting. #1147

Closed
opened 2026-11-09 14:42:24 +00:00 by SuperSenad · 1 comment
SuperSenad commented 2026-11-09 14:42:24 +00:00 (Migrated from github.com)

The idea

Add Logging, System Call Tracing, Memory Pool Logging, and Many more logging options so that you can return to whatever AI you're using with Data from the game and hunt very specific resources to improve performance and fix texture issues and object placement issues more rapidly. They should also be available to the community so that they can provide logged runs themselves and return here with that data for fruitful development. Your agent, or yourselve(s) could sort through those logs quickly and implement real fixes significantly faster without needing to consistently do incremental updates.

I don't want to self advertise, but I've done something like that for a Tears of The Kingdom Recomp I worked on and in a week went from 30fps in the most demanding areas to 72

Anything else

If anything comes across as rude or ungrateful that is not the goal. You guys took on the task of working on this recomp and it can be extremely teidious work. I'm grateful.

### The idea Add Logging, System Call Tracing, Memory Pool Logging, and Many more logging options so that you can return to whatever AI you're using with Data from the game and hunt very specific resources to improve performance and fix texture issues and object placement issues more rapidly. They should also be available to the community so that they can provide logged runs themselves and return here with that data for fruitful development. Your agent, or yourselve(s) could sort through those logs quickly and implement real fixes significantly faster without needing to consistently do incremental updates. I don't want to self advertise, but I've done something like that for a Tears of The Kingdom Recomp I worked on and in a week went from 30fps in the most demanding areas to 72 ### Anything else If anything comes across as rude or ungrateful that is not the goal. You guys took on the task of working on this recomp and it can be extremely teidious work. I'm grateful.
NotRexed commented 2026-11-09 14:45:39 +00:00 (Migrated from github.com)

Thanks for the idea, no offence taken! Hookshot already logs quite a lot (hookshot_log.txt has per-frame GPU, memory, texture and pipeline stats, and there are switches such as RX_VK_DRAW_STATS and RX_VK_CHECKPOINTS for deeper dives), but more targeted tracing is a fair request. Feature requests are collected in #1007, where this is now listed; closing this in favour of it.

Thanks for the idea, no offence taken! Hookshot already logs quite a lot (hookshot_log.txt has per-frame GPU, memory, texture and pipeline stats, and there are switches such as RX_VK_DRAW_STATS and RX_VK_CHECKPOINTS for deeper dives), but more targeted tracing is a fair request. Feature requests are collected in #1007, where this is now listed; closing this in favour of it.
Commenting is not possible because the repository is archived.
No milestone
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Hookshot#1147
No description provided.