Runtime Mesh Component

[housekiller]

I was able to solve my issues, I’ll post here what I did wrong so others may be helped.

@housekiller

Another more annoying issue I’m having with v2; I’m using:
runtimeMesh->CreateMeshSection(meshSectionInt, vertices, triangles, normals, texMap, vertexColors, tangents, false, EUpdateFrequency::Frequent);

I run that in a loop that adds +1 to meshSectionInt every loop.

The problem is that I end up with only 1 object, where i expect about 150 of them. Only the last object is in the runtime mesh. Any idea what I’m doing wrong here?

I kept overwriting my variables which created the object, thus I created the last object many times over.

@housekiller

Edit:
I seem to have misunderstood the inner workings, I though I could add pieces to a runtime mesh by calling createmeshsection multiple times for the same runtimemeshcomponent.

I have an actor that wants to create multiple meshes for itsself with different materials, how is it best to create multiple URuntimeMeshComponent instances? Any example with a piece of code? Or do I need to create an actor per mesh?

Working with sections works like a charm, my problem was that I kept creating new objects and did a CreateMeshSection for each of them.

@housekiller

When making an extra component during runtime I can’t even get a mesh in it to show up for some reason, I can only get it to work if the component already exists when the actor is created. Any clues?

Solved by using RegisterComponent() after creating a new object in the actor. This is how I create the empty objects;

URuntimeMeshComponent* newComp = NewObject<URuntimeMeshComponent>(this, objectName);
newComp->RegisterComponent();