Announcement

Collapse
No announcement yet.

Runtime Mesh Component

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Great to hear from you [MENTION=141752]Koderz[/MENTION] with the news. Itching to upgrade my project to 4.16... wish if Epic was faster at updating the marketplace.

    Comment


      Very happy to see you still so much invested in this [MENTION=141752]Koderz[/MENTION]!
      [Gamedev programmer at Darewise (Paris) - We are hiring]
      UE4 Git LFS 2.x Source Control Plugin 2.14-beta for UE4.23 - (v1 integrated by default since UE4.7)
      UE4 Plastic SCM Source Control Plugin 1.4.6 for UE4.23 - (integrated by default in Beta status since UE4.24)

      Comment


        Yes thats great news [MENTION=141752]Koderz[/MENTION], thanks again!
        What we can do for speed up marketplace approval? Its almost one month for 4.16 version...

        Comment


          Just a quick notice to all that the marketplace has been updated. Got the notice an hour ago. As usual, let me know of any problems.
          Runtime Mesh Component - The best way to render procedural/runtime created meshes! - Version 3.0 Out Now!

          Comment


            Originally posted by Koderz View Post
            Just a quick notice to all that the marketplace has been updated. Got the notice an hour ago. As usual, let me know of any problems.
            Downloading now. Thank you very much indeed! You do the best work

            Comment


              Downloaded the 4.16 plugin, all seems to be working great. Quick couple of questions, wondering if anyone knows about either....

              1) Converting from a RMC mesh to a Static Mesh. I saw in the notes this should be possible, “RMC -> SMC in editor. (new)” but cannot figure out how to actually hook this up in blueprints. Had a quick look in the docs and didn't see much.

              2) Updating an instance of a RMC, being used as a component inside a blueprint, from an existing RMC. For example, I have a RMC instance as part of an actor blueprint. I want to update this existing component at runtime, but currently cannot as far as I can tell. If using normal static meshes, I can just call Set Static Mesh, but can find no comparable for either the existing UE4 procedural mesh component or the RMC. Ideally I'd like to be able to call Set RMC Mesh and pass in an existing RMC, the result from a slice operation for example.

              Thoughts?

              Comment


                Originally posted by ToastyFirePlace View Post
                Downloaded the 4.16 plugin, all seems to be working great. Quick couple of questions, wondering if anyone knows about either....

                1) Converting from a RMC mesh to a Static Mesh. I saw in the notes this should be possible, “RMC -> SMC in editor. (new)” but cannot figure out how to actually hook this up in blueprints. Had a quick look in the docs and didn't see much.

                2) Updating an instance of a RMC, being used as a component inside a blueprint, from an existing RMC. For example, I have a RMC instance as part of an actor blueprint. I want to update this existing component at runtime, but currently cannot as far as I can tell. If using normal static meshes, I can just call Set Static Mesh, but can find no comparable for either the existing UE4 procedural mesh component or the RMC. Ideally I'd like to be able to call Set RMC Mesh and pass in an existing RMC, the result from a slice operation for example.

                Thoughts?
                1) Unfortunately right now it's not really possible in blueprints. I'll keep that in mind for the next version.

                2) Well first up, the next version is being redesigned so it could do exactly this. As for slicing, you'd end up with a new full RMC which can be added to the current actor or a separate actor so not exactly sure what you're attempting to do here.
                Runtime Mesh Component - The best way to render procedural/runtime created meshes! - Version 3.0 Out Now!

                Comment


                  Originally posted by Koderz View Post
                  Not quite sure what you're getting vs trying to get. You should be able to turn collision on for any/all/none of the sections and it should just work. The caveat to that though is there's no good way to tell which side you're colliding with from a ray trace or whatever. That is something that's coming, but not yet. Just to make sure you're clear, the CreateCollision flag on CreateMeshSection creates a trimesh collision shape, that only works if UseComplexAsSimple is on for the RMC (most like it is since that's default) and you don't try to turn on "SimulatePhysics". The only time you should have to manually tell it to CookCollisionNow is if you want to query it with something like a ray trace in the same frame as creating it, by default collision won't update until the following frame.
                  Thank you for your explanation. It works now. Interestingly, i simply had to delete and recreate the 'Add RMC' node to get the collisions to work properly.

                  Is there a way to READ/FETCH the vertex/normal/uv etc data from a mesh section?

                  And is there a comfortable way to have multiple mesh sections share a set of triangles?
                  Last edited by a_prototype; 06-26-2017, 09:59 AM.

                  Comment


                    Originally posted by a_prototype View Post
                    Thank you for your explanation. It works now. Interestingly, i simply had to delete and recreate the 'Add RMC' node to get the collisions to work properly.

                    Is there a way to READ/FETCH the vertex/normal/uv etc data from a mesh section?

                    And is there a comfortable way to have multiple mesh sections share a set of triangles?
                    Well that's good it works, but hilarious that it worked after that...

                    There are ways to read it in c++, BP on the other hand is severely limited. That's something I want to look into for v3 but that might be a while. As for sections sharing triangles, what are you trying to do? Multiple sections within one RMC use the same vertices? partial sharing between sections in the same RMC? Or sharing mesh data between multiple RMCs? The last one there is coming in v3, and is part of the core so it'll be ready relatively quickly hopefully, the other 2 I'm not sure I'd want to try to support unless there was a really good case, the first one wouldn't be too bad, the second would be interesting to near impossible.
                    Runtime Mesh Component - The best way to render procedural/runtime created meshes! - Version 3.0 Out Now!

                    Comment


                      I'm trying out the 4.16 plugin, but I'm having weird results when attempting to get collision up and running.

                      My goal is have the player generate the procedural mesh at runtime and when they are finished, allow them to interact with the mesh (grabbing, throwing, etc.) and have it simulate physics. My attempts at this:
                      1.) Create a simple box mesh and use 'add collision convex mesh' exactly like in your example template. The box falls extremely quickly then bounces into the stratosphere. No idea why.
                      2.) Create a simple box mesh and use 'set mesh collision section' and 'set mesh section collision enabled' currently has no effect. The object falls right through the floor.

                      Could this be a problem with the 4.16 update? Any help would be appreciated.

                      And thanks for the awesome work on the plugin! Cheers to all the hard work.

                      Comment


                        Originally posted by uw19 View Post
                        I'm trying out the 4.16 plugin, but I'm having weird results when attempting to get collision up and running.

                        My goal is have the player generate the procedural mesh at runtime and when they are finished, allow them to interact with the mesh (grabbing, throwing, etc.) and have it simulate physics. My attempts at this:
                        1.) Create a simple box mesh and use 'add collision convex mesh' exactly like in your example template. The box falls extremely quickly then bounces into the stratosphere. No idea why.
                        2.) Create a simple box mesh and use 'set mesh collision section' and 'set mesh section collision enabled' currently has no effect. The object falls right through the floor.

                        Could this be a problem with the 4.16 update? Any help would be appreciated.

                        And thanks for the awesome work on the plugin! Cheers to all the hard work.
                        1) Sounds like a mass problem, have you altered the collision/gravity settings at all? If so what are they. Only other guess is if it started moving before convex cooked, but I doubt it since that version doesn't have async cooking.
                        2) That's expected. PhysX (The underlying physics engine in UE4) doesn't support moving mesh collision, only static. There's various reasons for this, but nothing can be done about that. Every movable object in the engine will be some combination of box/sphere/sphyl primitives or convex bodies, potentially multiple of any of those. For concave objects the engine generates a set of convex shapes to approximate it using V-HACD unless you import the collision hulls from an outside tool.
                        Runtime Mesh Component - The best way to render procedural/runtime created meshes! - Version 3.0 Out Now!

                        Comment


                          Originally posted by Koderz View Post
                          1) Sounds like a mass problem, have you altered the collision/gravity settings at all? If so what are they. Only other guess is if it started moving before convex cooked, but I doubt it since that version doesn't have async cooking.
                          2) That's expected. PhysX (The underlying physics engine in UE4) doesn't support moving mesh collision, only static. There's various reasons for this, but nothing can be done about that. Every movable object in the engine will be some combination of box/sphere/sphyl primitives or convex bodies, potentially multiple of any of those. For concave objects the engine generates a set of convex shapes to approximate it using V-HACD unless you import the collision hulls from an outside tool.
                          You were right, it was something ridiculous on my end. Thanks for the clarification and quick response!

                          Comment


                            [MENTION=141752]Koderz[/MENTION] - So just updated to 4.16 (installed the updated RMC from the marketplace) and get the following warnings when compiling. This only comes up in C++ projects and I get them in both VS and when hitting Compile in the editor. I tried created a new blank project and still get the same warnings. My compile then fails after this, so I haven't been able to use RMC with 4.16 yet. I'm not sure if these warnings are causing the compile to fail or something else, but thought I better report this just in case.

                            CompilerResultsLog: Info C:\Program Files\Epic Games\UE_4.16\Engine\Plugins\Marketplace\RuntimeMeshComponent\Source\RuntimeMeshComponent\RuntimeMeshComponent.Build.cs: warning: Module constructors should take a ReadOnlyTargetRules argument (rather than a TargetInfo argument) and pass it to the base class constructor from 4.15 onwards. Please update the method signature.
                            CompilerResultsLog: Info C:\Program Files\Epic Games\UE_4.16\Engine\Plugins\Marketplace\RuntimeMeshComponent\Source\RuntimeMeshComponentEditor\RuntimeMeshComponentEditor.Build.cs: warning: Module constructors should take a ReadOnlyTargetRules argument (rather than a TargetInfo argument) and pass it to the base class constructor from 4.15 onwards. Please update the method signature.
                            CompilerResultsLog: Info C:\Program Files\Epic Games\UE_4.16\Engine\Plugins\Marketplace\RuntimeMeshComponent\Source\RuntimeMeshComponentSlicer\RuntimeMeshComponentSlicer.Build.cs: warning: Module constructors should take a ReadOnlyTargetRules argument (rather than a TargetInfo argument) and pass it to the base class constructor from 4.15 onwards. Please update the method signature.

                            Comment


                              [MENTION=141752]Koderz[/MENTION] - 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?

                              Comment


                                Originally posted by wilberolive View Post
                                [MENTION=141752]Koderz[/MENTION] - 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.
                                Runtime Mesh Component - The best way to render procedural/runtime created meshes! - Version 3.0 Out Now!

                                Comment

                                Working...
                                X