InstancedBufferGeometry: maxInstancedCount property
See original GitHub issueThe maxInstancedCount
property is poorly-named, IMO.
I suggest that the property be renamed to .instanceDrawCount
, which specifies the number of instances to render. That is how the property is being used.
Also, the renderer should silently ensure the draw count does not exceed the maximum possible, based on the buffer size – as we currently do with BufferGeometry.drawRange
.
- [ x ] Dev
- [ x ] r115
Issue Analytics
- State:
- Created 3 years ago
- Comments:5
Top Results From Across the Web
three.js - Updating InstancedBufferGeometry and ...
... r124 InstancedBufferGeometry does not have a maxInstanceCount property. With r117 maxInstancedCount was renamed to just instanceCount .
Read more >InstancedBufferGeometry – three.js docs
An instanced version of BufferGeometry. Constructor. InstancedBufferGeometry( ). Properties. See BufferGeometry for inherited properties. # .instanceCount : ...
Read more >How to use Three.js InstancedBufferGeometry ... - iTecNote
Apparently Three's InstancedBufferGeometry & InstancedBufferAttribute objects ... InstancedBufferGeometry and THREE. ... maxInstancedCount = 8; cubeGeo.
Read more >Instancing with three.js — Part 2 | by Dusan Bosnjak
InstancedBufferGeometry () //this is going to wrap both geometry and a bit of the scene ... There is one missing though, the property...
Read more >Rendering 100k spheres, instantiating and draw calls
InstancedBufferGeometry ().copy(baseGeometry);. let instanceCount = 7000;. instancedGeometry.maxInstancedCount = instanceCount;.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I would make it a mandatory parameter similar to
InstancedMesh
.OK. Does #11209 have any bearing on this issue?
Do you think
.count
should be initialized toInfinity
, as is.drawRange.count
?