-
-
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
GLTFLoader: Regressions in PBR rendering with r138 #23627
Comments
You've upgraded from r136 to r138. |
I should probably just bisect three... |
Okay, git bisect pointed to the #23420 as what broke khronos-TextureSettingsTest, but I haven't looked into why yet. @takahirox Any thoughts? I'm going to check the other one now. |
I'm done for today; if no one has looked into these tomorrow I'll start debugging. |
The removal of the inline sRGB decode was done under the assumption the color space for the texture is properly defined. It looks like this is not the case. |
About the failing texture clamp/wrap/repeat test, I've noticed that if the internal cache here is commented out... three.js/examples/jsm/loaders/GLTFLoader.js Lines 2905 to 2917 in c5e0fdf
... the test cases all pass. So I think the changes by @takahirox in the PR are correct, but there's something about sharing a |
Actually, |
Done! |
@elalish |
I've merged r138.3 and it's looking good 👍 |
Describe the bug
I've got two fidelity test failures on upgrading model-viewer to r138.2: See the .pngs I uploaded in the PR for how the renders changed. The SpecGloss extension has lightened considerably, and we're now failing most of the khronos-TextureSettingsTest. @donmccurdy @Mugen87 Any thoughts on what PRs might have affected this? I'm happy to help, but hoping you might have a pointer first.
The text was updated successfully, but these errors were encountered: