-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Keep float values when saving screenshots to .exr or .hdr #25657
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
alice-i-cecile
merged 3 commits into
bevyengine:main
from
stuartparmenter:hdr-wave3-float-screenshots
Sep 8, 2026
+135
−4
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Explain to me what's going on here too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was found due to a panic during testing, and I would have spent a while trying to figure it out w/o Claude.
Basically The .hdr format stores each pixel as three 8-bit color values plus one shared 8-bit exponent, so the range it can hold is limited.
image's encoder works out that exponent withfloor(log2(max)) + 1as ani32and then stores it as(exp + 128) as u8, and it never checks that the value fits. If a channel is infinite, which is easy to get in a float render target, log2 is infinite, the cast to i32 saturates, and the + 1 overflows. If a channel is2^127or bigger, or smaller than2^-128, the exponent byte wraps around and the pixel decodes to garbage. So before encoding we clamp every channel and set every NaN and subnormal value to zero.I'll update the comment to be more clear.
I'll see if I can find an upstream issue and file on if not.