if I set `ROP Fetch` node's `Frames per Batch` parameter other than 1, the node generates the work items based on the range attribute instead of the incoming work items. (Or at least, this is what I think it's doing..)
Here is what I'm trying to achieve:
- Write out a simulation with preroll frames. (I need the preroll frames for debugging the sim.)
- Filter out the preroll frames by `Filter by Expression`. (`@pdg_frames<$STARTFRAME` works just fine)
- Render an OpenGL preview without the preroll frames, but in batches larger than 1 to save on the startup time. (It's an OpenGL render, where it's not negligible.)
What happens is:
- `ROP Geometry Out` produces 240 work items.
- `Filter by Expression` filters out 48, remains 192.
- And here comes my problem: if batch size is 1 `ROP Fetch` stays with the 192, but if it's more than 1, then it goes back to 240.
Of course the last ROP Fetch is set to ‘single-frame’ mode.
Is it the intended behavior? Is there a workaround?
I can put a `Wait for All` before the last `ROP Fetch` and use ‘frame-range’ mode, but in that case the network waits for all the frames in vain.
Hope it makes sense and thanks in advance,
Mate