Re: Cinema4D 2022.1-[R2] (Latest stable) (10.12.2022)
Posted: Sun Dec 11, 2022 10:33 am
freeter_e wrote:"noise - voronoi type" don't work on bump channel
( test in several versions: v2021.1.4-R4 / v2021.1.6-R6 / v2022.1-R2 )
OTOY Forums
Community Forums for OTOY Customers
https://render.otoy.com/forum/
Cinema4D 2022.1-[R10] (Previous stable) (26.03.2023)
Page 12 of 32
Re: Cinema4D 2022.1-[R2] (Latest stable) (10.12.2022)
Posted: Sun Dec 11, 2022 11:26 am
aoktar wrote:freeter_e wrote:"noise - voronoi type" don't work on bump channel
( test in several versions: v2021.1.4-R4 / v2021.1.6-R6 / v2022.1-R2 )
sorry，i don't understand. you mean octane standalone not support?
Re: Cinema4D 2022.1-[R2] (Latest stable) (10.12.2022)
Posted: Sun Dec 11, 2022 12:52 pm
It is same in standalone as you can see. If you see something doesn't work in standalone it is not a plugin related. Reported to core team.freeter_e wrote: sorry，i don't understand. you mean octane standalone not support?
Re: Cinema4D 2022.1-[R2] (Latest stable) (10.12.2022)
Posted: Sun Dec 11, 2022 1:10 pm
ok,thank you
Re: Cinema4D 2022.1-[R2] (Latest stable) (10.12.2022)
Posted: Sun Dec 11, 2022 1:33 pm
I can confirm the store render buffer comparison is not working correctly. In older scenes, it doesn't do anything or just shows black.
To make it work, I have to create a new scene and copy/paste all objects into it. Then it works.
To make it work, I have to create a new scene and copy/paste all objects into it. Then it works.
Re: Cinema4D 2022.1-[R2] (Latest stable) (10.12.2022)
Posted: Sun Dec 11, 2022 2:48 pm
Nope, just switch to any HDR buffer type then it will work. Problem is that cryptoMatteFalseColors=FALSE case is not working with LDR buffers and it's FALSE by default in tonemapping functions.dynaraton wrote:I can confirm the store render buffer comparison is not working correctly. In older scenes, it doesn't do anything or just shows black.
To make it work, I have to create a new scene and copy/paste all objects into it. Then it works.
Re: Cinema4D 2022.1-[R2] (Latest stable) (10.12.2022)
Posted: Sun Dec 11, 2022 4:31 pm
OK thank you, tested and working nowaoktar wrote:Nope, just switch to any HDR buffer type then it will work. Problem is that cryptoMatteFalseColors=FALSE case is not working with LDR buffers and it's FALSE by default in tonemapping functions.dynaraton wrote:I can confirm the store render buffer comparison is not working correctly. In older scenes, it doesn't do anything or just shows black.
To make it work, I have to create a new scene and copy/paste all objects into it. Then it works.
Re: Cinema4D 2022.1-[R2] (Latest stable) (10.12.2022)
Posted: Sun Dec 11, 2022 7:37 pm
Hey guys, I downloaded and updated to the above version for Cinema4d 2023.1 and also on my render node installed the latest version of it found on the downloads on otoy website. But my Cinema4D Octane Render network preferences says: Invalid Version (11.00.5 [0])
Did I install the wrong node / daemon version? If so can you point me to where I can download the latest? Or is there another issue?
Thanks for your help,
Silan
Did I install the wrong node / daemon version? If so can you point me to where I can download the latest? Or is there another issue?
Thanks for your help,
Silan
Re: Cinema4D 2022.1-[R2] (Latest stable) (10.12.2022)
Posted: Mon Dec 12, 2022 3:12 pm
there is this line: it comes from "denoise volume" But why?
Re: Cinema4D 2022.1-[R2] (Latest stable) (10.12.2022)
Posted: Mon Dec 12, 2022 4:30 pm
As I'm sure it's probably noted, the new light linking is a bit finicky for certain things. Especially hierarchy elements like an object used, then if a deformer added it breaks the connection. Same for a generator like a connect - if the hierarchy is under the connect it breaks but if under the geo it holds. Just wanted to note it from my findings. Thanks!