Thank you for the clarification!
I’m working on a plugin for the prism-pipeline(open source vfx pipeline framework) and want to make a template starting scene that automatically links up to some pre-set output folders for various things (like geometry output, heightmap outputs, and bitmap outputs).
Essentially, I’m using Prism’s functionality to copy a template scene to a specific project folder. Then I build output directories to handle organization and versioning of individual world machine outputs
I have it all set up to write paths for various WM output devices, but that’s where I hit a roadblock.
I was planning to generate an automation script (that a user can run when loading the initial scene) to automate the hookup to the proper files on disk. I was hoping to use a string in an automation variable to drive a file path of a given WM output device.
My current workaround is to just write those paths out to a txt file for the user to copy-paste into the specific devices in WM, but it would be awesome to automate this process as well and reduce the potential for user error.
I can share some progress, of the plugin I’m making, in a little while - just need to make a user guide