Rendering the side of a mountain. Model is about 700MB 6 x 16K textures on simple Octane Diffuse Material.
All Geometry and Geometry shape nodes have force load disabled. There's only 6 meshes in the scene and one camera, one env map (2K) and one Octane Light.
Notice How my memory mounts over time. I can only reder 6 frames without have to stop the render and restart.
Is this a memory leak?
When I batch render, the memory level drops when I stop the render.
When I Render Sequence the memory level never drops and you have to restart Maya to render more than 6 frames.
Memory maxes out
Moderator: JimStar
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
The plugin does not manage the GPU memory load - this is done by Octane rendering engine. The plugin just builds the Octane's native nodegraph in the CPU memory, and then just switches the frames. And this is the Octane rendering engine that is loading/unloading the frames' data to/from GPU memory...
But I can check just in case to be sure it's not some plugin-side issue, if you give me this scene you are testing with.
Do you use the "frames to pre-cache" in the plugin or you have it set to "0"?..
But I can check just in case to be sure it's not some plugin-side issue, if you give me this scene you are testing with.
Do you use the "frames to pre-cache" in the plugin or you have it set to "0"?..
Thanks for the quick response.
Frames to precache is set to 0.
here's a scene for testing with a set of 8K textures
https://drive.google.com/file/d/1UcJsEy ... sp=sharing
Oh yeah, I'm using 2020.1 XB2
Maya 2020
on a PC
Frames to precache is set to 0.
here's a scene for testing with a set of 8K textures
https://drive.google.com/file/d/1UcJsEy ... sp=sharing
Oh yeah, I'm using 2020.1 XB2
Maya 2020
on a PC
Yes as I can see this is a rendering engine issue. I've told about it to the engine team, they said me they will have a look into this when they have time.
So if the XB3 does not fix this for you (going to release it soon) - then you'll need to wait before this gets fixed by the rendering engine team (and probably be reminding about it in the standalone section).
As a workaround for today - you can try to switch on the "out of core" functionality and see if this would work any better for you...
So if the XB3 does not fix this for you (going to release it soon) - then you'll need to wait before this gets fixed by the rendering engine team (and probably be reminding about it in the standalone section).
As a workaround for today - you can try to switch on the "out of core" functionality and see if this would work any better for you...