Page 5 of 10

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

Posted: Wed Jan 06, 2021 6:24 am
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.
Hello, Lanklaf, I have another question. Now there is no problem with output linear exr according to your settings(ACES2065-1), but how to output jpg/png with tonemap?
I tried sRGB and ocio output-sRGB in the Render Settings, but the results seemed wrong.

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

Posted: Wed Jan 06, 2021 1:22 pm
by rschrem
Should texture compression option on an ImageTexture node should work in this release?
To me this seems to be broken / not working as expected and documented.

Whatever option I pick: the VRAM usage after reloading the scene does not seem to change at all.
Clearing the texture buffer using the menu option in the octane live viewer does not change anything as well.

In the matching version of standalone there is no texture compression option at all. If I create externally a DDS file using the Nvidia compression tool it seems to reflect correctly in VRAM usage in standalone.

When I reference the same DDS texture files that worked in standalone in a C4D ImageTexture node the used texture VRAM size does not change at all - whatever DDS file compression file variant I use.

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

Posted: Wed Jan 06, 2021 1:28 pm
by lanklaf
BiteDXH wrote: Hello, Lanklaf, I have another question. Now there is no problem with output linear exr according to your settings(ACES2065-1), but how to output jpg/png with tonemap?
I tried sRGB and ocio output-sRGB in the Render Settings, but the results seemed wrong.
Why is it wrong, because of color or because of gamma?
Try exporting as OCIO - Output - Rec. 709

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

Posted: Wed Jan 06, 2021 3:25 pm
by bloomis2
Don't know if it's a 2020.2 issue, but when i want to keep my light power while scaling it down, unchecking "Surface brightness" doesn't work. But then, after struggling with this issue on some other light, when i get back to the first one and I check / uncheck "surface brightness", suddenly it works. Then I scale it down a bit more and the power gets reduced again... Seems like it's working half of the time. I'm on PC windows, RTX2080TI, every drivers updated etc.

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

Posted: Wed Jan 06, 2021 4:15 pm
by aoktar
bloomis2 wrote:Don't know if it's a 2020.2 issue, but when i want to keep my light power while scaling it down, unchecking "Surface brightness" doesn't work. But then, after struggling with this issue on some other light, when i get back to the first one and I check / uncheck "surface brightness", suddenly it works. Then I scale it down a bit more and the power gets reduced again... Seems like it's working half of the time. I'm on PC windows, RTX2080TI, every drivers updated etc.
This kind of issues are not related to drivers or gpu types. Mostly plugin related but, there is not a change in plugin side to cause a problem for this. Core is same for light management as previous stable builds. Please save the scene if it happened again and send me

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

Posted: Wed Jan 06, 2021 8:21 pm
by thanulee
Appreciate the ACES workflow tips from everyone. We need a clear manual explanation i think when its 100% implemented (dont know if it already is btw just a shot in the dark). Wanna see if this is something worth changing in my workflow which is pretty much 0 comp all effects on camera.

Thanks

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

Posted: Thu Jan 07, 2021 1:10 pm
by aoktar
BiteDXH wrote: This is the result of my test. The picture rendered to the picture viewer looks like an additional gamma curve has been added. After I offset this gamma with ps, the result looks normal.
It should be related to image saving format and colorspace type, if you talk about the saving of main buffer from C4D save section. Plugin assigns sRGB color profile for colorspace=sRGB, other types are Linear sRGB or Linear for OCIO.

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

Posted: Thu Jan 07, 2021 5:38 pm
by tegatwork
Hi, I'm facing an error while rendering... here is the log...

I'm using 2020.2 RC6, with 3*3080, C4D R23, and all files of the same project where rendering nicely until now...

Any clue?

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

Posted: Thu Jan 07, 2021 5:48 pm
by aoktar
tegatwork wrote:Hi, I'm facing an error while rendering... here is the log...

I'm using 2020.2 RC6, with 3*3080, C4D R23, and all files of the same project where rendering nicely until now...

Any clue?
Could you ask in standalone topic, it's not related to plugin.

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

Posted: Sat Jan 09, 2021 2:14 am
by eyeonestudio
Scatter Object - Not follow, Parent Object Animation
sca.png