The thing is that
resource.set_buffer(res, new_buffer) sets the resource named
res to the contents of
If all mesh components use the same resource (in you case
/main/quad.bufferc), you’ll get the scenario you now have.
As Marius hinted, there’s a way around this, by declaring resources for future use, as resource properties in your script. You can set such a resource, and then call
go.set(mesh_url, "vertices", res) to change the resource that the mesh component uses.
Ideally, soon we’ll have a way to be able to create some resources on-the-fly. It’s not something we’ve had on the roadmap yet though, and I wouldn’t want to rush into making such an api, but I can see some benefits to it for very dynamic content.