This is another bug-fix release to sort out a few issues that got noticed with the last version. In the next 1-2 weeks we plan to release a test build of 3.06 with new features and also some restructuring to address problems with CUDA 7.5 and 8.

abstrax wrote:the matte is only evaluate during path bounces and not during the direct light calculation, i.e. it doesn't throw a shadow and won't shade the emitter. That's currently a limitation of the kernel split we did for version 3.

@Abstrax,from your words this is not obvious that this V3 limitation is the reason of Shadow catcher not casting shadow, since this only happen when "alpha shadows" is enabled in kernel,and in V2, Shadow catcher always cast shadow even when "alpha shadows" is enabled in kernel.Can you confirm this ?

ShadowCatcherAlphaShadows.orbx

octane_2017-01-11_07-40-08.png

octane_2017-01-11_07-38-47.png

You do not have the required permissions to view the files attached to this post.

Just play around with last version of Octane for Blender with some existing scenes and noticed several issues:

The available videos cards are not available, I couldn't activate or deactivate them, Octane GPUs is empty.Sometimes, pressing F12 crashes but often nothing is happening, it stays on Render target-evaluation on server or displays Waiting for image and then stop the rendering without displaying anything.When by chance the available cards could be chosen in the interface, if I activate the 4 cards I have, it seems that only one is used.Again when by chance the 4 cards work together (can't explain why it works sometimes), I can see it by the fact that the samples per second increase when I add a card, the rendering speed is around 3-4 times slower than with the standalone version using the same scene.

... or displays Waiting for image and then stop the rendering without displaying anything.

Have you checked System Console? I think you could be out of GPU memory. Anyway worth checking console for messages.

Ok, I made some more tests and discovered a strange behavior.

I start the Octane Server then start BlenderOctane, Octane GPUs in the render panel is empty as if my cards weren't recognized, I press F12 to start the rendering and got the problem and indeed a memory problem is reported on one card in the console, the one with only 3Gb, though the scene worked fine with the previous versions.

I stop BlenderOctane and restart it, Octane GPUs in the render panel is fulfilled with my cards and this seems to be a constant behavior, I mean the first time you start BlenderOctane after starting the server, no GPU is recognized but it's fine the second time you start BlenderOctane , I press F12 and got the same issue.

I deactivate the problematic card, the one with only 3Gb and press F12 to start rendering with the GTX1070, the rendering is working fine and I got the image.

I stop the rendering, add the card with 3Gb and it works fine, no more memory problem.

Last Octane engine log entries:CUDA error 2 on device 3: out of memory -> failed to allocate device arraydevice 3: the device failed immediately after the recovery -> giving up and switching the device into error state

Stop Octane 4 Blender, restart it, load the scene, F12, render stop with no image and got this in the console :

Hi enricocerica, I cant reproduce missing cards at start with latest Blender for Octane on Linux.Did not check memory error yet.May you post in Blender Bug Report thread too, JimStar reply quiet fast and if he can reproduce error he fix fast too last few month.