Runtime Mesh Component

[Koderz]

@Chupacabra;632648

I’m having an issue using the slicing system in the latest marketplace version of RuntimeMeshComponent and I’m not entirely sure how to debug what’s going on:

-I’m taking a static mesh (a wall, it’s pretty much just a scaled cube), then in BeginPlay I’m using “Copy Runtime Mesh from Static Component”
-I’m then slicing it down the middle with “Create Other Half” enabled and “Create New Section” selected.
-When I make the slice I get this error in the log: “RuntimeMeshLog:Error: Section is not of legacy type.”
-The resulting slice seems to have worked for the newly created section, but nothing happens to the original Mesh Component

I’m using the exact same blueprint logic that I used for using the inbuilt procedural mesh slicing, which visually works as expected but results in a lot of weird collision issues (hence why I’m looking to switch over to your plugin).

Any ideas what I’m doing wrong?

Hey, sorry about the late response. I actually didn’t get a notification when you posted this. I’m not sure what would cause that… Would you be willing to send me some more details about how you did this and I’ll try to get it fixed! I actually tested that using SMC converted meshes… so not sure why it would be doing that. I’m also around the UE4 Discord if that’s easier.

@housekiller;634391

Fantastic work thanks!
I’m importing various models at runtime via assimp.

One question though; while reading somewhat bigger files (+50k faces) and giving the info for making the mesh the ue4 application freezes for a second. Is there something I could do to prevent this from happening?

Thanks! Glad it’s been useful! Assuming it’s not Assimp, the two primary culprits for something like that is first collision, and secondly if you’re using the RMC’s utility to calculate normals/tangents. Collision will hitch with large meshes due to cooking. The normal/tangent calculator is exponentially slower for large meshes, which will be fixed soon. Are you using one or both of those?