Runtime Mesh Component

[housekiller]

@;635101

Thanks for the donation!

You can convert to a static mesh by selecting the RMC in editor and finding “Convert to Static Mesh” in the details panel. This will only work in editor.

So not available/legal in built application?

@;635101

It’s been a while since I’ve put much thought into replication, but you can’t do conversion to static mesh at runtime, and even then the SMC does support replicating the mesh either. I’ve had a few thoughts on how to do it, but I’ve not really dug into it as you’re talking replicating potentially MB’s of mesh data and it usually ends up being better for the app to do it’s own replication. In the case of voxel, it’s easier to replicate the voxel data and regenerate the mesh on the client for example. Other projects have similar ways to more efficiently get the needed parts to client/server than straight mesh replication.

It’s meant to run on local network only for now so size is practically no problem, for now I’ll share the files between server & clients, import on both and replicate the transforms with necesary logic checks as a quick fix.
Interesting ideas for voxel based meshes, I’m planning a project on the side where this will be relevant.

@;635101

From your edits it appears you found the problem to movable objects. Basically PhysX (the underlying physics engine) doesn’t support dynamic moving triangle meshes. They work well for static objects, but for dynamic you have to use an approximation of the object through some combination of convex hulls, cubes, spheres, and capsules. Currently the RMC only supports convex hulls but that will be changed in the future. I’m investigating ways to generate this at runtime, but there isn’t an easy solution to this.

For now I made a simple box hull which is enough for my current project, might make something more complex as the need arises.