-
-
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
WebGPURenderer produces washed out colours compared to WebGL #26233
Comments
At first sight it looks like the color space for the video texture isn't honored. |
ok a color space issue I am seeing it on other projects. I can help debug it perhaps. So its on any texture setting or the renderer as the renderer as colorSpace and outsideColorSpace. |
Both of these are needed. if outputColorSpace is not set it has the problem.
|
update: I'm experiencing high cpu usage with video textures and will make a seperate ticket. I have 20% usage with the example below. In an external project adding the colorSpace property helped but not for these examples I updated. Its the current builds. https://danrossi.github.io/three-webgpu-renderer/tests/webgpu_video_panorama_equirectangular.html |
The Linear color space stops the problem but only when configuring outputColorSpace. changing the texture colorspace didn't resolve it. |
This is possibly replated and "washed out" is gamma correction is needed when srb is used ? https://discourse.threejs.org/t/updates-to-color-management-in-three-js-r152/50791/53 |
We're using |
I get carried away and spam sorry guys. It's something to do with video textures but I saw it on images loaded by the TextureLoader also. I can make an example for that. Thanks. I am experiencing performance problems in chrome with video textures and webgpu. I can't determine whos problem it is to report. Should I try GPUExternalTexture ? |
I suggest you wait until this particular issue is fixed. It's about wrong/missing color space conversion. The performance issues are something that I would investigate separately after the colors are right. If there are performance issues in the WebGPU implementation, we have to delegate these to the Chromium team in any event. But first, we should make sure the visual results on our side are correct. |
OK I found a possible AB test this doesn't have color or cpu resource issues but it's a small canvas. So I will wait to report my findings with chrome. https://webgpu.github.io/webgpu-samples/samples/videoUploading |
Confirmed it is working. But I need to figure out how to report the performance problem with videotextures with Chrome. Do I add it here or with chrome ? |
I think it's okay to open an issue here first. When we are sure it's not three.js related, we can delegate the issue to the Chromium bug tracker. |
Oh, you already did^^: #26266 |
Description
I've integrated a bundle of the WebGPURenderer to begin testing and I am seeing a difference in the colors produced compared to WebGLRenderer. They are highly exposed. I'm not sure if a property is needed for it.
The WebXR manager is also not available yet and might need integration.
Reproduction steps
live examples
Code
Live example
Screenshots
No response
Version
153dev
Device
No response
Browser
No response
OS
No response
The text was updated successfully, but these errors were encountered: