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

Add option to skip the clearing of textures #298

Closed
cabanier opened this issue Jan 19, 2023 · 4 comments · Fixed by #301
Closed

Add option to skip the clearing of textures #298

cabanier opened this issue Jan 19, 2023 · 4 comments · Fixed by #301

Comments

@cabanier
Copy link
Member

The WebXR layers spec defines that the textures that are returned from the binding are always cleared to opaque black.
This feature is hard to implement without incurring GPU overhead especially when dealing with multiple layers.

Could we introduce an option to skip this behavior and leave it up to the experience to clear its buffers?

/agenda Add option to skip the clearing of textures

@DRx3D
Copy link

DRx3D commented Feb 7, 2023

There was a request that it might be better to name the flag so that the default (FALSE) implies what is desired. The initial proposal was for 'clearOnAccess' with the default value of TRUE. A field with a default of FALSE could be called 'alwaysClear'.

@AdaRoseCannon
Copy link
Member

Removing label, because it was discussed at the last meeting, if this is in error or more discussion is needed please reuse '/agenda'

@cabanier
Copy link
Member Author

cabanier commented Mar 6, 2023

@toji I looked at various idl interfaces in chromium and there are many that initialize dictionary values to true.
I prefer to keep it as "true" because it's less confusing. (False would require a double negative)

@cabanier
Copy link
Member Author

cabanier commented Mar 6, 2023

/agenda can we keep clearOnAccess?

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 a pull request may close this issue.

3 participants