say you have a mesh for light stuff
and now you have a certain build that requires multiple of that mesh light so you obviously duplicate it .
NOW -
what SHOULD you do:
leave it as that even tho it now has more than 1 mesh object [but same ID] or combine those into 1 meshPart [with different ID ]
so bottom line - more of the same meshID or few of different meshID’s??
I suggest you research on Geometry Instancing
so re-using the same mesh is way better? even tho it can have more instances
‘the fewer different meshIDs, the better’?
Yes, that’s the recommended method
Depends on use case.
If model is stationary - better to reuse singular mesh.
But if it will moved, like BaBFT ships, then it would be much better to union them into singular mesh, so 1 part will be moved instead of 100.
It’s actually more efficient and better for memory usage to weld all of those parts to one anchored part and just move that part instead.
Still depends on their quantity. Even when they are assemblies, it’s easier to move 1 part than 100. Assemblies are just more performant to move than pivoting all that parts as model, but singular part will outperform that.
The way I’ve seen staff speak about moving objects with lots of instances seems to heavily suggest that moving a welded assembly should be just as performant as a singular part.
Even if moving a singular part is somehow even slightly faster than this, it feels like a needless micro-optimization at that point which only comes at the expense of additional memory usage due to practically duplicate meshes being stored.
THANK YOU
what about ‘enable fluid forces’?
should i DISABLE that property?
Don’t worry about it, especially if your parts are anchored. Keep it to automatic
