Is Out-of-Core support not working in 2020 (octane)

Sub forum for bug reports

Moderator: juanjgon

Post Reply
pixelsmack
Licensed Customer
Posts: 112
Joined: Wed Jun 11, 2014 6:31 pm

I keep getting the same issues. Octane errors randomly. it's using 9GB of my 11GB. Then sometimes it gets through a bunch of frames and then sometimes it only gets through a couple. What REALLY odd is I have another scene that's TWICE the size of this one and it renders. Same exact content, just double of everything. So I don't even think it's a ram issue.

00:00:19 (0019.66) | <> Mem Used/Free/Total: 3127 / 5892 / 11264
00:00:19 (0019.66) | <> Triangles/DisplaceTris/Hairs/Objects/Voxels rendered: 2402678 / 0 / 0 / 2500033 / 0
00:00:19 (0019.66) | <> Textures RGB32/RGB64/GREY8/GREY16 used: 38 / 2 / 0 / 0
00:00:19 (0019.66) |
00:00:19 (0019.66) | ... Init rendering ...
00:00:19 (0019.66) * OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
00:00:19 (0019.66) * OCTANE API MSG: -> failed to create link
00:00:19 (0019.66) * OCTANE API MSG: device 1: failed to create OSL compile context:

00:00:19 (0019.66) * OCTANE API MSG: device 1: failed to compile module 0
00:00:19 (0019.66) |
00:00:19 (0019.66) | ++++++++++++++++++++++
00:00:19 (0019.66) | +++ RENDER FAILURE +++ processing the failure callback
00:00:19 (0019.66) | ++++++++++++++++++++++
00:00:19 (0019.66) |
00:00:19 (0019.66) |
00:00:19 (0019.66) | Aborting rendering detected
00:00:19 (0019.66) | >>> Refresh preview window
00:00:19 (0019.66) | >>> Draw preview window progress bar
00:00:19 (0019.66) | >>> Refresh preview window done
00:00:19 (0019.66) * OCTANE API MSG: CUDA error 700 on device 0: an illegal memory access was encountered
00:00:19 (0019.66) * OCTANE API MSG: -> failed to create link
00:00:19 (0019.66) * OCTANE API MSG: device 0: failed to create OSL compile context:

00:00:19 (0019.66) * OCTANE API MSG: device 0: failed to compile module 0
00:00:19 (0019.68) | ... Finish Rendering ...
00:00:19 (0019.68) |
00:00:19 (0019.68) | ... reset image callback ...
00:00:19 (0019.68) | ... wait for the getPreviewImage function ...
00:00:19 (0019.78) | Close and free scene, free buffer: 1, reset scene: 1
00:00:19 (0019.78) | ... freeBuffers
00:00:19 (0019.78) | ... setRenderTargetNode(NULL)
00:00:20 (0020.42) | ... update()
00:00:20 (0020.42) | ... getRootNodeGraph()->clear()
00:00:20 (0020.54) | >>> Refresh preview window
00:00:20 (0020.54) | >>> Draw preview window progress bar
00:00:20 (0020.54) | >>> Refresh preview window done
00:00:20 (0020.54) | Scene closed
00:00:20 (0020.54) |
00:00:20 (0020.54) | Close preview window
00:00:22 (0022.10) |
00:00:22 (0022.10) | Octane Render for Lightwave, end of log system
hkleton
Licensed Customer
Posts: 86
Joined: Wed Apr 06, 2016 6:17 am
Location: Netherlands

What Nvidia driver do you use?
After I installed the latest NVIDIAdriver,latest Octane 2020 and LW2020 all my problems like this disappeared.
I also had smaller scenes that would crash like this, and bigger scenes would render..and really huge scenes crashed again.
None of that anymore after all the new softwareversions.
pixelsmack
Licensed Customer
Posts: 112
Joined: Wed Jun 11, 2014 6:31 pm

I’m using the latest Studio driver. Which is quite out of date from the normal driver. What driver are you using?
hkleton
Licensed Customer
Posts: 86
Joined: Wed Apr 06, 2016 6:17 am
Location: Netherlands

Studio Driver 442.92 , 16/4/2020.
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

I think that this problem doesn't come from the lack of memory. It sounds to me like a bug or something like that. I'm still trying to reproduce the problem with the other scene.

Thanks,
-Juanjo
Post Reply

Return to “Bug Reports”