feat(gui): expose -texchart, and release 0.6.0 - #3
Merged
Merged
Conversation
A CSG flag nobody can reach from the app is a flag nobody uses, so the texture cost report gets a toggle under CSG like the merge options did. The help text is aimed at the decision, not the mechanism. What matters is the "oversampled" column and what to do at each value: 4x or more, the texture can lose half its resolution in each axis and still have a pixel per pixel on screen; around 1x, leave it alone; below 1x it tiles across a large surface and halving it will show. It also explains why that column exists, because reading the byte column on its own suggests savings that turn out not to be there. Version goes to 0.6.0 rather than 0.5.1: this release carries a new feature, not only the BEVELHINT fix.
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
1 participant
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.
-texchartlanded in CSG in #2 but there is no way to reach it from the app, so it gets a toggle under CSG alongside the merge options.The help text is aimed at the decision rather than the mechanism. The column that matters is
oversampled, and what to do at each value:It also explains why that column exists, because reading the byte column alone suggests savings that are not there: on
zm_aztecathe naive reading claims most of a 2.2 MB lump is recoverable, and the real answer is that nothing on that map is oversampled.Version
0.6.0, not 0.5.1. The release carries a new feature, not only the
BEVELHINTfix.Checks
cargo build --releaseclean,cargo test --release21 passed / 0 failed, including a new test that the flag is emitted on its own and does not drag the merge options along with it.After this merges the tag can go up and the 0.5.0 auto-update will distribute it.