Alex Majewski

@racoonart From what I've read the first one makes you use X11 backend resulting in XWayland instead of Wayland. The second one disables XInput2, some exetension related to input handling.

From your description, you do need to use Wait for All.

ROP Fetch -> Wait For All -> ROP Fetch -> Wait For All -> ROP Fetch.

All the other settings you mentioned are irrelevant for your goal. Unless, alternatively, you set all your ROP Fetches to cook all frames in a single batch, it would achieve the same effect since there would now be a queue of single work items I suppose.

Previous node's work items are like a multiplier for subsequent node's work items. If you use Wait For All you bring work items back to "1".

A late response, but just in case somebody looks this up in the future, I'll answer.

You start your TOP network with a File Pattern TOP and use it to scan your folder for FBX files. It will generate a separate work item for every file it finds. It will create TOP attributes containing the directory, filename and extension.

You then create your SOP network and start it with a File SOP (and follow it up with whatever changes you need, polyreduce, etc). In that File SOP you set the input path to:
`@directory`/`@filename``@extension`


To test it, you can cook your TOP network and left-click one of the dots so it's highlighted. Your SOP network will now display that work item's geometry in the viewport. With a selected dot you can also middle-mouse click path parameters to temporarily expand those @ variables and see where they point to.

Now you can add a ROP FBX Output TOP node and select the final node of your SOP network you want to export, as well as provide the output path. In your case, it could be something like:
C:/outputdirectory/`@filename`.fbx


You then cook the ROP FBX Output TOP. And that's all there is to it.