Is this change something expected? What could be affecting this change and, in particular, which parameters could I tweak to try to get the same looks with 135 as with 134? (assuming it is possible to do so)
Since it is not a reproducible case, any pointer/idea would be appreciated, even if it is a miss. I had a look at the changelog, but did not find anything I could relate to this change in looks (with my limited Three.js knowledge).
We had to revert the usage of SRGB8_ALPHA8 with r135 which is a WebGL 2 specific feature for decoding sRGB textures to linear space via WebGL. We introduced the feature for better rendering quality in r133 however the decode on Windows browsers took way more time than before. The performance regression was actually a more critical issue than the rendering problem.
When the performance issue is solved, we are going to add SRGB8_ALPHA8 back.