Is your feature request related to a problem? Please describe.
3428 moved processing of schedule scripts from backend to frontend. The previous implementation would provide, for each transform node, the union of the ranges of the elements comprising that node. This range is critical for culling tiles that cannot intersect the node, eliminating unnecessary processing and tile requests. Now, such culling is not performed.
Describe the solution you'd like
When loading a RenderScheduleState, query the ranges of the transform nodes from the backend, then use them for culling as in the previous implementation.
Is your feature request related to a problem? Please describe.
3428 moved processing of schedule scripts from backend to frontend. The previous implementation would provide, for each transform node, the union of the ranges of the elements comprising that node. This range is critical for culling tiles that cannot intersect the node, eliminating unnecessary processing and tile requests. Now, such culling is not performed.
Describe the solution you'd like When loading a RenderScheduleState, query the ranges of the transform nodes from the backend, then use them for culling as in the previous implementation.
Describe alternatives you've considered
Additional context