Docs: Improve Material page.

[atul-mourya]

Clarification on the Tonemapped Property

Description

After observing some confusion, including my own experiences, regarding the behavior of tonemapping following the r154 update, particularly among users accustomed to utilizing effect composers for post-processing, I have taken steps to enhance the clarity of the documentation pertaining to the tonemapped property.

This update includes additional insights aimed at providing further assistance to readers encountering similar challenges.

[donmccurdy]

I do see what you mean, but in another sense, the setting is very much not ignored by post-processing:

three.js/examples/jsm/postprocessing/OutputPass.js

Lines 44 to 54 in e65206d

	render( renderer, writeBuffer, readBuffer/*, deltaTime, maskActive */ ) {
	this.uniforms[ 'tDiffuse' ].value = readBuffer.texture;
	this.uniforms[ 'toneMappingExposure' ].value = renderer.toneMappingExposure;
	// rebuild defines if required
	if ( this._outputColorSpace !== renderer.outputColorSpace || this._toneMapping !== renderer.toneMapping ) {
	this._outputColorSpace = renderer.outputColorSpace;
	this._toneMapping = renderer.toneMapping;

Perhaps we say something like ...

Ignored when rendering to a render target, but may be applied in post-processing by using THREE.OutputPass.

[Mugen87]

but may be applied in post-processing by using THREE.OutputPass.

OutputPass applies tone mapping to the entire image and can't evaluate the material property anymore (or in other words the pass can't distinct between tone-mapped and non-tone-mapped objects).

[donmccurdy]

Ah! Sorry, was thinking of renderer.toneMapping, I should have read this more carefully. Looks good to me, thank you @atul-mourya!