Runtime Mesh Component

[S0rn0]

@;571093

As @Korcan said, you can replicate the raw meshes but you’ll have to do it yourself for now. It’s a planned feature for the RMC but it will likely be a while before I touch it as to be honest it falls behind most of the other wanted features since I need several of the others for my own project.

Since you mentioned voxel directly… Replicating the meshes is a valid option, but depending on the type of voxel you’re working with, replicating the voxel data can frequently be smaller and therefor lower bandwidth due to the type of data being easy to compress. Think about it this way, each FRuntimeMeshVertexSimple is 32 bytes… Naive mesh generation of Minecraft like blocks needs 4 vertices (128 bytes) + 6 indices (4 bytes each so another 24 bytes) for each visible face whereas usually you can represent blocks in 1-2 bytes depending on what you’re doing. Smooth voxel is another story and depends heavily on the surface extraction algorithm used.

Ah, very true. I tried using Unreal’s compression and was able to compress a TArray containing 32^3 uint8s down from 32768 bytes to 58. I guess this also debunks my idea that having the server rely on RPC’s to the client to change blocks in an array.
I still need to think about how to “nicely” replicate the data to the clients though - Unreal’s replication system is still new to me.

Recently I tried PolyVox, but am not sure if I like using it with Unreal or not yet… this also adds more replications woes (for me anyways).