Understood, Paul.

Thank you for all your help!

Best regards,

Roy

I see - now for the kicker: would your Modo 4.05 plugin still work with my Modo 10.2v4 (on Linux)?

If not, I really am going to have to stick to 4.02.1, in which case - can I trouble you for the 4.02.1 build for Modo 10 (Linux) - I don't seem to be able to find it anymore!

Best regards,

Roy ...

Hello Paul,

I'm unfortunately a bit out of the loop as I haven't really been following recent Octane developments but was wondering, are the latest OctaneRender 4 for Nuke builds compatible with version 4.04?

I have a permanent Octane 4 licence and do not want to go over to the subscription model ...

Yes please, Paul - for Linux (mint 18.1) and Nuke 10.5v7.

With my thanks and wishing you a Happy New Year!

Roy

Hi Paul,

I realise v4 has only now officially come out and that you've been busy with the Modo plugin, but I just wanted a very rough estimate as to when you hope to produce a v4 plugin for Nuke...

Cheers,

Roy

********
Linux Mint 18.1 64bit
4.4.0-62 kernel
128 GB RAM
4x NVidia GTX 1080
NVidia ...

Thanks Paul.

I'll give the 390.48 driver a try then.

Roy

Hello Paul,

I'd like to update my setup to Octane 3.08 with the latest Nuke plugin, but I notice that you specify an NVidia driver of 392.x or later as a requirement. Is there any specific reason it has to be more recent than the 390.x driver you specify for your latest Modo plugin?

I ask because ...

Any chance of getting a Linux build, Paul?

TIA,

Roy

Hmm, I threw away the OctaneRender node in the script and replaced it with a new one and reloaded the scene. Now it's working - maybe it was a corrupt node.

I did check GPU VRAM usage though (8 GB is what I have available) - it's really not a heavy scene ...

Hi Paul,

Just updated to Nuke 10.5v2 and I'm getting a CUDA error from Octane now:

Started logging on 26.02.17 21:38:23

OctaneRender 3.05.3 (3050300)

CUDA error 2 on device 0: out of memory
-> failed to create context for pinned memory
device 0: failed to pin film buffer
device 0: detected an ...