Hi coilbook,
do you mind to share the two vdb files, please?
ciao beppe
OctaneRender™ Standalone 3.06 TEST 4
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
i willbepeg4d wrote:Hi coilbook,
do you mind to share the two vdb files, please?
ciao beppe
By the way can you guys add slot for noise to Volume medium (for daylight system) that can be animated so instead of stationary fog we can have moving fog that looks like smoke of different densities. Not sure if it is possible
- FrankPooleFloating
- Posts: 1669
- Joined: Thu Nov 29, 2012 3:48 pm

So GTC has wrapped, and presumably Jules, Marcus & Co are back in the salt mines... Really hongry for some delicious piping hot 3.07 goodies fresh out of the oven... hopefully, it will be a banquet for the ages! Is 3.07 possibly coming this week?...
Win10Pro || GA-X99-SOC-Champion || i7 5820k w/ H60 || 32GB DDR4 || 3x EVGA RTX 2070 Super Hybrid || EVGA Supernova G2 1300W || Tt Core X9 || LightWave Plug (v4 for old gigs) || Blender E-Cycles
We are cleaning up the slides from both talks and merging them into a clean (and properly annotated) deck one now that we're back. We will share once that's done!FrankPooleFloating wrote:A tumbleweed just rolled by....
So GTC has wrapped, and presumably Jules, Marcus & Co are back in the salt mines... Really hongry for some delicious piping hot 3.07 goodies fresh out of the oven... hopefully, it will be a banquet for the ages! Is 3.07 possibly coming this week?...
- FrankPooleFloating
- Posts: 1669
- Joined: Thu Nov 29, 2012 3:48 pm
Should have said back in the kitchen, rather than salt mines. Oh well... Hey, thanks G! Now get off forums and get yer ass back in the kitchen!
Win10Pro || GA-X99-SOC-Champion || i7 5820k w/ H60 || 32GB DDR4 || 3x EVGA RTX 2070 Super Hybrid || EVGA Supernova G2 1300W || Tt Core X9 || LightWave Plug (v4 for old gigs) || Blender E-Cycles
- BorisGoreta
- Posts: 1413
- Joined: Fri Dec 07, 2012 6:45 pm
- Contact:
Protection against failed nodes is still not working !
Last 4 nights every night I set a sequence to render and in the morning I see it stopped somewhere in the middle. One of the nodes throws bunch of errors and this caused master computer and other nodes to pause rendering since master is waiting for an answer from the failed node. But there is no answer. All I have to do is close the octane node window on the failed node and rendering continues on the master and other nodes.
So, why does master wait forever for an answer from the node ? Why can't it wait for a reasonable amount of time and then call it dead and continue, or even better, restart the node by itself ( not entire machine, just Octane node DOS window ) ?
This is how it is since I started using network rendering and if you have 20+ GPUs there is always one in there which is bound to fail.
We need this timer protection !
Last 4 nights every night I set a sequence to render and in the morning I see it stopped somewhere in the middle. One of the nodes throws bunch of errors and this caused master computer and other nodes to pause rendering since master is waiting for an answer from the failed node. But there is no answer. All I have to do is close the octane node window on the failed node and rendering continues on the master and other nodes.
So, why does master wait forever for an answer from the node ? Why can't it wait for a reasonable amount of time and then call it dead and continue, or even better, restart the node by itself ( not entire machine, just Octane node DOS window ) ?
This is how it is since I started using network rendering and if you have 20+ GPUs there is always one in there which is bound to fail.
We need this timer protection !
19 x NVIDIA GTX http://www.borisgoreta.com
Can you confirm this is the case in non test release?BorisGoreta wrote:Protection against failed nodes is still not working !
Last 4 nights every night I set a sequence to render and in the morning I see it stopped somewhere in the middle. One of the nodes throws bunch of errors and this caused master computer and other nodes to pause rendering since master is waiting for an answer from the failed node. But there is no answer. All I have to do is close the octane node window on the failed node and rendering continues on the master and other nodes.
So, why does master wait forever for an answer from the node ? Why can't it wait for a reasonable amount of time and then call it dead and continue, or even better, restart the node by itself ( not entire machine, just Octane node DOS window ) ?
This is how it is since I started using network rendering and if you have 20+ GPUs there is always one in there which is bound to fail.
We need this timer protection !
Also, the limit is 20 GPUs and for good reason - if you are seeing more than that at once then this is a bug that should also be fixed, as it would likely impact stability.
- BorisGoreta
- Posts: 1413
- Joined: Fri Dec 07, 2012 6:45 pm
- Contact:
I am using 3.06 (3060005).
I was using 17 GPUs at the same time. I have 18 in total so I can't break the 20 limit count.
What is a good reason not to have more then 20 GPUs ?
I was using 17 GPUs at the same time. I have 18 in total so I can't break the 20 limit count.
What is a good reason not to have more then 20 GPUs ?
19 x NVIDIA GTX http://www.borisgoreta.com
BorisGoreta wrote:I am using 3.06 (3060005).
I was using 17 GPUs at the same time. I have 18 in total so I can't break the 20 limit count.
What is a good reason not to have more then 20 GPUs ?
i rendered with 21 GPUs fine (4 in master and 17 in slaves). Maybe 20 GPUs is a myth
That is pretty strange. 20 GPU should be the max you can load in at once. How many slaves were you running?coilbook wrote:BorisGoreta wrote:I am using 3.06 (3060005).
I was using 17 GPUs at the same time. I have 18 in total so I can't break the 20 limit count.
What is a good reason not to have more then 20 GPUs ?
i rendered with 21 GPUs fine (4 in master and 17 in slaves). Maybe 20 GPUs is a myth