RealtimeMeshComponent VS RuntimeMeshComponent

Take a look at this: https://github.com/TriAxis-Games/RealtimeMeshComponent

Yeah, u can do everything in UE. This kind of things have a common name of procedural generation. U can use build in options, write it yourself or use a 3rd party component, one of the popular ones is https://runtimemesh.koderz.io/

I recently started learning ue5, and I wanted to make a random procedural terrain that creates itself on when the game starts. I almost finished it, and now I just need a faster way to create the terrain. I found the Realtime Mesh Component 5 from github, but there is also the same one with the same author on the marketplace for around 6$. What is the difference between the two of them? Thanks!

Personally, I generate voxel terrain with noise then mesh it using the realtime mesh component. This allows for fully 3d worlds with caves, overhangs etc and for runtime editable terrain.

You could use the Runtime Mesh Component to deform the geometry itself. The deformations are handled on the CPU, so CPU access is required on the mesh. And you can also offload the work to another thread, so minimize/avoid blocking.

Are you using the RuntimeMeshComponent

Searching for ue4 and modifying a meshes vertex buffer, one quick result was this: https://github.com/TriAxis-Games/RuntimeMeshComponent which seems like a good place to start for modifying meshes at runtime in ue4.