Page 2 of 2
Re: Blender Octane v3 - network render slave deamon crashes
Posted: Fri Sep 15, 2017 11:49 am
by hullo
To get it working within Blender: install and run Octane deamon on slave ( needs to be the same cersion as workstation )
After entering default values when installing most of the time it works. If deamon is running on slave -> Blender should automaticly detect the slave gpus.
Re: Blender Octane v3 - network render slave deamon crashes
Posted: Fri Sep 15, 2017 9:54 pm
by JimStar
kibbycabbit wrote:Aah?! How do you get network rendering to activate in Blender?
...
In Render tab, I can only see local GPU but no extra GPU from another slave. What other step do I need to do to get it to work?
You don't need to do anything in Blender - if you have Octane slaves running in your network (make sure they are of the same Octane core version), when you start rendering Blender will find them automatically and show you the network GPUs amount in a render's info-line on the top of the viewport.
Re: Blender Octane v3 - network render slave deamon crashes
Posted: Sat Sep 16, 2017 6:15 am
by kibbycabbit
Still no go. Maybe works fine on Windows environment? I'm using Blender on OSX and other machine running Windows + Octane daemon running.
Re: Blender Octane v3 - network render slave deamon crashes
Posted: Sat Sep 16, 2017 6:37 am
by kibbycabbit
I decided to try a development build (3.06.4 - 12.2). Voila, I see "Net GPUs: 2/2" Not sure why previous build doesn't work.
By the way, what's recommended Blender version for the development build?
Re: Blender Octane v3 - network render slave deamon crashes
Posted: Mon Sep 18, 2017 4:20 am
by azen
kibbycabbit wrote:I decided to try a development build (3.06.4 - 12.2). Voila, I see "Net GPUs: 2/2" Not sure why previous build doesn't work.
By the way, what's recommended Blender version for the development build?
Hi,
While the 12.2 version of the Blender plugin is still marked as a test build, the 3.06.4 branch of the Octane core renderer is considered stable. A number of issue with the previous version were resolved as part of the update to a stable 3.06 Octane core build.
If you do come across any other previous issues in the latest build, please let us know.