Runtime Mesh Component

[Koderz]

@wilberolive;728852

@ - So I eventually got everything compiling and running. Those warnings from my previous post are still there though. Looks like the build files haven’t been updated as needed.

I was so excited to upgrade as I thought I might finally get rid of that annoying bug I have… but to my great devastation, I’m still hitting that same exception breakpoint every time I try to use RMC for the first time. See my other previous post from a while ago about it. It breaks out to VS at some exception breakpoint in the engine code. I then have to click Continue to keep going. Then I can continue using RMC with no problems until I stop the current game and then click play again. Then it happens all over again. So frustrating when you have to click play, let it break to VS, click continue in VS, then go about testing your game… like 100 times a day.

I’ve tried different engine versions as well as creating new fresh projects. It was all working amazingly for me back in 4.14. Don’t understand why I’m seemingly the only person hitting this problem, unless nobody else uses RMC in C++… surely not. If you use it just in BP then there is no issue.

I remember you saying that you fixed this issue… was that for v3 though?

Yeah, forgot about the warnings, and not much point in pushing a whole new update to fix just that.

As for the other, I’ve never seen it and I only work with it from C++. It has to be specific to something you’re doing differently that it’s not liking but I don’t know what it would be. I’m still on 4.15 for work project, but work with 4.16 and 4.17 almost daily now working on the new RMC. Not sure what would cause that though. For materials the RMC should be setup almost identically to the PMC.