@karistouf Another issue worth noting is layer compositing in Stride. I encountered a similar problem during compositing. I resolved it through comprehensive optimisation and, later, by disabling inactive layers from the render. This is a genuinely complex topic, and I’m not entirely sure myself how best to approach it.
If your application, for example, is already optimised at other levels, it’s worth looking into manipulating layers and disabling them from the render at a deeper level. It’s been a long time since I last did anything complex in Stride, so I can’t quickly recall all the nuances, but I do remember that there’s room for optimisation there too.
thank you @Yar, the rendering is already optimized with “in the field of view” function.
i think its more around my runtime calculating players (embeded sequencers in my “layers objects”) that something could be gained
