I'm trying to understand the difference between various NodeMaterials, such as MeshStandardNodeMaterial and StandardNodeMaterial.
Is the ultimate goal to offer the same built-in materials as Three.js proper? (e.g. THREE.MeshBasicMaterial, THREE.MeshDepthMaterial, THREE.MeshDistanceMaterial, THREE.MeshLambertMaterial, THREE.MeshMatcapMaterial, THREE.MeshNormalMaterial, THREE.MeshPhongMaterial, THREE.MeshPhysicalMaterial, THREE.MeshStandardMaterial, THREE.MeshToonMaterial)
I'd also hope to be able to expect the same properties between normal materials and NodeMaterials. For example, does MeshStandardNodeMaterial accept an alphaMap (or alpha) input like THREE.MeshStandardMaterial? I'm having a hard time following the supported properties from the inheritance chain... it looks like there are references to a transparency property or an alpha property on StandardNode, but no support for a Nodes.TextureNode to replicate alphaMap functionality?
cc @sunag
Thanks! I'm really excited by the possibilities that NodeMaterials unlock 😄