OTOY Forums

aoktar wrote: 1-No. Please share your experience.
2-On next builts.
3-No. It depends to topology and complexity of faces. Be careful while changing values. It's heavy effect for cpu.

1- I fixed it quitting and re-loading C4d. Don't know what happend. Il'll test it longer and will send a scene will it happen again.
2- Fine. Is there an ETA on this? Would need to know for planning purposes and decide to start with 3.0.8 or old 3.0.7 a new project.
3- Thank you, I did not realize it was so heavy on cpu. I'll test it with 3.0.7 I have the impression it was faster. Could otoy inspire from surface-spread which has the same option but is really fast?
Octane spread is amazingly fast and surprises me how it can handle millions of clones, I use it mainly for vegetation and keeping away trees is a necessity. As I said I used it with cubes the same size of trees (to keep polygons down) as placeholders, planning to replace them with the real tree in the final render, still it is extreemly slow.

Not criticising, just seeking informations thank you for your work

All those solutions are fine of course if it would be a single project use material. But most of us have a library for use in multiple projects. And the annoying thing is it will probably change again in the future or as soon as v4.

jelly wrote:

aoktar wrote: 3- Thank you, I did not realize it was so heavy on cpu. I'll test it with 3.0.7 I have the impression it was faster. Could otoy inspire from surface-spread which has the same option but is really fast?
Octane spread is amazingly fast and surprises me how it can handle millions of clones, I use it mainly for vegetation and keeping away trees is a necessity. As I said I used it with cubes the same size of trees (to keep polygons down) as placeholders, planning to replace them with the real tree in the final render, still it is extreemly slow.

Not criticising, just seeking informations thank you for your work

I don't think it's different on 3.07, because there's no change. And it's not an Otoy thing, add-on of C4D plugin. It's just using scatter node of core to clone objects at depth level. High part is in plugin.

Hey guys, thanks for the update.

Is the denoiser available ? I didn't find it

Hi omegear,
the denoiser will arrive with v4 beta plugin, just a bit of more patience.
ciao Beppe

Hello,
Since 3.08 I have many bug, octane is slower.
Today Have a crash when change texture while live viewer working.
Can you help me ?
c4d r19
Thank you
Started logging on 09.05.18 10:47:47

OctaneRender 3.08 (3080015)

Could not load 'C:\Users\cmitt\Desktop\Work\1826\tex\LS05brn4.tif:rgba'.
Could not load 'C:\Users\cmitt\Desktop\Work\1826\tex\LS05brn3.tif:rgba'.
Could not load 'C:\Users\cmitt\Desktop\Work\1826\tex\LS05brn2.tif:rgba'.
Could not load 'C:\Users\cmitt\Desktop\Work\1826\tex\LS05brn1.tif:rgba'.
Could not load 'C:\Users\cmitt\Desktop\Work\1826\tex\LS05brk1.tif:rgba'.
Could not load 'C:\Users\cmitt\Desktop\Work\1826\tex\LS05brn1.tif:rgba'.
Could not load 'C:\Users\cmitt\Desktop\Work\1826\tex\LS05brn4.tif:rgba'.
Could not load 'C:\Users\cmitt\Desktop\Work\1826\tex\LS05brn3.tif:rgba'.
Could not load 'C:\Users\cmitt\Desktop\Work\1826\tex\LS05brn2.tif:rgba'.
Could not load 'C:\Users\cmitt\Desktop\Work\1826\tex\LS05brn1.tif:rgba'.
Could not load 'C:\Users\cmitt\Desktop\Work\1826\tex\LS05brk1.tif:rgba'.
CUDA error 700 on device 0: an illegal memory access was encountered
-> kernel execution failed(kernel25)
CUDA error 700 on device 0: an illegal memory access was encountered
-> failed to launch kernel(kernel34)
device 0: path tracing kernel failed
CUDA error 700 on device 3: an illegal memory access was encountered
-> kernel execution failed(kernel25)
CUDA error 700 on device 3: an illegal memory access was encountered
-> failed to launch kernel(kernel34)
device 3: path tracing kernel failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> kernel execution failed(kernel25)
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to launch kernel(kernel34)
device 2: path tracing kernel failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 0: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 0: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed

cmittenaere wrote:Hello,
Since 3.08 I have many bug, octane is slower.
Today Have a crash when change texture while live viewer working.
Can you help me ?
c4d r19
Thank you
Started logging on 09.05.18 10:47:47

OctaneRender 3.08 (3080015)

Could not load 'C:\Users\cmitt\Desktop\Work\1826\tex\LS05brn4.tif:rgba'.
Could not load 'C:\Users\cmitt\Desktop\Work\1826\tex\LS05brn3.tif:rgba'.

CUDA error 700 on device 3: an illegal memory access was encountered
-> kernel execution failed(kernel25)
CUDA error 700 on device 3: an illegal memory access was encountered
-> failed to launch kernel(kernel34)
device 3: path tracing kernel failed

CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 2: picking failed

CUDA errors are about some crashes on the renderer core in depth. There's several possible reasons. A bug on renderer or on driver or issues on gpus.

aoktar, I'm really enjoying the latest version but I'm still occasionally getting that unwanted behavior where Octane is switching the render kernel to "info-channels". It's happened now a few dozen times.

Iceman9 wrote:aoktar, I'm really enjoying the latest version but I'm still occasionally getting that unwanted behavior where Octane is switching the render kernel to "info-channels". It's happened now a few dozen times.

Thanks! It has been reported many times. I'll fix that if happens on me.

Sorry for offtopic, but any news about Octane 4.0 for C4D coming this year?