Replacing an attribute of a geometry instanced by another new attribute with a superior length break the renderer

[Samsy]

Description

On previous version of Three.JS, ( r162 havnt tested between then and now ) ,we were able to replace an entire instancedgeometry attribute with a new length and set the instanceCount to a superior value

This is a valuable feature for performances if you play with huge dynamic instanced geometry that increments count over time and allows to first allocate a smaller buffer then grow with a safe multiple to limit the size of the buffer

But this also limits flexibility of building geometries by a lot

In both WebGL and WebGPU back end it now breaks the renderer :

Look at the switchArray function

Live example

[Samsy]

maybe @RenaudRohlinger knows about it ?

[RenaudRohlinger]

Ah yes, it's because the instance node is created when the material is first mounted, you need to add material.needsUpdate =true.

https://jsfiddle.net/4pk7csru/4/

[Samsy]

@RenaudRohlinger

Here is the updated fiddle with material.needsUpdate = true

Does not seem to work :

https://jsfiddle.net/zjsy4r7a/1/

[RenaudRohlinger]

oops didn't see my console, indeed, then we need to fix this in InstanceNode.

[Samsy]

@RenaudRohlinger This is a blocking bug on my end, can I help with this ?

Where should I look at exactly ?