OTOY Forums

lamloops wrote: Mon Mar 30, 2026 11:09 pm This link works fine - viewtopic.php?t=85487

but not this one

viewtopic.php?t=85488

Sorry, laamloops, I used the wrong link in the original post. Thanks for reporting this, now it's fixed.

getting an error telling that i ran out of GPU memory when using curvature node while using texture displacement.
is this a known bug/limitation?

marcikola wrote: Tue May 05, 2026 3:52 pm getting an error telling that i ran out of GPU memory when using curvature node while using texture displacement.
is this a known bug/limitation?

Heyo!
I am not aware of a bug like this - but I will have a look here in a bit.
Does this happen when your ram is still very empty?
Are there any other errors in the Houdini console ouput?

yea, it's not heavy scene, only about 3gb vram are used.

houdini gives this error:

*** OCTANE API ERROR: CUDA error (700) on device 0: an illegal memory access was encountered
*** OCTANE API ERROR: -> failed to launch kernel(kernel37)
*** OCTANE API ERROR: device 0: path tracing kernel failed
15:55:13 ERROR: [qt5 image] --------- Rendering failure. Unable to continue

another bug: when using vellumpostprocess and changing the Spatial Blur slider while having the IPR rendering, it almost crashes.

marcikola wrote: Wed May 06, 2026 1:59 pm yea, it's not heavy scene, only about 3gb vram are used.

houdini gives this error:

*** OCTANE API ERROR: CUDA error (700) on device 0: an illegal memory access was encountered
*** OCTANE API ERROR: -> failed to launch kernel(kernel37)
*** OCTANE API ERROR: device 0: path tracing kernel failed
15:55:13 ERROR: [qt5 image] --------- Rendering failure. Unable to continue

another bug: when using vellumpostprocess and changing the Spatial Blur slider while having the IPR rendering, it almost crashes.

Just tested in 2026.3 and definitely works fine there.
Not sure if it's fixed in the latest core build, or if it's some scene specific error - in which case it'll be hard to figure that out without a test scene.
If you can provide that I'd be happy to test it and see if I can figure out what's going on.

When you say "almost crashes" what do you mean with that?

Also happens with texture displacement only. On super simple scenes, its just a cube with a texture used as displacement.

Hmm tbh this sounds like this could be a nvidia driver issue.
Try downgrading to a 581.x driver as the 59x drivers have had some issues
If you can share a scene file that has this issue that would also be helpful that way we can isolate if it's a general octane bug, to do with your scene or an issue with your system (could be caused by drivers, bad GPU power cable...)

i already use 581.29..

marcikola wrote: Sun Jun 07, 2026 5:46 pm i already use 581.29..

Good to know - not it then.
Could you share an example file of the bug you're encountering?

yes sure, its attached!