Repository navigation
docs: tested configurations, the runs behind the status table - #1723
Merged
Merged
Conversation
docs/tested-configurations.md keeps one row per test run: build (from the log's first line), OS and desktop, GPU and driver, CPU and RAM, the settings that matter, where in the game, and what was measured; plus what is not covered yet. Seeded with the Linux + RTX 4070 Ti runs made while testing NotRexed#1308, NotRexed#1305, NotRexed#1459, NotRexed#1462 and HDR. CONTRIBUTING's "Test on other hardware" points testers at it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 10, 2026
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.
What
The README's status table says what works where, but not which runs back it up. This adds
docs/tested-configurations.md: one row per test run, with the build (hookshot vX.Y.Z-N-gHASHfrom the log's first line), OS and desktop, GPU and driver, CPU and RAM, the settings that matter, where in the game, and what was measured (fps fromhookshot_log.txtat a named spot). It also has a "not covered yet" list, so the next tester can see what is still open. CONTRIBUTING's "Test on other hardware" row now points testers at it and asks them to add a row.It is seeded with the runs I made on Linux (Ubuntu 26.04, KDE Plasma 6.6 Wayland, RTX 4070 Ti on 595.99, Ryzen 7 9800X3D) while testing #1308, #1305, #1459, #1462 and HDR. Each row only states what was measured, with the commit it ran on.
Docs only.
🤖 Generated with Claude Code