The shadow decreases and the render effect changes greatly!

[chloe]

Hello, may I ask a question? When using “MeshStandardMaterial” in three.js to render .stl model, the rendering effect of different versions of the same code is quite different, and the black shadow of the edge outline of the model in the new version 0.157.0 is disappeared. The overall shadow of the model is weaker, and the rendering effect of the previous 147 version is more realistic. Is there any way to enhance the shadow of the model in the new version, like the effect of 147, or are there any parameters that can be controlled and adjusted? Thank you for your answers!

const loader = new THREE.STLLoader();
loader.load(‘monkey.stl’, geometry => {
const material = new THREE.MeshStandardMaterial({
color: 0xfff4c2,
metalness: 0.0,
roughness: 1,
});

[mjurczyk]

There’s quite a bit happening in terms of colors / lights between r147 and r157

Updates to Color Management in three.js r152

The upcoming release r152 will contain changes affecting color and lighting. These updates enable a “linear workflow” by default, for better image quality in both physically-based and non-physically-based scenes. By “linear workflow”, we mean that any sRGB input colors (as found in most textures, color pickers, CSS, and HTML) are converted from sRGB to a linear working color space for rendering, and the rendered image is converted back to sRGB for display. What does that mean for me? These cha…

Updates to lighting in three.js r155

The upcoming release r155 will contain a major change in context of lighting. The legacy lighting mode will be disabled by default which affects all light intensities and how point and spot lights decay. What does that mean for me? The release changes the default of WebGLRenderer.useLegacyLights from true to false and also deprecates the property. Meaning it will be eventually removed from the engine with r165. Setting WebGLRenderer.useLegacyLights to false is one important prerequisite for a…

[chloe]

@Updates to lighting in three.js r155

The goal of this change is to provide a single lighting mode that supports physically correct lighting. We believe the engine’s lighting should have been implemented like this in the first place meaning without internal scaling factors or custom decay implementations.

Besides, WebGPURenderer will only come with a single (physically correct) lighting mode. We are convinced it’s better to make this change in WebGLRenderer now so a switch to WebGPU will become easier.

---

Questions

For general questions, please reply to this thread. If you would like help updating some existing code, consider starting a new thread with the full context, then including a link in this thread.

We also recommend to check how the official examples and the manual will be updated to get a better impression of the migration tasks. You can do that by simply comparing the example code between r155 and 154.

Hello, I read your link, the version of rendering has indeed made a very big change, then may I ask what way can I use to adjust the rendering effect to the state of Figure r147? Do you have any parameters or anything like that? or there is no way?

[drcmda]

realism has to do with correct gamma and dynamic range. the right image appears more realistic, it is gamma correct and has high dynamic range. i would change nothing. previous versions had no color management so by default you would run wrong gamma, which is the #1 culprit for that 90s era cgi look with blown and banding colors and low dynamic range.

this is a good read, the example images also help: Color management in three.js

if you want to go back you can switch color management off.

THREE.ColorManagement.enabled = false
renderer.outputEncoding = THREE.LinearSRGBColorSpace
renderer.useLegacyLights = true

[chloe]

@drcmda

THREE.ColorManagement.enabled = false
renderer.outputEncoding = THREE.LinearSRGBColorSpace
renderer.useLegacyLights = true

Thank you very much for your answer, very useful