Slaves not working in Batchrender Tweet

[danielsiegl]

Hey there!

I need some Help with my current Setup:

I try to render a Maya scene on a MacPro. I Setup 2 Slaves for this Job. The Master is the MacPro the Slaves are 2 Win10 PC's.
In IPR everythig works fine, but in the terminal batchrender the Slaves refuse to help! Only the Master is rendering. Maya is closed while batchrender.

Master: MacPro 12core 1x GTX 680 4GB
Slave 1: Win10 i7 32GB 1x GTX980ti 6GB
Slave 2: Win10 dual Xeon 64GB 6x GTX 780ti 3GB

And yes, I could start the render from a Win10 PC and it would work. But i want to keep working on my mac..

Thank you for you help!
Daniel

[BK]

Hi Daniel,

Which Octane for Maya plugin version are you running?
Are you able to see all the Slave daemon nodes from the Master's Octane render network preferences dialog?

While we are investigating, please try these options..

1. From the render settings dialog, enable "all available Slaves for batch".

2. Uncheck the "Enable Network Rendering" option from the Network render settings. This option will work for IPR only.

Now, save the file and it is ready for batch render. Please let us know how it go.

[danielsiegl]

Thank you!

It's getting better. But still no network rendering on my mac:
At least i got this message now:

"Octane: Starting in batch mode...
Network rendering is ENABLED:
Network GPUs in use: 0/0
Network slaves count: 0"

Still in IPR with enabled Network Rendering rendering everything works just fine.

:/

[BK]

Thank you, Daniel, for reporting this.

We have logged a ticket now, hopefully, we will come up with a fix soon.

[danielsiegl]

Thank you!

Sorry btw: OSX 10.12.5 Octane Standalone 3.06.2, Maya Plugin 3.06.2-11.6

Best!
Daniel

[BK]

Thank you, Daniel, for the info.

[danielsiegl]

Hey Guys!

Any news on this?

Thank you!
Daniel

[BK]

Hi Daniel,

Thank you for following up on this.

We have already lodged a ticket on our bug tracking system. For some reason, Maya OSX batch is denying to listen to the request from Slave node.

While we are resolving the issue, please try these options ? 1 - Using Octane Standalone, 2 - Using a network remote application ( VNC ).