-
-
Notifications
You must be signed in to change notification settings - Fork 382
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
Fix large scalar values #2915
Fix large scalar values #2915
Conversation
But will get overwritten to halfFloat if the |
Yes, preferSizeOverAccuracy should prefer halfFloat. |
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.
LGTM
Scalars that cannot be represented accurately with half-float should be rendered with a full float format. useHalfFloat tells use whether the scalars can be accurately represented in half-float. OES_texture_float_linear is needed to filter 32 bit internal formats.
87eaed7
to
2dca152
Compare
Co-authored-by: Scott Wittenburg <[email protected]>
This keeps the ImageMapper in-line with the VolumeMapper.
2dca152
to
ce2b9bf
Compare
Rebased and updated the tests to use |
🎉 This PR is included in version 29.5.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Context
Large scalar values cannot be accurately represented in half float format. When large scalar values are detected, switch to 32-bit floats.
Additionally enables the
OES_texture_float_linear
extension for 32-bit texture filtering.Results
Changes
PR and Code Checklist
npm run reformat
to have correctly formatted codeTesting