Runtime Mesh Component

[housekiller]

@Mtimofeev;639815

I appreciate your reply. A similar scene with imported static mesh gives me steady 120+ fps. My scene is really very simple - it is just few rooms: walls, floors and ceilings, a single source of light (the sky light) and I’d assume there should be a way to get 90fps. What I think could be problematic is that every room is currently an actor with single RuntimeMeshComponent that consists of a large number of sections. I have mistyped it in my OP, the RuntimeMeshComponent is rather constituted by 40-120 sections. But there are only 4-8 such components in the whole scene. Can this be a problem? Would it be better if these sections were instead separate actors? I absolutely need to be able to apply a material separately to each of the sections, so I either have to make them RuntimeMeshComponent sections or separate actors.

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.