I really don’t get their reasoning to be honest. It’s not like things that are exposed on the engine API this release can’t be broken next even in the uppermost layers of what people interact with. Each engine version I have to change a few things in the RMC, in 4.18 for example they changed a return reference to a pointer. I expect this type stuff, especially in the lower levels of the rendering subsystems. I had plans of upgrading the slicer to directly slice a distance field which means you still have all the distance field support for meshes you go hacking apart with the slicer. After that I was planning the utilities needed to do full runtime generation of distance fields. All of that got put on hold until either they decide to accept it (or open it up in a way they’d prefer) or I get some other things done that more people can use and then come back to it since that will take a source compile of the engine with that PR to allow it.
What did you mean by splitting out the mesh slicing? btw RMCv2s slicer is pretty broken. I’m working on its replacement and it should be up in the next day or two hopefully.