Docs: Expand .aoMapIntensity description

[donmccurdy]

Clarification of the typical range for .aoMapIntensity.

Related:

• https://discourse.threejs.org/t/ambient-occlusion-wrong-with-khronos-neutral-tone-mapper/68192/5

/cc @WestLangley

[pailhead]

I would have made a PR but i might be a bit out of touch with these later versions. This is a great starting point, but if the number represents something from 0-100% we should then probably clamp it. As of today, is this still a property on some Material subclass, not nodes?

[WestLangley]

we should then probably clamp it

three.js does not validate user data. That is your app's responsibility.

[pailhead]

three.js does not validate user data

I may be misinterpreting this pattern:

https://threejs.org/docs/#api/en/materials/MeshPhysicalMaterial.sheenRoughness

three.js/src/renderers/webgl/WebGLMaterials.js

Line 410 in 216398f

uniforms.sheenRoughness.value = material.sheenRoughness;

three.js/src/renderers/shaders/ShaderChunk/lights_physical_fragment.glsl.js

Line 117 in 216398f

material.sheenRoughness = clamp( sheenRoughness, 0.07, 1.0 );

• Like this improvement, the docs do mention that the value is expected to be in the range from 0 to 1.
• However, 0 doesn't actually seem to be ever seen by the shader. The smallest value seems to be 0.07.
• Passing 123.4567 will result in the value of 1 in the shader.

I don't think that this is validation per se. Whatever the pattern may be, it could be applicable here.