MeshPhysicalMaterial: .clearcoat -> .clearcoatIntensity
See original GitHub issueDiscussion continued from #18684
I suggest renaming MeshPhysicalMaterial.clearcoat
to .clearcoatIntensity
. It is an intensity value in [0, 1].
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
MeshPhysicalMaterial#clearcoat – three.js docs
MeshPhysicalMaterial. An extension of the MeshStandardMaterial, providing more advanced physically-based rendering properties: Clearcoat: Some materials ...
Read more >MeshPhysicalMaterial - Three.js Tutorials - sbcode.net
In this lecture we experiment with the Three.js MeshPhysicalMaterial. ... material.roughness = 0.2 material.metalness = 0 material.clearcoat = 0.3 material.
Read more >clearcoat should not use underlying normal map ... - GitHub
I have recognized that the PhyscialMaterialShader is taking the perturbed normal of the material into consideration.
Read more >Three.js on Twitter: "ClearCoat in MeshPhysicalMaterial is ...
ClearCoat in MeshPhysicalMaterial is looking good ...
Read more >Flash Sonoof HAA RavenCore - C esp-homekit-devices - GitAnswer
Today I discovered a strange problem. With FLASH Sonoff mini R2. Everything goes by default until I configure JSON and after restarting the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
OK, closing…
Nested sub-properties (
material.clearcoat.intensity
) are one naming pattern, prefixed properties (material.clearcoatIntensity
) are another. Neither is incorrect, but the latter is more consistent with e.g.material.emissiveIntensity
and the many.____Map
properties.To date, we don’t have any
.fooIntensity
properties except those that are paired with a.foo
property they modify, like emissive or envMap. I’d prefer that our long term goal be to align with other PBR models rather than creating new models and new names, so IMHO the term.clearcoat
is more future-proof.Unreal engine calls this “clear coat”, as far as I can see, and states: “Amount of clear coat layer, 0 acts like the standard shading model, 1 is the full clear coat model.” This aligns with Autodesk Standard Surface, Filament, glTF, Houdini, and Blender. I don’t think we should rename the property, diverging from others further.