Clients don't care that I've missed the deadline because the octane license server was down and I couldn't render the job. Simply not acceptable when there seems to be no option to get the licences to be local and not online. We need the local licences back and quickly.

Thank you for the clarification.

Hi Paride,

just to be clear. The RTX cards don't work on V4 even without using RTX ON is that it? They will simply not render?

Or will they render but with RTX turned off?

Cheers

Hi, I have this weird new bug where if both "quick update" and "lock update" buttons are switched off, the render runs in crazy loops and never really stops rendering. But if one of those buttons is on, then renders normally. I have the vague idea I've seen this bug before on an early version of ...

is it just with me or this version simply does not save the elements with the render? Tried in both max 2014/2017. Quick fix for this please.

Is it just with me or there is a gap between rollouts on the latest version (see attached image)?

Hi Paride,

yes, if I open my Octane V2-scenes first and let Octane convert the whole scene, then the conversion works. Afterwards I can save the file (which is now Octane V3) and merge objects from the scene into new scenes.

But as I noticed today: the same problem still occurs with opening one ...

This is what I got from Itoo Software regarding edge mode for Octane:

"Unfortunately, because of several technical limitations (mostly due to GPU based algorithms of this render engine) it's not possible to implement support for such feature as the Edge Boundary Checking mode. Thanks for your ...

Thanks for thumbs up on this. Unfortunately I have one bad eye and can't see the stereo, hence being just one image.
I didn't have much time to spend on this and the image is only half way there. My idea was to make it look like a real underwater experience with a bit of a surprise to spice up ...

I'm guessing here that if you have a large number of gpu's on one image you'll get severe bottlenecks over the network. When rendering with only 3 extra network gpu's, on large(ish) images (ie: 3k and above) the network gpu's stop processing every time they have to send/receive data from the master ...