Runtime Mesh Component

[Koderz]

@wilberolive;586263

@: I believe I’ve found another bug. It seems like the runtime mesh isn’t updating the nav mesh like a procedural mesh does. I created an actor with a runtime mesh using the same blueprint shown in the picture from my earlier post and then created a second actor using a procedural mesh, again using the same blueprint. I then added a nav mesh bounds volume to the level and set it to dynamically update. When you drop the actor on the level with the procedural mesh, every works correctly. The nav mesh updates and takes the procedural mesh into account. However when you drop the actor with the runtime mesh on the level, the nav mesh does not update at all. Even when you force it to update it doesn’t take the runtime mesh into account.

Well that’s strange… I don’t see anything special in the PMC to support that, and the collision in the RMC is almost identical to the PMC’s until I get the upgrades done. I’ve not had much experience with the navmesh so I’ll try to take a look at it here soon in my bug fixing pass.

@Chariots;586420

As a workaround on the nav issue: You need to reset the navigation flags on the rmc.

RMC->SetCanEverAffectNavigation(false);
RMC->SetCanEverAffectNavigation(true);

This should enable navmesh generation. I do this on the first tick (and never again), I recall that it wouldn’t work on BeginPlay, can’t test it right now unfortunately. In editor you can also force generation of it by modifying any property of the actor it’s in, or by moving it slightly.

If you change the mesh later do you have to do this again?

@Thumper;586508

I’m curious how one would use the packed vertex arrays method described on the documentation site. I see your example with the 640K waves which looks great, but I’m wondering how that was done in terms of the containers that were used. I have similar sized container and a simple way of having sections to it, but I don’t understand how I could pack all the vertices into a container and only update the only the sections in questions vertices. Any chance I could see the wave examples code?

While there’s not much to these examples (and I haven’t made absolutely sure they work with the latest version quite yet. I will do that in the next few days though) it does contain everything I used in those images.
https://github.com//UE4RuntimeMeshComponentExamples
The wave specifically is here…
https://github.com//UE4RuntimeMeshComponentExamples/blob/master/Source/RMC_Examples/Actors/AnimatedTerrain.cpp
The Generate() function sets up the mesh including the full vertex information, as well as index buffer, then in the Tick function it recalculates and updates the positions and updates them alone. There’s a similar way to update the rest of the vertex information using BeginMeshSectionUpdate() and EndMeshSectionUpdate() and you can also still use UpdateMeshSection like the PMC but it was adapted to work with the packed vertex.