WebGLRenderer: Replace .outputEncoding with .outputColorSpace

[donmccurdy]

Changes in this PR:

• WebGLRenderer: Replaces .outputEncoding with .outputColorSpace
  • THREE.sRGBEncoding → THREE.SRGBColorSpace
  • THREE.LinearEncoding → THREE.LinearSRGBColorSpace

Remaining changes for r152, in next PRs:

• WebGLRenderer: Change default output to sRGB
  • WebGLRenderer: Default output to sRGB #25783
• Texture: Replace .encoding with .colorSpace
  • Texture+WebGLRenderTarget: Replace .encoding with .colorSpace #25771
• Update documentation

Related issue:

• Roadmap for a color-managed workflow in three.js #23614

[donmccurdy]

@Mugen87 from #23614 (comment) I understand we may want to break this into two PRs:

1. Rename .outputEncoding and update all references
2. Change the default and update affected examples

I'll split the PR tomorrow, unless you or @mrdoob would prefer otherwise.

[Mugen87]

Yes, that would be great.

[github-actions]

📦 Bundle size

Full ESM build, minified and gzipped.

Filesize	Gzipped	Diff from dev
627 kB	155.9 kB	+400 B

🌳 Bundle size after tree-shaking

Minimal build including a renderer, camera, empty scene, and dependencies.

Filesize	Gzipped	Diff from dev
418.7 kB	102 kB	+431 B

[donmccurdy]

@Mugen87 - done!

[Mugen87]

Merging this before even more conflicts occur.

[Mugen87]

Feel free to improve the migration guide. I've just added a first draft: https://github.com/mrdoob/three.js/wiki/Migration-Guide

[donmccurdy]

Thanks @Mugen87! I'll make suggestions on the migration guide after the next few PRs (or before r152, if the PRs slip).

[938640624]

Hello, I'm going to the renderer. OutputEncoding = THREE. SRGBEncoding replace the renderer. OutputColorSpace = THREE. SRGBColorSpace, the effect is completely different, THREE. The effect of SRGBColorSpace added and not added is almost the same, should this be handled?

[donmccurdy]

Hi @938640624, please use the forums (https://discourse.threejs.org/) or Stack Overflow and provide enough context (demo or code) for someone to fully and immediately reproduce the issue you're seeing. The renaming of the property has no side effects, but you may be seeing the results of other changes in recent three.js versions, as described here. In any case we prefer to help you work through these questions outside of GitHub issues. Thanks!