Hi,
With Destructibles, you shouldn’t be seeing any hit when it’s not fractured, and this is what I’m seeing when I’m looking at my scene when I create several different ones (0, 25, 250, and 1000 chunks) and add them to the scene.
Everything is looking as I would expect. The biggest hit I get is when I simulate for one and have it fracture the rest that are placed because then all the chunks are there and being dynamically rendered. You have to keep in mind as well that APEX Destruction and Cloth (Nvidia tech) is all handled on the CPU and not the GPU. Most the hit likely from your GPU is coming from lighting and the draw calls from so many chunks.
If you’ve not already I would suggest starting with the documentation on GPU/CPU profiling for a more in-depth breakdown of what’s happening in your scene:
- Timing Insights in Unreal Engine 5 | Unreal Engine 5.1 Documentation
- Timing Insights in Unreal Engine 5 | Unreal Engine 5.1 Documentation
Once you have a better breakdown feel free to post back here where the hang up is happening, but with destructibles, I would expect to see what I’m seeing in my scene which is Depth 1 is low cost because it’s simple geometry (I’m using the Template_Floor.uasset btw), and when it fractures, whether the entire mesh breaks apart or not, Depth 2 replaced Depth 1 and is always rendered. Whether the mesh is broken apart full or not, these chunks are being dynamically lit and rendered as part of drawcalls for your scene. If the DM has a lot of chunks this will add up.
So at the moment, from what I have put together I’m seeing behavior I would expect.
-Tim