Explicitly mention how depth/alpha/stencil values get used#800
Merged
toji merged 1 commit intoimmersive-web:masterfrom Aug 13, 2019
Merged
Explicitly mention how depth/alpha/stencil values get used#800toji merged 1 commit intoimmersive-web:masterfrom
toji merged 1 commit intoimmersive-web:masterfrom
Conversation
Member
|
Perfect, thank you! |
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
2 participants
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.
Fixes #671
There's actually no direct algorithm for WebGL framebuffers that can handle these, typically you control these via
framebufferRenderbufferandframebufferTexture2Dwhich our code forbids.Instead, I looked at how the primary drawing buffer handles this in WebGL and updated the opaque framebuffer text to work with that, since its purpose is to match the drawing buffer anyway.
r? @toji