-
Notifications
You must be signed in to change notification settings - Fork 32
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
Per-node UBO population and per-frame cam state access #676
base: main
Are you sure you want to change the base?
Conversation
…populate UBOs on their own
…that is attached to a pass
@@ -48,7 +48,6 @@ open class DefaultNode(name: String = "Node") : Node, Networkable { | |||
return true | |||
} | |||
|
|||
override var nodeType = "Node" |
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.
Will this cause any trouble in other parts of scenery that rely on this node type?
Or rather: will removing the property nodeType
altogether result in any unexpected behavior in other parts of scenery?
} | ||
} | ||
|
||
var stereoEnabled = false |
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 is this false if it is a stereo camera?
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.
Looks good, but maybe add a short documentation to the populate UBO classes?
This PR introduces:
PopulatesUBO
interface, which enables node to define their own serialisation procedure, aka, how to translate a node's information into something accessible to shaders that goes beyond ShaderProperties