Proper Logging and Issue hunting. #1147
Labels
No labels
accessibility
autorelease: pending
autorelease: tagged
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
testing wanted
wontfix
No milestone
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot#1147
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
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.