branchrust_reboot/main/occlusion_culling_toggle_fix/batch_culling_fixescancel
5 Commits over 0 Days - ∞cph!
Wrap last MeshCull changes behind useDetailedRendererBatchCullingCheck convar for accurate a/b
Possibly fixed MeshCull objects not being affected by occlusion culling
Culling.env is no longer admin only
Added culling.skinnedRenderers, controls the player/animals culling system
Both culling.env and culling.skinnedRenderers require culling.toggle to be active, turning this convar off will turn both related convars off
Add graphics.useDetailedRendererBatchCullingCheck convar to test new behaviour, defaults to true
Would need to relog to see the difference
Allow MeshLOD and RendererLOD components to use the occlusion culling system if they have a RendererBatch component but the RendererBatch won't work (eg. not marked r/w, too many tries, etc.)
When standing at the edge of trainyard or outpost and looking directly at a wall (when you would expect the majority of assets to cull) this seems to cull a huge amount of renderers
Compound goes from 4.4m tris and 1347 SetPass calls to 2.2m tris and 829 SetPass calls
Trainyard goes from 5.5m tris and 1538 SetPass calls to 1.8m tris and 726 SetPass calls
MeshCull seems to be working correctly on paper but still seems to be rendering when I would expect it to be culled, so there may be more gains to be had here
