-
-
Notifications
You must be signed in to change notification settings - Fork 35.5k
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
problem with CustomBlending #11280
Comments
I formatted your post for clarity. Can you please make necessary corrections to your post and provide further detail? |
sorry for my poor english, well, i ment this post have enogh details. this code fragment, which need fix. when i give CustomBlending parameter, this code first set NormalBlending, then do some check: |
@Dark-Energy Why not using |
@Dark-Energy So we may better understand, can you please edit your original post and show how you think the code should be written? No code fragments, please. |
how can i explain the code shoud be written with no code fragments? There are two blocks of if's, first of them check and apply blending mode. It ended with 'else' block which enabled normalblending. State of WebGL is changed. Second if block check and apply custom modes. It checks state of srcColor & srcAlpha function changed and assign new values to local variables. And... this block may run only once, then it reckons states still unchanged. But state of blending may be changed in other places. |
@sasha240100 this way is acceptable. |
@mrdoob I think the OP is suggesting a one-line change in the
With all due respect, that change seems a bit hacky to me. I think the entire code block should not be executed if |
@WestLangley sounds hacky indeed. |
@mrdoob I think something needs to be done. Maybe this one-line change is adequate to prevent the code block from being called when
|
That looks good. |
Function setBlending in
WebGLState
incrorrectly processcustomBlending
:Three.js version
Browser
OS
Hardware Requirements (graphics card, VR Device, ...)
The text was updated successfully, but these errors were encountered: