Our application has potentially high throughput needs, so I’m a bit concerned about how working in a non-run-time environment would create a bottleneck. I’m not sure it’s viable to create a mesh, import a mesh, build the scene, etc. If we’re doing 10s of thousands of these a day, I feel like that would add up very quickly. Even if scene was simple, it seems like a lot of overheard that would otherwise be unnecessary. It’s unfortunate that UE isn’t friendly with regards to run-time mesh modifying.
I was just looking at a unity tutorial that made this look really straight forward and so I’m surprised to hear that it’s not also a common thing in UE. I feel like landscape and mesh modifications are pretty common in a lot of games (user character creation sections where head shapes change with a slider), though perhaps these are done differently with blending or something.
I’ve been looking into a couple possibilities:
Procedural Mesh Component
Run-time Mesh Component (open source project)
I’m actually already kind of procedurally generating the meshes right now and have the z values stored in a single text file, so getting them into a matrix should be quite simple.