Are Hierarchical Instanced Static Meshes Still Relevant?

Development World Creation
, , , ,
1

I wanted to see if anyone here knows, is it still relevant to use Hierarchical Instanced Static Meshes in a scene using World Partition and Nanite? Say I have some building components in a Blueprint…They are Nanite, would it make sense to set duplicate parts up on an HISM component?

Also how do you read the Nanite->Instances Visualizer? Everything seems to be a different color or shade…even when I have them setup on an HISM…I can’t tell what the colors mean or if that is relevant at all given how there is no mention in the documentation as to how to properly read the Visualizers…

In this image you’ll see 2 sets labeled 1 and 2…these are setup on Hierarchical Instanced Static Mesh Components…and yet they are still different colors…Intuitively I expected that this would show shared colors for those parts that are instanced. But they are all different colors…

image
image2121×1191 219 KB

One more thing in case anyone knows anything about any of this…because I can’t find any information on how HISMs work with World Partition anywhere on the Net…would it make sense to manually Instance meshes in my world if I am using World Partition…I know it uses HLods but I have no idea how those actually work…no one has really explained that system yet…

2

There’s a lot of question here. Something I can tell you, it’s not cool to just change everything to Nanite and never worry about instancing and LODs again.

Until recently, I had a GTX1050, and doing anything with Nanite was like blowing the back off the machine with a shotgun.

A lot of people out there, still have sub 1000 cards, so it will be even worse.

It really depends who you’re targeting.

1 Like