Hello,
I have a problem with renderings of render elements with deadline. While everything works fine locally, when I try to render through deadline some render elements in max9 (even to the local machine), it renders ok (framebuffer visible) but errors at the end with a save/directory problem. It looks for a temp directory on the local drive (c: docs & settings, myname, local settings, temp) which has nothing to do with the file save settings I indicated in the render element panel.
Is there something I should do differently when using render elements?
Tks for your support
Olivier
Hi Olivier,
Previously, our max plugin would save the file to the local temp directory first, then copy it to the final destination afterwards. That’s why you’re seeing the local drive in your error message. Can you post the exact error message you’re getting?
If we can’t resolve the issue, you may want to try using the update to the max plugin we’ve posted here:
http://support.franticfilms.com/wb/default.asp?action=9&boardid=2&read=444&fid=7
It saves the images directly to the final location instead of saving locally first.
Cheers,
- Ryan
Here is below the type of error message I receive. I am running on deadline 2.6.2479 (following some exchanges with Bobo a few weeks ago regarding a particular issue I had with tile renderings);
is the version that you pointed out more recent than that? Since I am in a middle of a production, can I deploy this with no risk? how should I proceed to install this set of files?
Failed to save C:\DOCUME~1\Olivier\LOCALS~1\Temp\plan2_matte-yeux0010.png: The system cannot find the path specified.
red on Production.6
2007/04/06 22:04:47 INF: JOB 0.6 progr: 94.0% rendered on Production.6
2007/04/06 22:04:47 INF: JOB 0.4 progr: 94.3% rendered on Production.4
2007/04/06 22:04:47 INF: JOB 0.6 progr: 94.5% rendered on Production.6
2007/04/06 22:04:47 INF: JOB 0.4 progr: 94.8% rendered on Production.4
2007/04/06 22:04:47 INF: JOB 0.8 progr: 95.0% rendered on Production.8
2007/04/06 22:04:47 INF: JOB 0.11 progr: 95.3% rendered on Production.11
2007/04/06 22:04:47 INF: JOB 0.5 progr: 95.5% rendered on Production.5
2007/04/06 22:04:47 INF: JOB 0.10 progr: 95.8% rendered on Production.10
2007/04/06 22:04:47 INF: JOB 0.18 progr: 96.0% rendered on Production.18
2007/04/06 22:04:47 INF: JOB 0.7 progr: 96.2% rendered on Production.7
2007/04/06 22:04:47 INF: JOB 0.4 progr: 96.5% rendered on Production.4
2007/04/06 22:04:47 INF: JOB 0.6 progr: 96.7% rendered on Production.6
2007/04/06 22:04:47 INF: JOB 0.8 progr: 97.0% rendered on Production.8
2007/04/06 22:04:47 INF: JOB 0.11 progr: 97.2% rendered on Production.11
2007/04/06 22:04:47 INF: JOB 0.11 progr: 97.5% rendered on Production.11
2007/04/06 22:04:48 INF: JOB 0.11 progr: 97.7% rendered on Production.11
2007/04/06 22:04:48 INF: JOB 0.11 progr: 98.0% rendered on Production.11
2007/04/06 22:04:48 INF: JOB 0.11 progr: 98.2% rendered on Production.11
2007/04/06 22:04:48 INF: JOB 0.10 progr: 98.5% rendered on Production.10
2007/04/06 22:04:48 INF: JOB 0.18 progr: 98.7% rendered on Production.18
2007/04/06 22:04:48 INF: JOB 0.7 progr: 99.0% rendered on Production.7
2007/04/06 22:04:48 INF: JOB 0.5 progr: 99.2% rendered on Production.5
2007/04/06 22:04:48 INF: JOB 0.8 progr: 99.5% rendered on Production.8
2007/04/06 22:04:48 INF: JOB 0.6 progr: 99.7% rendered on Production.6
2007/04/06 22:04:48 INF: JOB 0.4 progr: 100.0% rendered on Production.4
2007/04/06 22:04:48 INF: PHEN 0.3 progr: calling output shaders
2007/04/06 22:04:48 INF: RC 0.3 progr: rendering finished
This version is more recent than the one included with Deadline 2.6. We’re currently using this version in production, and other studios that have installed the patch haven’t reported any problems with it. Of course, it is recommended to make a backup of the old 3dsmax plugin, just to be safe, but we don’t anticipate you experiencing any problems.
Here are the installation instructions:
To install it, simply unzip the file and replace the 3dsmax9 folder in \your\repository\plugins (remember to back up the original, just in case). You might have to configure the plugin afterwards to ensure things like the executable path are correct. You can do this in the Monitor while in super user mode by selecting Tools -> Configure plugins.
Hopefully this patch resolves your problems. Since it’s saving directly to the final location, I would expect it to.
Cheers,
- Ryan
Yes, the new version has solved the issue. that’s a good thing.
Tks