-
-
Notifications
You must be signed in to change notification settings - Fork 412
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How this compares to FMeshDescriptionBuilder? #288
Comments
Is that set of C++ classes editor-only? RMC works the same in packaged builds. |
Also I'm pretty sure RMC5 has a static path draw mode as one of the mesh setup options |
FMeshDescriptionBuilder is not editor-only, static meshes can be generated at runtime in the packaged game with it, I did it myself and it worked. |
If I remember correctly, I think creating a static mesh at runtime with "FMeshDescriptionBuilder" is slow with things being forced to happen on the game thread, while the RMC can do almost the whole mesh setup on custom threads. Would be good if someone would do some performance comparisons to really see how much difference there is. RMC also has support for automatic distance field generation and static raytracing (so both Lumen SWRT and HWRT), which static meshes created with FMeshDescriptionBuilder do not have as far as I know. |
Unreal Engine has a way to build static meshes at runtime that is built in, using FMeshDescriptionBuilder to create the meshes:
https://www.reddit.com/r/unrealengine/comments/pn53lo/building_a_staticmesh_in_c_during_runtime
This plugin apparently does the same, it can create meshes that render using the static draw path, are the meshes created by this plugin any faster than the meshes created by FMeshDescriptionBuilder?
The text was updated successfully, but these errors were encountered: