Troubleshooting

Stability Issues

If Modo crashes with the plugin installed, delete the MODO.CFG file in the System > User Folder (make a backup first).

Rendering

If you have multiple video cards, ensure SLI is disabled
If you have issues rendering with the plugin, try rendering with Octane Standalone. If Standalone is not working, you have a graphics card/driver or other hardware/operating system issue.
If the viewport renders black after upgrading from a previous version of Octane, your graphics card may have been disabled by Octane. To fix this, go into the Devices page of the plugin and re-tick “Active” for your video card.
If Windows becomes unresponsive when rendering large scenes, this is due to using the same card for Octane rendering and for your Windows display adapter. It is highly recommended that you have a separate card as your Windows display adapter (e.g. your onboard graphics card). If you are using one card, set the Render Priority to Low in the Octane Render Setup window.
If you get CUDA error 500, 700 or 702, you have an Nvidia driver issue (see above), and Windows configuration issue (see below), or a hardware issue (in which case, try underclocking your card, and monitor card temperatures with GPUThe GPU is responsible for displaying graphical elements on a computer display. The GPU plays a key role in the Octane rendering process as the CUDA cores are utilized during the rendering process.-Z).

NOTE: CUDA 702 errors can occur if Octane blocks your video card for more than the Windows timeout. Windows defaults to a 2 second timeout, however a 10 second timeout is recommended for Octane.
Installing Octane Standalone (.exe installer) will set the correct timeout automatically.

Advanced users can manually adjust the timeout in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers by setting REG_DWORD TdrLevel to 3 (Decimal) and TdrDelay to 10 (Decimal). See TDR Registry Keys for more details.

Logs

If you have a problem, check the following logs:

Modo Event Log - General plugin errors will be logged in the Modo Event Log, which can be found under System > Advanced > Event Log.
Octane Log - The Octane log will contain errors related to devices and the internal Octane core. It can be accessed using the Render Toolbar > Log button.

Open topic with navigation