This may be a silly question, but I am trying to drive the "framesperbatch" parameter on a TOP ROP Fetch with a PDG integer attribute that I define earlier in the graph. When I manually enter "20" or reference a channel that results in "20" from SOPs when evaluating in "Single Frame" mode on the same ROP Fetch, I get the range of workitems divided into jobs with ~20 frames each, as is desired. When I drive it using the @ syntax to read my attribute (@test_batchsize in this case) I get many more work items. I've also tried defining this as detail attributes in SOPS and importing them using geometry import to see if there would any difference, but with the same result. I may be missing something obvious, but any help with enabling this kind of workflow would be really great. Thanks in advance!