You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working at the post processing nodes, I have noticed that scenes with MeshBasicMaterial lack some features when used with WebGPURenderer. E.g. the quite commonly MeshBasicMaterial.envMap is not supported with WebGPURenderer so far.
I've tried to fix it by myself but NodeMaterial.getEnvNode() is only evaluate for lit materials right now.
Since MeshBasicNodeMaterial has set its lights properties to false, getEnvNode() is never called. I'm not sure where the best spot in NodeMaterial is for fixing that.
The more exotic lightMap and aoMap should also be supported since there are some baking workflows that make use of this combination. specularMap seems also missing.
Description
While working at the post processing nodes, I have noticed that scenes with
MeshBasicMaterial
lack some features when used withWebGPURenderer
. E.g. the quite commonlyMeshBasicMaterial.envMap
is not supported withWebGPURenderer
so far.I've tried to fix it by myself but
NodeMaterial.getEnvNode()
is only evaluate for lit materials right now.three.js/src/nodes/materials/NodeMaterial.js
Lines 355 to 357 in 513ea12
Since
MeshBasicNodeMaterial
has set itslights
properties tofalse
,getEnvNode()
is never called. I'm not sure where the best spot inNodeMaterial
is for fixing that.The more exotic
lightMap
andaoMap
should also be supported since there are some baking workflows that make use of this combination.specularMap
seems also missing.Reproduction steps
Code
Live example
Live example: https://jsfiddle.net/p392kuho/
Screenshots
No response
Version
r167dev
Device
No response
Browser
No response
OS
No response
The text was updated successfully, but these errors were encountered: