I just now saw your message rdb.
Well within the actual game project, this is particularly used to generate terrain, hills, valleys, lakes, rivers etc. Since that is the case, it could be a bottleneck, as the terrain size is user-dependent, the user decides the size of the map to his liking.
That explains the additional copies each time “modifyVertexData” is called, thanks.
That’s actually how I’m doing things, many Geoms, one GeomNode which represents a ‘chunk/tile’ of the terrain. Then to create new ‘chunks/tiles’ as the player moves, I just instance the GeomNode to a different position and modify some of its Geoms. Of course I have to do this asynchronously but that is a story for another day!
Thanks for the additional clarifications rdb.