HISM and culling

[Neuffexx]

I want to use HISM’s to ensure that the actors in my level can maintain their individual LOD’s when I merge them, rather than ISM’s since as far as I am aware they will then all use one and the same LOD. (Correct me if that is wrong)

The question is, would that cause issues with culling as well when I merge all the HISM’s into one actor? Intuitively I would say ‘yes’, but I don’t really know how I can check if culling is happening in the editor or not.

Does anyone know?

[RecourseDesign]

Hi Neufexx,

You set the Cull Distance in your ISMC or HIMC - in the component itself:

[3dRaven]

@Neuffexx This thread might be of interest to you

Hierchical Instanced Static Meshes NOT occluding properly! What am I doing wrong?

@HeyMufti do you found a solution for this? Still getting no proper culling with Unreal 4.25 in 2020

FAQ: Rendering

FAQ includes content originally written for UDN. General: What are best practices for extending the rendering engine, preferably in a maintainable way? Avoid changing engine code and do everything you can in a plugin or project module. If there isn’t an API for a rendering change you want to make, work with us to add one.** What is the best way to switch between render techniques in application when using forward Rendering for VR but not all players are not exclusively using VR, such as …

“HISM creates clusters of instances. Culling, occlusion, and ‘lodding’ is done on a per cluster basis for HISM but is done on the Actor for ISM.”

[Neuffexx]

Thanks a lot for confirming that for me

[3dRaven]

I really wish they would implement a per instance occlusion culling for HISM’s, maybe GPU based one.
If you use the console command FreezeRendering then you can see what is occluded and what is left eating up GPU cycles.

[Neuffexx]

Yeah that would be great honestly.
Also good tip with the FreezeRendering, thanks!

[RecourseDesign]

There seems to be a bug in FreezeRendering - and HISMS do appear to be occluding ok: