Rendering deadline different projects loaded
Quote from pannekaka on 9. March 2021, 14:28Hello,
first of all i must say we really enjoy Prism, it's great for our size and quite easy to use!
But, we have a problem when we work on simultanous projects and render it throught Deadline.
We like to keep the render output path generated automatically from the tags used below:$PRISMJOB/03_Workflow/Shots/$PRISM_SEQUENCE-$PRISM_SHOT/Rendering/3drender/$HIPNAME/$OS.$AOV.$F4.exr
The problem appears then when a computer which has another prism project loaded, then renders the scene and outputs the images in the wrong project folder.
We have little to no experience with Python, cause we were thinking maybe convert the paths to absolute paths on submit to deadline.
Do you have any smart ideas to solve this?
-sondre
Hello,
first of all i must say we really enjoy Prism, it's great for our size and quite easy to use!
But, we have a problem when we work on simultanous projects and render it throught Deadline.
We like to keep the render output path generated automatically from the tags used below:
$PRISMJOB/03_Workflow/Shots/$PRISM_SEQUENCE-$PRISM_SHOT/Rendering/3drender/$HIPNAME/$OS.$AOV.$F4.exr
The problem appears then when a computer which has another prism project loaded, then renders the scene and outputs the images in the wrong project folder.
We have little to no experience with Python, cause we were thinking maybe convert the paths to absolute paths on submit to deadline.
Do you have any smart ideas to solve this?
-sondre
Quote from RichardF on 11. March 2021, 14:22Hey Sondre,
Are you submitting your renders to Deadline using the Prism State Manager or using the default Deadline ROP node?
When you submit a render using Prism to Deadline then Prism will set the outputpath for you. It will be an absolute path without any variables. Also Prism will add an environment variable to the Deadline job "prism_project", which the slave will recognize when rendering the job and load the same project, which was active during the job submission.
If you want to submit the jobs in a different way you could set the "prism_project" environment variable for your jobs or convert your path to an absolute path like you said. Both steps would require a bit python knowledge unless you want to it manually for every job.
I would recommend using the State Manager to submit jobs, because then everything is set up for you already.
Cheers,
Richard
Hey Sondre,
Are you submitting your renders to Deadline using the Prism State Manager or using the default Deadline ROP node?
When you submit a render using Prism to Deadline then Prism will set the outputpath for you. It will be an absolute path without any variables. Also Prism will add an environment variable to the Deadline job "prism_project", which the slave will recognize when rendering the job and load the same project, which was active during the job submission.
If you want to submit the jobs in a different way you could set the "prism_project" environment variable for your jobs or convert your path to an absolute path like you said. Both steps would require a bit python knowledge unless you want to it manually for every job.
I would recommend using the State Manager to submit jobs, because then everything is set up for you already.
Cheers,
Richard