Stoke partitioning in a separate path

Hello,
Is there a reason Stoke partitions in a separate path than the base one in the modifier? I’m pasting it in all the time :slight_smile:

Are we talking about the Deadline submission or Workstation partitioning?
For Deadline, it should be obvious why.
For Workstation, the Partitioning script asks the object for its path, but uses a slightly different prefix for the file name. If it is not working as expected, please explain.

You mean, it’s obvious because the one is on the network? By default, it’s all on the network here :slight_smile: I didn’t understand the reasoning for the different prefix folder too, but I guess it’s for a good reason.

The $default path used by Stoke objects by default (DOH!) points at the local user’s folder which tends to be on C:. So if you created a bunch of Stoke objects without customizing their base path (or setting the default to be something else), all your Stokes would write to C:. That’s why the Deadline submitter allows you to specify a Network location that all Slaves could see that is not on a local drive without having to change all Stoke objects’ settings.

Fair enough :slight_smile: I’ll look into writing a custom partitioning tool for us. Looks like lots of Stoke in our future!