-
Notifications
You must be signed in to change notification settings - Fork 3.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
Derived commands #3806
Derived commands #3806
Conversation
…rived commands can be recreated.
this._debugOverlappingFrustums = 0; | ||
this._dirty = true; | ||
|
||
// TODO: how to invalidate this? Get/set for properties above? Make some of them (e.g., vertex array) readonly? |
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.
Can we remove this TODO? It has the same idea we discussed today.
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.
How are we going to release the resources for the command? Primitives release the resources for each command, but who releases the resources for derived commands?
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.
The command can own the derived commands. In some cases - like in 3D Tiles - they will not have new resources.
What's the deal with the |
Just those minor comments. What is the best branch strategy here? Merge this into |
I'm not sure. The tests pass when run locally. |
Yes, that was my plan. |
Adds derived commands for 3d tiles, shadows, and OIT.