Max draw distance for Hierarchical Instanced Static Meshes?

Development Asset Creation
, , ,
1

It looks like there is a maximum draw distance for Hierarchical Instanced Static Mesh components.
This distance looks like it is related to the imported size of a mesh.

I set up a test case where I created an Hierarchical Instanced Static Mesh component.
I added 2 instance members.
One located at 0, 0, 0 with a scale of 20
The other located at 25000, 0, 0, with a scale of 50.

This is how it looks like:

80676-hismculling.gif

The second mesh is being culled away because of it’s distance to the camera.
If I change the mesh with a bigger mesh (Bigger scale on import) the cull distance will increase.

Is this expected behaviour? It looks like a bug to me.

Screenshot of the properties (Setting the mobility to static does not change the outcome):

80678-hismproperties.jpg
80678-hismproperties.jpg613×2336 201 KB

2

Bumping this thread because this is still an issue for me. Did anybody notice this before?

3

Hi Perfect_Storm, we experienced a somewhat similar problem in our project. As a temporary fix you can try lowering the value of “foliage.MinimumScreenSize” until you get your desired results.

4

Thanks for the help Cameron. I’ll try this today. At least there is a workaround so I can continue with the project.

5

This is an issue for us too. I know this is an older thread but did you guys find a permanent solution or did you just go with the workaround?