Unity 6 implements strict validation to prevent rendering crashes caused by late renderer registration. Invoking ScriptableRenderContext.Cull() inside the Execute phase is no longer supported because the execution point occurs after the pipeline has finalized the list of visible objects for the frame.

To resolve this, culling logic must be moved to the AggregateCullingParameters method. This provides the correct injection point for the HDRP to aggregate culling requirements before processing the render list.

1. Open your custom pass class.
2. Locate and remove any calls to ScriptableRenderContext.Cull() within the Execute method.
3. Override the AggregateCullingParameters method to define how your pass should handle visibility.
4. Use the CustomPassContext inside the Execute method to retrieve the computed cullingResults instead of generating them manually.

Additional Tips

• The ctx.cameraCullingResults can be used if your pass depends on the main camera’s visibility set rather than a custom one.
• Ensure you call base.AggregateCullingParameters(ref cullingParameters, ctx) within your override to maintain default pipeline behavior.
• This shift to AggregateCullingParameters is mandatory for stability when using Terrain components in Unity 6.