OTOY Forums

I have refreshed the installers at the top of this thread with:

2.15.0.37
- Compiled with Octane 2.15
- Various additions/enhancements to emitters, including addition of "Surface Brightness" and "Cast Illumination" pin. See Octane 2.15 Standalone release notes for details.
- Removed ISO and FStop Imager pins. See Octane 2.15 Standalone release notes for details. Scenes saved with plugin versions prior to 2.15.0.37 will have the exposure converted to the new scale, however your default rendertarget "exposure" will not be converted - so you may need to adjust the default exposure and then "Save a Default"
- Added Polygon Side texture node (see Octane Standalone 2.14 release notes for details)

Paul

Oops... looks like my Titan card just fell over... with this new version...

Started logging on 14.12.14 14:43:36

OctaneRender version 2.15 (2150000)

CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to allocated device memory
device 0: failed to upload data texture 4 of context 0
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to unload module

I am trying to use procedural maps (noise, turbulence) to create displacement, but procedural nodes seem to have no effect when applied to displacement. A basic example would be to use procedural random dots to create a "furry" effect on a flat plane. I can do this by creating a random noise bitmap texture elsewhere, and then apply it to displacement, but not with procedural noise.

Does this require something different to work?

I am trying to use procedural maps (noise, turbulence) to create displacement, but procedural nodes seem to have no effect when applied to displacement. A basic example would be to use procedural random dots to create a "furry" effect on a flat plane. I can do this by creating a random noise bitmap texture elsewhere, and then apply it to displacement, but not with procedural noise.

Hi Ken - that approach will not work. Pls see the Octane Notes link in my signature.

Paul

Oh I see - Octane displacement only supports bitmap textures, so procedural nodes are being ignored. What a waste... Is this Octane or the Poser plugin's limitation?

Is this Octane or the Poser plugin's limitation?

An Octane (or potentially Cuda?) limitation.

Paul

Bummer, just when it's exactly these kind of maps that are critical for GPU rendering because of... CUDA limitations, too.

Alright then, thanks for the info, Paul!

Ken1171 wrote:Bummer, just when it's exactly these kind of maps that are critical for GPU rendering because of... CUDA limitations, too.

Alright then, thanks for the info, Paul!

It's not a limitation of CUDA per se, it's just the way how displacement works. To calculate the displaced surface on-the-fly it requires a rasterized height map and procedurals are too slow to calculate.

It's not a limitation of CUDA per se, it's just the way how displacement works. To calculate the displaced surface on-the-fly it requires a rasterized height map and procedurals are too slow to calculate.

If Poser can use procedural displacement (I use it all the time), why not Octane? If it's a CUDA limitation, then there's nothing that can be done about it.

Ken1171 wrote:If Poser can use procedural displacement (I use it all the time), why not Octane? If it's a CUDA limitation, then there's nothing that can be done about it.

I don't know Poser, but it probably just displaces geometry, but doesn't render micro-polygon displacement which is what Octane does. The latter requires very little memory, since only the base geometry is stored and the displacement map.