Runtime Mesh Component

[anonymous_user_2d6a5faf]

@housekiller;639966

It’s usually not great practise having large sized meshes, here some things you could try (try them seperately and I’d be gladly hearing the results):
-Split into smaller meshes, not sectionized
-Light with stationary sun if not yet so and if it doesn’t have to move (or at least check what influence it has), it’ll still light and calculate shadows for movable and procedural meshes but only for lights that stay on the same location.
-Make a similar scene without runtime components (stationary directional light + movable meshes), if your framerate is still terrible you should look into optimising graphical settings for VR. Unbalanced graphical settings are easily capable of tanking framerate on any kind of hardware.

A single sun is what I am using, yep. And with the same amount of static meshes set to movable I had way better performance, so it’s something about the amount of runtime meshes I suppose.
As far as I know, there is no way to have a dynamic array of components in any actor (or is there?), hence also no way to create a single actor with a dynamic array of RuntimeMeshComponents, so the only way to split the big meshes is to split them into multiple actors. That is, from one actor with one component with 100 sections I will move to 100 actors with one component with one section each. I had tried it with the UEs ProceduralMeshComponent and haven’t noticed any performance difference, but maybe this will work better with the RuntimeMeshComponent.