Before installing the OctaneRender for Modo kit, we recommend installing OctaneRender Standalone Edition first. This is particularly important on Windows, since the Standalone installer adjusts registry values to help prevent graphics driver timeouts.
|
Exiting or closing the application |
Signing Out |
|
|
Standalone Edition |
Releases the Standalone license key, except when there is a plugin edition that is also open and still bound to that Standalone license key. |
Releases all OctaneRender® license keys bound on that machine. If other OctaneRender® instances are still running, you will be asked to close them before it can sign out and release all of the licenses. |
|
Plugin Edition |
Releases the license keys bound to the plugin. This includes the Standalone license Key, unless the Standalone edition is open or other plugins are open and their keys are still bound to the same Standalone license key on the same machine. |
Releases all OctaneRender® license keys bound on that machine. If there are other instances of OctaneRender® still running, you will be asked to exit those before it can sign out and release all OctaneRender® licenses. |
OctaneRender® requires authentication with its designated license key and requires internet access on its initial launch. OctaneRender® requests your OTOY® credentials and attempts to retrieve an available license from the OctaneRender LiveTM server.
OctaneRender® requires one available Standalone license on OctaneRender LiveTM, while plugins require one available standalone license plus one available license for that specific plugin. Standalone licenses are bound to one machine, which means you can share the Standalone license across multiple plugins running on that machine. You can also run multiple instances of Standalone or a plugin on a single machine using the same license.
Closing the application releases the OctaneRender® license, similar to a floating license scheme. Standalone edition just releases the standalone license, while plugins release both Standalone and their respective license. In either case, licenses are released if there is not another instance of Standalone or a plugin making use of that specific license. Note the distinctions below between just closing the applications and signing out of the applications.
As indicated above, deactivation via the Octane live licenses administration page is not necessary as this is done automatically by the application. This lets you use OctaneRender® somewhere else without deactivating any licenses. Licenses in use by older versions have the Deactivate button next to them if you need to release the license.
If the application didn't close properly from a crash or other circumstances, there is a chance the license isn't released. If the same machine accesses the same keys, this is not a problem as the same keys are still bound. The problem arises when you use OctaneRender® on another machine, as the keys are still bound to the previous machine. In such cases, failsafe web deactivation unbinds the keys.
You need an internet connection before starting OctaneRender® for the first time in order for it to communicate with the OctaneRender® licensing system. When you start the application, this sign-in screen appears.
Enter your OTOY® account username and password, then click the Sign in button.
At this point, the single sign-on and licensing system pulls a valid license key from your account on OTOY's secure server.
If OctaneRender® detects a connection problem, make sure all communications use HTTPS (TCP port 443) for the following:
The above may require updating your firewall settings. If the issue persists, check your proxy settings. Refer to the HTTP ProxyAn object saved as a separate file with the purpose of being reused in larger scenes. This is used to minimize any addition to the total polygon count in the scene, especially if the scene requires the same object to appear several times. If used in conjunction with instancing, Proxies help keep very large scenes from reaching polygon limits and also keeps the relative file size of the main project file manageable. Support topic in this Standalone manual for more information.
After signing in, OctaneRender® keeps a session alive as long you run the Standalone or the plugin application on a regular basis. In most cases, you should not have to sign in to the OctaneRender® licensing system again. This session also lets you link your local installation to other OTOY® services like Octane Render Cloud® (ORCTM).
Offline authentication and offline licensing mode uses an offline license dongle to run your OctaneRender® applications.
For more information on Offline Licensing, please see the Standalone Authentication and Internet Access documentation.