WebGLRenderer: Only compile renderable objects #29345
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The methods
WebGLRenderer.compile()
andWebGLRenderer.compileAsync()
fail when trying to compile custom objects that define amaterial
property. My use case involves objects that manage child meshes. The composite objects provide access to an inner, shared material via a getter for convenience.To reproduce the error, uncomment line 47 or 48 in the following example: https://jsfiddle.net/7nvcjwk8/
This PR changes the
compile
method to only process renderable objects, similar to how it's done inWebGLRenderer.projectObject()
.Alternatively,
Object3D
could defineisRenderable
with a default value offalse
and the renderable sub classes could set this flag totrue
.