If OctaneRender® crashes while loading a file, make sure that OctaneRender® and the drivers are installed correctly. To verify that the crash is caused by OctaneRender® or something that may be inherent in the file, try testing a scene by loading the demo suite files from http://render.otoy.com/downloads/OctaneRender_1_20_DemoSuite.zip or the OctaneBench® scenes from https://render.otoy.com/downloads/e4/39/98/a6/benchmark_scenes.zip.

 

Problem:

Problems inside OBJ file such as stray edges, vertices, etc.

Solution:

Re-export the scene using different exporting options from the modeling program or export script.

 

 

Problem:

Special characters inside OBJ or MTL file.

Solution:

OctaneRender® recognizes filenames containing spaces, and it can use files with non-latin characters. An OBJ or MTL file containing special characters can be UTF-8 encoded.

 

 

Problem:

Incompatibility of macros and OCS file formats from a previous version.

Solution:

The only way to get around this is to recreate the macros or OCS file in the current version.

 

 

Problem:

Insufficient RAM or VRAM.

Solution:

We recommend using a 64-bit operating system with more than 4 GB of RAM. Use a video card with more than 2 GB of VRAM. Two GB of VRAM is sufficient for 6 million polygons with medium texture use and a medium render size. To render in larger resolutions, or to utilize more high resolution textures, you'll need more than 2 GB VRAM.

 

 

Problem:

Display video card is not active while a CUDA®-enabled card is active.

Solution:

This may require swapping video card slots on the motherboard, or changing bios settings so the PCI-E slot with the display is initialized first. Review your motherboard documentation for the exact wording and location for this setting.

 

 

Problem:

CUDA error 702 on device 0: the launch timed out and was terminated.

Solution:

This happens if the GPU code takes too long to complete. To work around this, increase the timeout for the TDR recovery system. Increase the default to 10 seconds or more for rendering heavy scenes.

The OctaneRender® installer adjusts the TDR upon installation, but you can manually make this adjustment. To adjust the TDR, run regedit and add following DWORD values:

HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\TdrLevel = 3

HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\TdrDelay = 10


NOTE

Take caution using regedit, mistakes may render your system unstable. Reinstall OctaneRender® using the executable installer to make sure that the timeout for the TDR recovery system is adjusted correctly.