|
If OctaneRender® crashes upon loading a user created file, ensure that OctaneRender® and the drivers are installed correctly. To verify if the crash is caused by OctaneRender® or something that may be inherent in the user-created file, try also 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 recognises filenames containing spaces, and it should be able to use files with non-latin characters. An OBJ or MTL file containing special characters may be encoded in UTF-8. |
|
|
|
|
Problem: |
Incompatibility of previous version macros and OCS file format. |
|
Solution: |
Unfortunately, the only way to get around this is to recreate the macros or OCS file in the current version. |
|
|
|
|
Problem: |
Insufficient system or video RAM. |
|
Solution: |
It is recommended to use a 64-bit operating system with more than 4 GB of system RAM. Also, if possible use a video card with more than 2 GB of vram. For example, 2 GB 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, a video card with more than 2 GB vram might be necessary. |
|
|
|
|
Problem: |
Display Video Card is not active while CUDA enabled card is active. |
|
Solution: |
This may require swapping video card slots on the motherboard or changing bios settings so PCI-E slot with the display is "Initialized First". Review your motherboard documentation for the exact wording and location for this setting. |