OTOY Forums

How does Octane lock both the standalone and plugin licenses to the machines they're installed on? I'm asking because, in trying to track down bugs, the licensing/activation hoops I have to jump through is getting silly and frustrating.

I cannot use different versions of the host app or different OS's without having to login to OTOY's website to deactivate both standalone and plugin licenses each and every time I switch, on the same computer. If I move from MODO 701 to 801, I go through this. If move from OSX to a BootCamp partition, same thing. So I have 701 and 801 installed on both OS's to help the developer isolate whether it's a MODO bug, an Octane bug, or a plugin bug, and this licensing model is becoming a real pain.

Is there a way to node lock the license to an actual node (computer) instead of locking it to a specific installation on a specific partition?

John, I have a PC which I can boot to Win7, OSX or Linux - and the one OctaneRender Standalone works for all 3, and the on Modo plugin license works for all 3 - however I did need to re-authenticate the same licenses in ll 3 environments - but no need to de-activate via the Otoy website. So in this situation, Octane thinks all 3 environments are the same PC.

Bootcamp may be different - and Octane may think that is a different PC - resulting in the need to de-activate via the Otoy website.

If Modo 701 and Modo 801 is installed in the same environment, the one Octane Standalone and Octane Modo plugin license will work on both (assuming they are the same version of the plugin and Standalone - ie. both 2.06).

Hope that helps a little.

Paul

Thanks Paul. Didn't get a chance to try it right away.

The 701/801 thing on OSX is correct so far. Just needed to re-enter my credentials.

However, I wiped Boot Camp and setup my Windows installation as a separate hard drive in my machine, but no luck. If I authenticate there, I can't authenticate in OSX. Frustrating.