-
-
Notifications
You must be signed in to change notification settings - Fork 35.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebGPURenderer: Sheen #26329
WebGPURenderer: Sheen #26329
Conversation
|
||
} | ||
|
||
node = node.clamp( 0.07, 1.0 ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why the minimum is 0.7?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that 0.07
is to prevent incompatible values.
material.sheenRoughness = clamp( sheenRoughness, 0.07, 1.0 ); |
@@ -43,13 +43,14 @@ const toFloat = ( value ) => { | |||
|
|||
class NodeBuilder { | |||
|
|||
constructor( object, renderer, parser ) { | |||
constructor( object, renderer, parser, scene = null ) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe for scene we can use an approach like for CameraNode or ObjectNode -- taking the value from frame updates?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm... Using this approach, we can try soon create sceneBackground
(or just background
), it can change the code if scene.background
is different, the same not happen with per frame approach.
Description
Added
sheen
support forPhysical Lighting Model
.