Page 3 of 10

Re: Cinema4D version 2020.2-RC6 (Release candicate) 29.12.2020

Posted: Thu Dec 31, 2020 2:32 pm
by WesCREAM
Slightly confused by the posts here, is the denoiser supposed to be working with 3090 cards in this version or not?

Re: Cinema4D version 2020.2-RC6 (Release candicate) 29.12.2020

Posted: Fri Jan 01, 2021 10:40 am
by divasoft
bepeg4d wrote:
divasoft wrote:HI. I constantly get crushes denoising process with RC6 release. Cinema just crush without any messages.
Please, try to export to Standalone 2020.2-RC6, and check if the issue with Denoiser is still present.
I have reported a couple of issues with Denoiser to the core devs, and should be fixed for the next version.

ciao Beppe
Yep, i still get crushes with standalone denoising. It's a core issue.

Re: Cinema4D version 2020.2-RC6 (Release candicate) 29.12.2020

Posted: Fri Jan 01, 2021 1:24 pm
by lanklaf
BiteDXH wrote:
aoktar wrote:Hi @bite, there shouldn't be a mistake for my side. It's working well if all related parameters set correct. Check intermediate parameters, they are a kind of language interpreter between two different colorspaces(from octane to OCIO)
Intermediate color space should be linear sRGB.Render setting OCIO color space really not work
The intermediate color space must be ACES if you want the correct ACES file.
Aces workflow setup:

- in Octane all (sRGB, Linear sRGB and ACES2065-1 textures) are automatically converted to ACES2065-1 or sRGB.
No IDT for textures required.
---

- Working space setup:
"CS = color space"
ACES2065-1
Image
Linear sRGB
Image
---

- Select LV ODT
Image
Image
---

- Octane cannot render in ACES CG, instead it renders in ACES2065-1 and converts it to ACES CG.
In Settings > Color Space, you choose the EXPORT color space, not the Working color space.
Image
---

Re: Cinema4D version 2020.2-RC6 (Release candicate) 29.12.2020

Posted: Fri Jan 01, 2021 2:50 pm
by BiteDXH
lanklaf wrote:
BiteDXH wrote:
aoktar wrote:Hi @bite, there shouldn't be a mistake for my side. It's working well if all related parameters set correct. Check intermediate parameters, they are a kind of language interpreter between two different colorspaces(from octane to OCIO)
Intermediate color space should be linear sRGB.Render setting OCIO color space really not work
The intermediate color space must be ACES if you want the correct ACES file.
Aces workflow setup:

- in Octane all (sRGB, Linear sRGB and ACES2065-1 textures) are automatically converted to ACES2065-1 or Linear sRGB.
No IDT for textures required.
---

- Working space setup:
ACES2065-1
Image
Linear sRGB
Image
---

- Select LV ODT
Image
Image
---

- Octane cannot render in ACES CG, instead it renders in ACES2065-1 and converts it to ACES CG.
In Settings > Color Space, you choose the EXPORT color space, not the Working color space.
Image
---
Thank you for correcting the process!I didn't realize that oc didn't need the idt process.

Re: Cinema4D version 2020.2-RC6 (Release candicate) 29.12.2020

Posted: Fri Jan 01, 2021 3:07 pm
by lanklaf
BiteDXH wrote: Thank you for correcting the process!I didn't realize that oc didn't need the idt process.
Unfortunately there is no documentation for ACES in octane,
but as for me, everything works just fine and is much more convenient and faster than, for example, in Arnold.
My only request is to add an ACES CG render and copy an OCIO tab from Camera Imager directly to Octane Camera:
Image
+ Make Custom LUT and Responce tabs work with OCIO, without enabling "force tone mapping".
Force tone mapping just ruins the image.

Re: Cinema4D version 2020.2-RC6 (Release candicate) 29.12.2020

Posted: Fri Jan 01, 2021 4:43 pm
by BiteDXH
lanklaf wrote:
BiteDXH wrote: Thank you for correcting the process!I didn't realize that oc didn't need the idt process.
Unfortunately there is no documentation for ACES in octane,
but as for me, everything works just fine and is much more convenient and faster than, for example, in Arnold.
My only request is to add an ACES CG render and copy an OCIO tab from Camera Imager directly to Octane Camera:
Image
+ Make Custom LUT and Responce tabs work with OCIO, without enabling "force tone mapping".
Force tone mapping just ruins the image.
Yes, the description document of oc has been lagging behind other renderers.

Re: Cinema4D version 2020.2-RC6 (Release candicate) 29.12.2020

Posted: Sun Jan 03, 2021 3:28 pm
by mikeflex
Can confirm c4d hard crashing on denoise, no error

S22.123
2080Ti + 1080Ti

Re: Cinema4D version 2020.2-RC6 (Release candicate) 29.12.2020

Posted: Mon Jan 04, 2021 10:53 am
by cannon126
Windows 10
NVIDIA Studio Driver 460.89
RTX 3090
C4D R23


Can confirm that Spectral AI denoiser works! (so far)
Working in LV and PV with GI_Diffuse as well as Pathtracting.

Rejoice!

Re: Cinema4D version 2020.2-RC6 (Release candicate) 29.12.2020

Posted: Mon Jan 04, 2021 1:18 pm
by SSmolak
There is error while using device peers after restarting LV window :
nvlink_error.jpg
This is related to Standalone too.

Re: Cinema4D version 2020.2-RC6 (Release candicate) 29.12.2020

Posted: Mon Jan 04, 2021 2:09 pm
by pxlntwrk
mikeflex wrote:Can confirm c4d hard crashing on denoise, no error

S22.123
2080Ti + 1080Ti
I dont know if it denoiser or not (no time to investigate), but multiple crash without error, log and backup. :o
i think its a core issue, I sometimes noticed the same behavior in Houdini and Standalone.
Tiring...