We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I notice an extra number of drawCalls after renderBundle.needsUpdate
let group = new THREE.BundleGroup() // mesh setInterval(()=>{ // material const material = new THREE.MeshBasicMaterial( { color: new THREE.Color(THREE.MathUtils.randInt(0,0xffffff)), side: THREE.DoubleSide, } ); mesh = new THREE.Mesh( geometry, material ); mesh.position.set( THREE.MathUtils.randFloat(-5,5), THREE.MathUtils.randFloat(-5,5), THREE.MathUtils.randFloat(-5,5) ) group.add( mesh ) group.needsUpdate = true }, 500) scene.add( group ); } function animate() { renderer.render( scene, camera ); console.log(renderer.info.render.drawCalls) }
https://jsfiddle.net/cdzm0pLq/20/
No response
r174 dev
The text was updated successfully, but these errors were encountered:
@RenaudRohlinger I'm new to the concept of the RenderBundle, do you think its the normal behavior here ?
Sorry, something went wrong.
No branches or pull requests
Description
I notice an extra number of drawCalls after renderBundle.needsUpdate
Reproduction steps
Code
Live example
https://jsfiddle.net/cdzm0pLq/20/
Screenshots
No response
Version
r174 dev
Device
No response
Browser
No response
OS
No response
The text was updated successfully, but these errors were encountered: