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.I've tried both versions on the top of this page.
Paul
Moderator: face_off
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.I've tried both versions on the top of this page.
*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)
I hope to have it implemented in the next month or so.Any news on UDIM for Octane in Modo though?
funk wrote: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)
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).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.
Users browsing this forum: No registered users and 3 guests