Runtime Mesh Component

[housekiller]

As a warning, this isn’t going to be an easy fix, and may require a drastic structural change in how the RMC works. It appears the StaticMesh Rendering now uses 4 independent buffers, {Position}, {Normal/Tangent}, {UVs}, {Color} and each has an associated SRV with their datatype. Since the position/tangents/uvs/colors don’t share a datatype I think it might be required to keep them in separate buffers now. This isn’t exactly hard to support, and it’d be nearly invisible for anyone using the blueprint API, or the MeshBuilder, but that’d be the end of single/dual/triple buffers and it’d just become a quad buffer full time, so if you set the mesh data with the single array of FRuntimeMeshVertexSimple it’d end up having to split it, so that’d slow that function down a bit, same with dual buffer, same with triple. So the best solution would be to pretty much rely entirely on the meshbuilder from this point forward and deprecate out all the old API but not sure that’s what I want to do. Will have to investigate this more once I have some more time.

Nuts, I’m trying to get a packaged build working of 4.17 with RMC 2 with using light propagation volume, the packaged build doesn’t work in 4.17. (This issue: Unreal Engine Issues and Bug Tracker (UE-49205)).

It got fixed for 4.19 but then I can’t use RMC, I’m thinking to reproduce the change in 4.17 made to make LPV work, but I’ve never edited or compiled the engine before, anyone who can deduct what files I’d need to change?

Edit: I’m trying to just comment out the assert that makes it fail, no idea what it’ll do though.
-> This resulted in the packaged build being able to run, but lpv didn’t work. Guess I’m waiting for 4.19 then.

When opening my project I get a message stating that I need to rebuild the RMC plugin, after agreeing it rebuilds the entire engine, how do I prevent that behaviour?