OctaneRender 2018 for Modo [OBSOLETE]

[face_off]

I've tried both versions on the top of this page.

Do you have an All-Accesses subscription? I think this is something you will need to handle via a ticket with OTOY. Sorry I can't be more help.

Paul

[OlaHaldor]

I'm confused. There's only subscription based downloads for the latest build, and an older one for the 'old license type'. Will there no longer be any builds for the old license type?

[funk]

Octane has moved to subscription only for future releases. They allow you to use 4.x perpetually after a subscription expires though

I'm not too happy about this to be honest. There was some talk about adding perpetual access for those who subscribe 3 years in advanced, but no final word if that's happening.

viewtopic.php?f=7&t=69646

*For 3 year passes, we are planning to support a rent-to-own system that let's you keep using versions after V4 (at minimum 2018.1 now in beta), with limited support and online features and only for your purchased licences. (see below)

[OlaHaldor]

WHAT!? Such... bull... Everything is becoming subscription it's getting hard to keep up and maintain.

[OlaHaldor]

Any news on UDIM for Octane in Modo though?

[face_off]

Any news on UDIM for Octane in Modo though?

I hope to have it implemented in the next month or so.

Paul

[vantrum]

Hi Paul,

I'm experiencing the CUDA 700 error, and can't get octane to initialize in Modo. Initially I fixed this issue by rolling back to driver 417, which worked, but led to other system instability. Misunderstanding some forum threads, I purchased the enterprise subscription in order to get access to Octane 2018.1 - thinking it had resolved the nvidia driver issue. It didn't fix the issue, I'm still getting the cuda error with the nvidia 'creator' drivers.

What's my best option here? Is it still to revert to old nvidia drivers and wait for improvements? There's a variety of conflicting reports on the forums, so I'd be satisfied to simply know the actual state of the bug. Thanks so much for your help!

-Matt

modo 12.2.2
OctaneRender Enterprise 2018.1 (5000010)
windows 10
64gb ram, rtx2080 8gb, nvidia driver 419.67

[Goldorak]

Octane has moved to subscription only for future releases. They allow you to use 4.x perpetually after a subscription expires though

I'm not too happy about this to be honest. There was some talk about adding perpetual access for those who subscribe 3 years in advanced, but no final word if that's happening.

viewtopic.php?f=7&t=69646

*For 3 year passes, we are planning to support a rent-to-own system that let's you keep using versions after V4 (at minimum 2018.1 now in beta), with limited support and online features and only for your purchased licences. (see below)

The 3 year rent to own plan was a compromise solution for users who really wanted a perpetual licences at any cost for at least 2018.1. We offered it on Black Friday for $599 and those users that bought it now have a 2018.1 perpetual licence, and will get 2019.1 once that is out too . Now that we are well into 2019.1 (V6) and 2019.2 (V7), we feel we can offer a more fleshed out and targeted rent-to-own plan covering 2019.x. which we plan to lock down after the stable release of 2019.1 on the shop page.

[face_off]

I'm experiencing the CUDA 700 error, and can't get octane to initialize in Modo. Initially I fixed this issue by rolling back to driver 417, which worked, but led to other system instability.

I am not aware of any other users having this problem on Nvidia drivers 419. I suggest trying to reproduce the issue on Octane Standalone - and then if re-produced, report to OTOY. Also make sure you have a good enough power supply, and if rendering with multiple cards, try each card in isolation. Also try trying off the denoiser (if it's on).

Paul

[Fredrikvictorhugo]

Can somone test if you can save animations in the latest enterprice build.
I can't save animations anymore.
The frames won't save.

/Fredrik