Some problems about drive character mapping and environment

Hi, I have encountered some problems. For example, I have many projects in parallel. For example, project a needs to map / / server01 to the drive letter z: and use redshift2.5.48, and then project b needs to map / / server02 to the drive letter z: and use redshift3.0.54. Every time we render the project, we need to manually change the plug-in of maya on the machine to the corresponding version, and then change the drive letter mapping path. Sometimes it’s easy to forget to switch versions and paths.
I think there should be some way in deadline to automate these operations.
I need help. Thank you.

It might be an option to use a JobPreLoad script to perform the mappings.
But there is nothing out of the box to do this.
Sounds like an odd setup, though. Why not use different drive letters for different projects?

1 Like

Thank you for your answer. I’ll give it a try. Because all the jobs are outsourced, the folder may have the same name, so we have to store the assets separately.

1 Like