Out Of Core

 

Out Of Core textures let you use more textures than what would fit in VRAM by keeping them in RAM. This means that as the CPU accommodates requests to access the host memory, CPU usage increases and any RAM occupied with out of core textures is not available to other applications. The Out Of Core attributes are accessible from the Out Of Core rollout in the Octane tab of the Render Settings window.

Out_of_Core_Fig01_MAYA_v2022.jpg

Figure 1: Accessing the Out of Core attributes in the Render Settings window

 

Note: OctaneRender’s Out Of Core settings are for textures, not Geometry or render buffers.

When using out of core textures on slave nodes with the Octane Network RenderingThe utilization of multiple CPUs or GPUs over a network to complete the rendering process. feature, you also need enough RAM for the slaves. For net render slaves, you can specify the out of core memory options while installing the daemon. When specifying this for the slaves, enter the out of core memory amount in bytes, not Gbytes.

For example, if the master is rendering a large scene that has texture climbing up to 6 GB, the out of core memory amount to specify for the slaves during the installation of the slave daemon would look like this:

octane_slave.exe --net-master-address 192.168.xxx.xxx --net-master-port 21000 --out-of-core 6442450944