-
-
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
WebGLRenderer: background is not set to transparent on 0.137.0 version #23495
Comments
Instead of creating the this.renderer = new THREE.WebGLRenderer({
canvas: canvas as HTMLCanvasElement,
antialias: true,
alpha: true
}); BTW: AFAIK, In three.js/src/renderers/WebGLRenderer.js Line 62 in 766b95b
And this value leads to a wrong alpha clear value in
|
@mrdoob We could fix this issue on our side however it means we have to call |
Thanks for the reply! Moving the params out of context fixes the issue. |
That sounds good 👍 |
@japie1235813 The PR you have filed at this.renderer = new THREE.WebGLRenderer({
canvas: canvas as HTMLCanvasElement,
antialias: true,
alpha: true
}); /cc @bmd3k |
so after #23504
or
|
Correct. I recommend the first one though. Creating a rendering context manually should only be done if there is a compelling reason. |
Describe the bug
We upgrades the threejs version recently from
0.131.3
to0.137.0
tensorflow/tensorboard@420916a. It breaks our repo by not setting the background to black. (see screenshots before)After debugging we found the cause is from the background is not set to transparent by "alpha: true". (which means, we can fix our issue by adding
renderer.setClearColor(0x000000, 0);
)Is there any changes from the version that makes this stop working?
To Reproduce
You can reproduce the issue by clone our repo. Checkout to the upgrade comment and run TensorBoard (https://github.com/tensorflow/tensorboard).
However it requires some demo data to run the card. Let me know how I can assist.
Code
code point
Screenshots
before (0.131.3)
after (0.137.0)
Platform:
The text was updated successfully, but these errors were encountered: