ranbuch
1
I’m trying to change the renderer.toneMappingExposure but it doesn’t seems to work.
Here is an example of r112 where it works fine.
Update to r120 by changing package.json:
"three": "0.112.0" => "three": "0.120.0"
After the update it doesn’t seems to work.
Should I needsUpdate = true something?
Thanks.
Mugen87
2
Since r116, the default value of WebGLRenderer.toneMapping is NoToneMapping . This is also noted in the migration guide: https://github.com/mrdoob/three.js/wiki/Migration-Guide#r115--r116
So setting WebGLRenderer.toneMapping to WebGLRenderer.LinearToneMapping should restore the previous behavior.
1 Like
ranbuch
3
Works well, thanks.
What is the reason for this change? Does it has an effect on performance?
Mugen87
4
Check out the following discussion:
1 Like