#Do most product configurators use dynamic lighting?
24 messages · Page 1 of 1 (latest)
I don't think most product configurators use three.js
Ah what do they use?
Well most are not 3D
and use photograph instead
some are 3D
I'm sure there are a lot that use three as well
Dynamic lighting in three.js product configurators probably depends a lot on the style of 3D model/scanning method
Simpler objects or more stylized 3D models probably make more sense for dynamic lighting
if the textures and lighting is more complex it may make more sense to use an optimized photo scan depending on your budget
i have some 3d scans that I need to simplify and was wondering about dynamic lighting so I could use normal maps etc.
You can use dynamic lighting, how good it looks will depend on the implementation and your scan
Three is capable of normal maps
One of the most common workflows is to export as a GLB or GLTF from something like blender, which will use the MeshPhysicalMaterial
You can take a peak at all the properties this supports over here: https://threejs.org/docs/index.html?q=material#api/en/materials/MeshPhysicalMaterial
thanks
in context of 3D most certainly rather use dynamic lighting, but there are a lot cases they bake it
in general you bake as much as possible of quality that is too expensive to archive in realtime reasonably like AO maps, however not all even aim for realistic appearance, most more technical/construction ones focus much more on the construction and benefits of 3D view part
aren't there hundreds like that already ðŸ¤
the shadowing looks baked
It looks like a physical material with an environment map reflecting off of it
which is a pretty standard workflow