Stack/04 culling

[JucanAndreiDaniel]

Summary

Reworks distance culling to be band-based with hysteresis and lets NPC routines progress while meshes are unloaded.

Changes

• Shared base — common bounding-sphere/bucket plumbing moved into AbstractCullingDomain/AbstractCullingService.
• NPC culling — distance bands with hysteresis (no thrashing at the boundary); visible NPCs tracked in a HashSet; routine waypoints advance even while the mesh is culled, so NPCs are in the right place when they re-appear.
• VOB mesh culling — three near-identical wrapper handlers collapsed into one per-bucket closure loop.
• VOB sound culling — List + ToArray() replaced by a reusable doubling array (no per-update allocation).

How to test

• Walk toward/away from NPCs and confirm they load/unload at the band edges without flicker near the threshold.
• Leave an NPC's area, return after some time, and confirm it has progressed along its routine.
• Confirm VOB meshes and positional sounds cull correctly with no GC spikes.

[JaXt0r]

I don't know if that is correct. We need to check in Scene View when game is running. Turning around and see, if a Vob is getting invisible or stays. Because Frustum should be handled for static objects. But how about Items?

[JaXt0r]

I tested it. Works as expected. Thanks a lot. Less checks per frame are always appreciated. :-)

[JucanAndreiDaniel]

No more custom frustum, everything that is in range is left active but culled by unity itself. in scene view we can still see the vobs, but that's because the scene view is another camera.

But perhaps there is a case for truly static vobs (not interactable/movable/items) to be culled by custom frustum.

[JaXt0r]

Works like a charm. Performance improvements like this are always appreciated. 🙇