Runtime Mesh Component

[wilberolive]

@ - Yay, you’re not dead!

[Skifree]

@Chupacabra

I’m having an issue using the slicing system in the latest marketplace version of RuntimeMeshComponent and I’m not entirely sure how to debug what’s going on:

-I’m taking a static mesh (a wall, it’s pretty much just a scaled cube), then in BeginPlay I’m using “Copy Runtime Mesh from Static Component”
-I’m then slicing it down the middle with “Create Other Half” enabled and “Create New Section” selected.
-When I make the slice I get this error in the log: “RuntimeMeshLog:Error: Section is not of legacy type.”
-The resulting slice seems to have worked for the newly created section, but nothing happens to the original Mesh Component

Pre Slice: (Red line is where I make the slice)

Post Slice: (I’ve moved the pieces apart to illustrate the problem, the purple slice is the newly create mesh)

I’m using the exact same blueprint logic that I used for using the inbuilt procedural mesh slicing, which visually works as expected but results in a lot of weird collision issues (hence why I’m looking to switch over to your plugin).

Any ideas what I’m doing wrong?

Was this ever resolved? I just switched over from Procedural Mesh Components to RT Components and I have the same problem. Slicing creates new slices as expected, but the original mesh is unchanged…

I also only swapped out the basic ingredients and have run into this issue.

[a_prototype]

So I can prioritize things, I’m curious to know what features you’re most interested in?

Glad to hear that RMC is still in development!
Looking forward to the 4.17 release.

As for me, i’d love to see more Mesh creation utilities available in blueprint (cylinder, sphere, capsule etc.).
Also it would be super helpful to be able to get the index data for a raycast against a face. My current workaround is a bit hacky (each face (or quad) as its own section).

[Infiltrator]

Hi , I have an issue with runtime mesh component, I have posted a thread in content creation here : Issue with creating a mesh in run time in UE4 using data from .obj and RuntimeMeshComponent - Unreal Engine Forums. Could you take a look ? If you can provide some comments and insight into the issue that would be great.

[mflux]

Hi , excellent work I am currently using your plugin to develop my procedural buildings.

I noticed that generating tangents is very slow. I’m having trouble generating tangents myself in my own proc meshes. Is there a way to trick the material into using the derivative of a given normal to compute the tangent on the shader? Essentially, I want to still have correct looking normal maps without having to run the calculate tangent function.

[Koderz]

@Skifree

Was this ever resolved? I just switched over from Procedural Mesh Components to RT Components and I have the same problem. Slicing creates new slices as expected, but the original mesh is unchanged…

I also only swapped out the basic ingredients and have run into this issue.

This is the one remaining thing I want to look into before I push the 4.17 release. I hope to get to this tomorrow/Sunday.

@a_prototype

Glad to hear that RMC is still in development!
Looking forward to the 4.17 release.

As for me, i’d love to see more Mesh creation utilities available in blueprint (cylinder, sphere, capsule etc.).
Also it would be super helpful to be able to get the index data for a raycast against a face. My current workaround is a bit hacky (each face (or quad) as its own section).

I’ll try to add additional utilities at some point, but I’m more focused on the core features for now. I’m up for submissions for utilities for things like this.
As for being able to get the face index of a raycast… It’s untested but it should be in the github version, as I believe I added the necessary supporting code for that last weekend.
A section per quad is definitely beyond hacky as that’s a draw call per quad.

@mflux

Hi , excellent work I am currently using your plugin to develop my procedural buildings.

I noticed that generating tangents is very slow. I’m having trouble generating tangents myself in my own proc meshes. Is there a way to trick the material into using the derivative of a given normal to compute the tangent on the shader? Essentially, I want to still have correct looking normal maps without having to run the calculate tangent function.

Yeah, that function is horridly slow. Simply because it’s doing common vertex detection the brute force, and therefor exceedingly slow way. It’s basically a O(n^2) solution so it grows exponentially slower the larger the mesh. I have a new version in RMCv3. I might try to backport it to v2 until v3 is out.

[Rumbleball]

Hey there.
Trying to use the RuntimeMesh with Outliner in Materials - UE Marketplace. This material uses CustomDepth (Render CustomDepth Pass / CustomDepth Stencil Value) to create the outline. It is working with the RuntimeMesh as long as the RuntimeMesh is not fully Occluded (The ProceduralMeshComponent has issues as well, behaves even weirder than RuntimeMesh).

Screenshots out of Editor, not playing.
Blue Outline = StaticMeshComponent
Green Outline = RuntimeMeshComponent

Partially Occluded:

Occluded but RuntimeMesh (Actor) still selected:

Occluded, RuntimeMesh not selected:

Maybe this is related to the issue of Dustums:

@anonymous_user_a6092ea3

Hi everyone. I’ve been using Runtime Mesh Components for some time, and something has changed in my build (not sure when it changed). I have custom panels created with RMC, but they are not rendering in the Z PrePass (I’m pretty sure they used to, back in the 4.14 days?) I’m on 4.16 now, and using RenderDoc, I can see that they no longer are part of the depth pre-pass, and thus I’m getting a lot of overdraw, which is killing my performance. I have “Render in Main Pass” checked. Any ideas what could be wrong? Anything I should check? This is a VR app, so performance is crucial.

You can also check this by using the render options with the editor viewport:

A related thread for ProcedualMesh: Render Custom Procedure Depth Doesn't Work - Rendering - Epic Developer Community Forums

Regards

[Nazdorovye]

@Thumper

Migrated my project from 4.15 to 4.17.1 and there are many errors. Many of which are already listed in the pull request on the github repo for this. I was able to work through most of them except this one -

1>D:\GameDesign\UE_4.17\Engine\Source\Runtime\CoreUObject\Public\UObject/Class.h(655): error C2280: ‘FRuntimeMeshComponentPrePhysicsTickFunction &FRuntimeMeshComponentPrePhysicsTickFunction::operator =(const FRuntimeMeshComponentPrePhysicsTickFunction &)’: attempting to reference a deleted function
1>D:\GameDesign\KoreShanty-4.17\Plugins\RuntimeMeshComponent_v2.0\Source\RuntimeMeshComponent\Public\RuntimeMeshComponent.h(69): note: compiler has generated ‘FRuntimeMeshComponentPrePhysicsTickFunction::operator =’ here
1>D:\GameDesign\UE_4.17\Engine\Source\Runtime\CoreUObject\Public\UObject/Class.h(990): note: see reference to function template instantiation ‘bool CopyOrNot<CPPSTRUCT>(CPPSTRUCT *,const CPPSTRUCT *,int32)’ being compiled

Any ideas how I can fix this?

Added

template<>
struct  TStructOpsTypeTraits<FRuntimeMeshComponentPrePhysicsTickFunction> : public TStructOpsTypeTraitsBase2<FRuntimeMeshComponentPrePhysicsTickFunction>
{
    enum { WithCopy = false };
};

after

FRuntimeMeshComponentPrePhysicsTickFunction structure.

Managed to build without errors, but dunno, am not a programer.

[wilberolive]

@ - Did an update get submitted for 4.17 and we waiting on Epic again? 4.18 is about to land (my guess in next couple of weeks) and we don’t have a 4.17 update yet. sigh

[anonymous_user_c4a1f7d71 (anonymous_user_c4a1f7d7)]

Hi, we’re using the RuntimeMeshComponent, and I’m reading that there’s a function for saving and loading it, but we can’t for the lives of us find it. Could someone please point us in the right direction?

[OmniMachina]

@wilberolive

@ - Did an update get submitted for 4.17 and we waiting on Epic again? 4.18 is about to land (my guess in next couple of weeks) and we don’t have a 4.17 update yet. sigh

haha I feel you bro
im checking this thread every day - hoping RMC 4.17 got released

[Nazdorovye]

So I downgraded UE to 4.16, and it still won’t compile. What is latest compatible version?

[rYuxq]

It works for me in 4.17 (I pull from github)

[Nazdorovye]

@rYuxq

It works for me in 4.17 (I pull from github)

How? Did you make some fixes?

[rYuxq]

No, I didnt do anything.
I tested it again. I download the zip from github, replace my old folder with the new one and either build it from Visual Studio or just start the project

[Nazdorovye]

@rYuxq

No, I didnt do anything.
I tested it again. I download the zip from github, replace my old folder with the new one and either build it from Visual Studio or just start the project

You are the lucky one then, I guess.
I’ll just have to wait for stable release, as my builder highlites same old warnings and errors.

[anonymous_user_03985c40]

Hi! I heard this plugin would make for more efficient mesh creation. I am trying to make a terrain editor where the terrain cells are about 2m x 2m, and each mesh consists of a simple square with 9 verts (1 in center and 1 in middle of each side), and 8 triangles total. My goal is to create large landscapes of over 100x100 sections of this same mesh where each can be modified to create a rough terrain. The issue though is that even 100x100 creates a huge graphical load and my fps in editor drops like crazy. By spawning 10,000 meshes that’s only 90,000 vertices and 80,000 triangles…so why does this hammer my gpu so badly (running a 1080). Any ideas on how to get this running smooth would be great.

[BlackFangTech]

@Darlandra

Why does this hammer my gpu so badly (running a 1080).

Probably because you spawned in 10,000 separate meshes, each one requiring dynamic lighting.

[SRombauts]

@Darlandra

By spawning 10,000 meshes that’s only 90,000 vertices and 80,000 triangles…so why does this hammer my gpu so badly (running a 1080). Any ideas on how to get this running smooth would be great.

A bit late here, but what BlackRang666 is saying is that your current approach is far to naive: the polycount is not the problem here, the number of meshes is! Just for a starter, do a quick search on what are draw calls and why does they matter more than the number of vertices or triangles.

So to answer your question, a very good start would by to stop spawning 10000 separate objects, but instead manage to group them (for instance by 16*16) and then when the user edit one, either update the whole group or create a new separate object for the one edited (there is plenty of more seriously explained algorithms about this out there). This is also why Minecraft is not as simple to do well as it seems at the first look.

[ambershee]

10,000 meshes is a lot. I’d definitely take a look at the implementation and maybe even look into finding a technique to use them in instanced mesh components.