Hello,
I'm having some issues rendering image sequences using TOPs and Deadline:
I'm using a ropfetch in TOPs, which works fine as long as I render one frame per batch. (but that means one Deadline job per frame)
The issue comes when I check the "alll frames in one batch" option or if I increase the "frames per Batch" setting to something higher than 1 : I get an error in deadline : "Process returned non-zero exit code '1')"
I thought at first the issue might be from Houdini or Deadline, but when I do the same operation with Mantra, it renders all fine.
I've attached the working Mantra file and non working Octane file.
Any idea what that could be?
Thanks,
( I'v followed these instructions to set up PDG with Deadline:
http://www.sidefx.com/docs/houdini/node ... duler.html)
Houdini 17.5.229
Octane plugin 4.05
deadline 10.0.26.0
TOPs Deadline
Moderator: juanjgon
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
- Attachments
-
- octane_pdg.rar
- (10.46 MiB) Downloaded 192 times
Hmm, I'm not sure what could be the problem, but I can imagine that in the end if you are trying to render more than 1 frame per batch, the system could be trying to render two or more images at the same time using the same Houdini/Octane session, something that is not possible. Currently, a single Houdini/Octane process only can render one image at the same time, even if the plugin is running on hython.
Probably all this stuff has been designed for Mantra or other CPU renderers, that can launch several render sessions that the same time from a single process.
Thanks,
-Juanjo
Probably all this stuff has been designed for Mantra or other CPU renderers, that can launch several render sessions that the same time from a single process.
Thanks,
-Juanjo
Hi,
I see.. Mantra Renders one image after the other so I'm not sure what is Octane's behaviour..
but I've found a way to keep Deadline organised when using "1 frame per batch" if anyone is interested: use a Job Batch Name (screenshot attached)
Thank you juanjgon.
I see.. Mantra Renders one image after the other so I'm not sure what is Octane's behaviour..
but I've found a way to keep Deadline organised when using "1 frame per batch" if anyone is interested: use a Job Batch Name (screenshot attached)
Thank you juanjgon.
- Attachments
-