-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
1.3.0 Hellow WebVR screenshot looks washed out #5014
Comments
Wild guess, from reading 4915 and 4917, is it a question of whether colorManagement is enabled? The Hello WebVR example doesn't use colorManagement, whereas maybe the cases being looked at in 4915 and 4917 did? |
Here's a glitch with a totally unmodified "Hello WebVR" except for the addition of the "screenshot" attribute on the scene. Ctrl-Alt-S on this will reproduce the washed out screenshot. |
Thanks for raising @diarmidmackenzie . I just took a look at the commit (it's been a while). I agree with your analysis.
|
Yeah we should match color management on screen and screenshot component. Thanks |
Is there an easy fix for this in the meantime? |
I tried the code from @diarmidmackenzie and that fixed the problem for me: <script>
AFRAME.components.screenshot.Component.prototype.getRenderTarget = function (width, height) {
return new THREE.WebGLRenderTarget(width, height, {
minFilter: THREE.LinearFilter,
magFilter: THREE.LinearFilter,
wrapS: THREE.ClampToEdgeWrapping,
wrapT: THREE.ClampToEdgeWrapping,
format: THREE.RGBAFormat,
type: THREE.UnsignedByteType
});
}
</script> I was using the chromakey component and screenshots looked be very washed out, now screenshots looks fine. |
Any PRs to fix this super welcome |
I'll have a go. |
fixed by #5157 |
Description:
This is what a screenshot of the Hello Web VR app (Ctrl-Alt-S) used to look like
This is what it looks like in 1.3.0 - to my eye this looks far too washed out.
This glitch uses a small JS script to run a version of 1.3.0 with the fix for PR4822 reverted, and gives the same screenshot output as 1.2.0 did.
I understand that PR4822 was added because screenshots were coming out too dark in some circumstances, but it seems that the way it's been fixed has just traded one problem for another.
I don't have any expertise around the various WebGLRenderTarget settings, so no idea what the "correct" fix is - but it looks like we still have issues here in getting the screenshot colors right in all cicumstances.
The text was updated successfully, but these errors were encountered: