Not entirely sure where the RMC stands currently. Initiating a chat with Epic to see what’s up.
Alright, before I start this. I personally have ZERO intention of dropping the RMC, and up until Friday I was still actively developing it, granted very slowly, but I’m in question/concern right now as to where my work stands.
@JamesG Within the next day I’ll be opening a new email chat with you and Ori as I’d love it if you could provide a little clarification on a few things about something on the roadmap linked below. Before I do, I saw the new async collision. Haven’t tried it but thank you and Ori both (and whoever else was involved) for moving forward with that! I like the new solution better than my quick and dirty get it running setup.
Now, I was pointed to this… Trello …Friday and is why I’ve currently halted my own work on the RMC until I can get a little clarification on a few things.
This post is honestly a bit vague beyond the obvious specific features of mesh editing. The engine already has the CustomMeshComponent, ProceduralMeshComponent and then I added the RMC on top of it to improve on them both. This obviously makes for a question I get nearly daily of “what should I use? what’s the difference?” So depending on where this goes I think before long the path of permanently replacing/merging the PMC/RMC is probably a good idea, and then it’s just a question of what should happen to the CMC, but we can come back to that soon.
So this new mesh editor has me a little confused/concerned. The very high level and largest question this brings up is does this new editor replace the PMC? and with that the RMC? Or is this a separate tool meant more for programmatic simple meshes like say a maze? Then for things like a full voxel engine, or terrain engine or model loading etc you’d still need the PMC/RMC. So until I can hopefully get some clarification I’ve stopped work on the RMC since I have a lot of time already into unreleased work on it and don’t want to continue if it’s going to be made useless by this new feature.
So to all of those currently using the RMC. I will still continue to support it and bug fix it for as long as it’s used, but I’m not currently moving forward with the new features until I verify what the RMC’s place is in all of this.