I’m working with some continuously generated 3D Text meshes that I am rendering on-screen. I currently generate them as a
geom object in a separate thread, then pass them back to the main thread.
To render them, I’ve tried two implementations thus far:
- Creating a new
Batchobject when the
- Pre-allocating a number of
Batchobjects, and then creating a new
VboMeshobject when the
geomarrives with which to update an existing
Both approaches cause a brief visible pause in
Debug mode. In
Release it runs without significant visible hitching. Either way, I’m pretty set on eliminating the hitching in
Debug mode. But I’m not exactly sure how to best leverage Cinder to do this.
I believe maintaining a single
Batch and updating it with all incoming mesh data is probably fastest, but I am currently just pursuing a solution where I maintain several
Batch objects. I.e. one per incoming mesh.
So I’ve created a set of pre-allocated
Batch objects, but I don’t know how to easily update them with a
geom. I’ve only spotted approaches that require creating a
VboMesh which also makes the execution hitch.
I hope someone can help point me in the right direction? I.e. is there a easy way to use the geom data to write straight into a