Skip to content
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

Clarify GLES/WebGL difference with uninitialized compressed textures. #3688

Merged

Conversation

kenrussell
Copy link
Member

Fixes #3686.

@kenrussell
Copy link
Member Author

@juj any feedback welcome. This seemed most appropriate to add to the WebGL 2.0 spec because this has always been disallowed in WebGL 1.0.

@lexaknyazev
Copy link
Member

Using texStorage is not a functional replacement because it would prevent potential texture redefinitions. Assuming that we cannot retroactively allow null, the only option is to use new Uint8Array(n) with an appropriate size.

@kenrussell
Copy link
Member Author

Fair point; I've rewritten this paragraph. Would you please take another look?

Copy link
Contributor

@juj juj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for the update!

@kenrussell kenrussell merged commit de50dfc into KhronosGroup:main Sep 5, 2024
2 checks passed
@kenrussell kenrussell deleted the clarify-uninit-compressed-tex branch September 5, 2024 17:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

There is no way to initialize a compressed 2D or 3D texture with uninitialized contents
4 participants