Thank you for another great video! You will get a better perf approximation in full screen (F11). It may be a bug currently, but the draw and primitive stats seem to also report editor components.
Yes, you're right, I'm just giving an approximation of relative performance. IRL, you would build a standalone dev version for proper benchmarking and optimising.
UE 5 Editor surprises every day! Thanks for this essential info. Just wondering if there is any Node that you can call from your PCG that will convert PCG to the static mesh?
amazing tutorial really helping to cement what i have figured out on my own its helping me build out my large map , i hope you will show what to do with the floors/roofs as i haven't found a great way to do this yet , keep up they great work
Hey thank you for the awesome video and showing GPU monitoring. Question though about collisions. It seems that my walls have no collisions on them. How do I add them?
When I use Merge Actors, I can’t replace it with another object. Everything seems fine until the “Do you want to replace” warning, but after that, if I select a file named SM_Wall, my merged file is renamed to SM_SM_Wall. How can I fix this?
The same way we made the door mesh, take the original wall and cut out a window the same size and position as we used for the 1st video mock ups using the grid tool and save it. From there you need a way to place that new wall mesh. I couldn't get it to work alone so took the answer from the tutors awesome plugin. In BP_SplineWall: Duplicate the DoorMesh variable and name it WindowMesh. Complie and set (I set in editor to keep the BP default blank). Duplicate the DoorPosition array variable and name it WindowPosition. The logic for the door is in the construction script connected to the set static mesh node on the far right. In this logic duplicate the array search and boolean select and all connected pins just before the cast node. Rewire the new select node in between the old select node and the cast. Old select output is new B input. Delete the duplicated Wall Mesh getter you just disconnected. Replace DoorMesh variable getter connected to new A with WindowMesh variable. Replace DoorPosition variable getter connected to new array contains with WindowPosition variable.
First of all - thank You for another great tutorial! I have a question tho. Can I just leave the spline meshes on the scene for gameplay instead of merging them? I mean a situation where You have a river or road mesh. After merging it into one mesh, it's not too good for rendering because when You see but 1 pixel of it, it will render the whole road. So hence my question if it's totally safe to just leave splines in such situation. From my understanding as long as they don't need to be recalculated (they don't move, don't get edited by anything etc.) they should be fine, right? Once again, a great series! Cheers!
Yes, you can leave the spline meshes in the scene for gameplay, you don't have to convert. As always, profile your game near the end of dev to see if there's any performance bottlenecks and then you can convert to static mesh if you have to (but I think you would have to have a LOT of structures in your level). I think you can now have nanite meshes in your spline mesh components as well, but I need to double check that works.
Packed levels would not work well on terrain of unknown shape and size generated at runtime. A big set of buildings on a plane won't work in a hillside city.
I did mention this briefly in the video but the difference is that Packed Level Actors are for static meshes ONLY and provide the instancing of the meshes (hence the Packed), whereas Level Instances can also contain functional assets such as blueprints and do not give you the benefits of instancing.
Thank you for doing this video, it's full of important info that you don't see everywhere!!
This video is filled with a lot of useful information. Thanks a lot for that.
Absolutely stellar video, thank you so much for your time and sharing the knowledge.
Thank you, more actual useful optimization tutorials are needed
Great video! Really appreciate you going to the effort of testing all of the combine methods!
Thank you for another great video! You will get a better perf approximation in full screen (F11). It may be a bug currently, but the draw and primitive stats seem to also report editor components.
Yes, you're right, I'm just giving an approximation of relative performance. IRL, you would build a standalone dev version for proper benchmarking and optimising.
UE 5 Editor surprises every day! Thanks for this essential info. Just wondering if there is any Node that you can call from your PCG that will convert PCG to the static mesh?
Yes. If you use "Clear PCG Link" on your PCG blueprint, they will become regular, unchanging static meshes
amazing tutorial really helping to cement what i have figured out on my own its helping me build out my large map , i hope you will show what to do with the floors/roofs as i haven't found a great way to do this yet , keep up they great work
I have a cunning plan for floors and roofs but I haven't prototyped it yet, so not sure if it will fully work.
Hey thank you for the awesome video and showing GPU monitoring.
Question though about collisions. It seems that my walls have no collisions on them. How do I add them?
When I use Merge Actors, I can’t replace it with another object. Everything seems fine until the “Do you want to replace” warning, but after that, if I select a file named SM_Wall, my merged file is renamed to SM_SM_Wall. How can I fix this?
very informative, thank you
You are good tutor :)
Yo, how do we make that window mesh though? T.T
The same way we made the door mesh, take the original wall and cut out a window the same size and position as we used for the 1st video mock ups using the grid tool and save it.
From there you need a way to place that new wall mesh.
I couldn't get it to work alone so took the answer from the tutors awesome plugin.
In BP_SplineWall:
Duplicate the DoorMesh variable and name it WindowMesh. Complie and set (I set in editor to keep the BP default blank).
Duplicate the DoorPosition array variable and name it WindowPosition.
The logic for the door is in the construction script connected to the set static mesh node on the far right.
In this logic duplicate the array search and boolean select and all connected pins just before the cast node.
Rewire the new select node in between the old select node and the cast. Old select output is new B input.
Delete the duplicated Wall Mesh getter you just disconnected.
Replace DoorMesh variable getter connected to new A with WindowMesh variable.
Replace DoorPosition variable getter connected to new array contains with WindowPosition variable.
First of all - thank You for another great tutorial! I have a question tho.
Can I just leave the spline meshes on the scene for gameplay instead of merging them? I mean a situation where You have a river or road mesh. After merging it into one mesh, it's not too good for rendering because when You see but 1 pixel of it, it will render the whole road. So hence my question if it's totally safe to just leave splines in such situation. From my understanding as long as they don't need to be recalculated (they don't move, don't get edited by anything etc.) they should be fine, right?
Once again, a great series! Cheers!
Yes, you can leave the spline meshes in the scene for gameplay, you don't have to convert. As always, profile your game near the end of dev to see if there's any performance bottlenecks and then you can convert to static mesh if you have to (but I think you would have to have a LOT of structures in your level).
I think you can now have nanite meshes in your spline mesh components as well, but I need to double check that works.
@@unrealitybites763 Yeah I'm moving to 5.3 soon and nanite on splines is one of the things I was waiting for, so I hope it actually works :D
Packed levels would not work well on terrain of unknown shape and size generated at runtime. A big set of buildings on a plane won't work in a hillside city.
So what would be more efficient, using PCG or Blueprint for that wall generation?
What is the reason for using packed level actors instead of level instances?
I did mention this briefly in the video but the difference is that Packed Level Actors are for static meshes ONLY and provide the instancing of the meshes (hence the Packed), whereas Level Instances can also contain functional assets such as blueprints and do not give you the benefits of instancing.
Works for making static mesh foliage?