In the current implementation, when the PRE_CULL event is triggered, the frustum matrix is not yet updated. This limits the usefulness of the event for implementing correct custom culling logic. As a result, developers are forced either to defer their calculations to a later stage or to recompute the required data manually, which duplicates the engine’s internal work and may lead to inconsistencies.

It would be beneficial to consider one of the following improvements to the API:

either update the frustum matrix before firing the PRE_CULL event so that it reflects the current camera state;

or introduce an additional event (e.g., POST_FRUSTUM_UPDATE or similar) that is guaranteed to be called after the frustum has been recalculated but before the culling process begins.

This would allow more efficient integration of custom algorithms (such as custom culling, LOD logic, or analytical checks), reduce redundant computations, and make the system behavior more predictable.