There's been some confusion about how to transition from Octane v2.x to v3.x, so in order to ensure a smooth change here we are giving you some guidelines:
- Fist things first: please take a look at the 3.0 new features post. There you'll find information about all improvements and changes already included in 3.0, including examples and description of new features.
- Note that the licensing system has changed to a floating licensing scheme which automatically releases the licenses in use when the application exits. Deactivation via the website still works but is limited to a maximum number of times as it's meant for emergency use only.
- You may check all currently available versions in the downloads archive page for either standalone or plugins.
- You may upgrade your V2 licenses here. Note that you may get standalone+plugin bundle deals and that you need to upgrade at least one standalone license to V3 to use either standalone or any plugin.
- Proxy support: Some users using Octane behind a proxy used to be able to authenticate against OctaneLive using a proxy exception. However, the new authentication system is load-balanced so it has no fixed IP address, rendering this workaround not effective anymore. We are planning to add native proxy support very soon but on Octane versions 3.00 and 3.01 you may circumvent this issue as follows:
Use offline licensing mode while activating using a connection that bypasses the proxy.
Force Octane to communicate to the proxy using a tool such as Proxyfier. - OSX authentication: Due to a bugfix introduced in 3.0, the same OSX machine will look as a different one from Octane 2.x and 3.x perspective. If you plan to continue using 2.x at the same time as 3.x you may come across a message such as this:
This means that the 3.x licensing system thinks the license is in use on a different machine, while it's actually the same one. To workaround this you'll need to follow these instructions:
Moving from 2.x to 3.x:
- Deactivate your Octane 2.xx plugin(s) license(s) via the specific plugin or your licenses page.
- Deactivate your Octane 2.xx standalone license via
File > Preferences > OctaneLive > Deactivateor your licenses page. - Run Octane 3.x again.
- If offline licensing was NOT used: There's no need to deactivate 3.x explicitly as licenses are released upon exiting. Just make sure all 3.x standalone and plugin instances are not running anymore.
- If offline license was used: Sign out via
File > Preferences > Account > Sign Out. On 3.0 you'll need to do this on every plugin and standalone, while 3.01 will deactivate ALL licenses in use on this machine. - Run 2.x standalone or your plugin and activate normally.