Consider defaulting to `renderer.physicallyCorrectLights = true`

The current R3F defaults include…

• renderer.outputEncoding = sRGBEncoding
• renderer.toneMapping = ACESFilmicToneMapping

… both of which are generally good defaults for a physically-based rendering workflow (even if tonemapping is pretty subjective). For the same reason I think it’d be a good idea to consider defaulting to renderer.physicallyBasedLights = true. This is the only mode in which lights imported with a GLB model will look as intended. Eventually I’d like to see that become the default in three.js as well — see https://github.com/mrdoob/three.js/issues/23614.

[bhouston]

I agree. Everyone wants physicallyCorrectLights, and it was only added in this old fashion because we needed to not break backwards compatibility with people using incorrect lgihts.

[krispya]

The same is true for R3F users too. All our demos and tutorials are made with physicallyCorrectLights=false and making the change would mean at least updating all of those and educating users why their projects suddenly look wrong and why the same lighting tutorials and examples now look different.

Right now it isn’t something that comes up in the Discord form our users very often even though it is a GLTF workflow issue. Maybe something will change that, like more asset tooling, and we can reopen this issue.