Cinema4D 2022.1-[R10] (Previous stable) (26.03.2023) Tweet

[Kalua]

New build(R5) with same SDK that's available. Enjoy it!

Hi, Aoktar
These new features are absolutely awesome!

Relink, Global and Localize commands on "Octane Texture Manager" are super handy!
C4D light link is also pretty damm good!
Thanks for the features!

[ShivaMist]

Agreed these are great features!

What are the plans in the future for C4D light link ? If we could get a similar system as redshift it would be a real game changer in the motion/vfx industry (each Light group can be named and we can select which aov we get from each light group)

[SSmolak]

Color GUI type Octane native doesn't work in gradients. Octane native one is good, without update delay lag.

[thanulee]

Hey Ahmet!

Few small requests on my end:

- Can you please bring back the ctrl+ double click functionality that was expanding or collapsing a node completely? I used that a lot to tidy up my node editor network.
- Can we have a shortcut for solo/disable node? I think one of the two has a shortcut already but could we have also the option for the other as well? I think these are the most common operations a lot of users do in node editor.

Many thanks for all the effort in the node editor, in general is extremely well done!

[SSmolak]

The new color management is badly implemented it cause serious materials issue :

Oct_color_management.zip

(3.29 MiB) Downloaded 45 times

Also when we have OpenColorIO active viewport colors are mostly too bright :

Probably the new Standard Material has problem.

[jayroth2020]

Change the settings in Edit > Project Settings > Project tab > Color Management to the following:

• Select the OpenColorIO button
• Set the Preset dropdown menu to ACES
• Choose the location of the installed config.ocio file — This should be the same file as used for Octane
• Set Render Space to ACES2065-1 — This will conform Cinema to Octane standards. You can choose ACEScg, but you will then be limiting your color space to a subset of the full range offered in the ACES2065-1 option.
• Display Space — There is only one option, sRGB, which is correct
• Set the View Transform to Raw — This will allow Cinema to show you the Octane results without additional processing.
• Set the Thumbnails to Raw — This will allow the Thumbnails to be correct, without additional processing by Cinema 4D

Change the Picture Viewer View Transform setting to Embedded/Raw or Embedded.

Set the Colorspace Menu in Live Viewer to ACES2065-1. Picture Viewer and Live Viewer will match with these settings in Cinema 4D R2023. You can also choose A different colorspace in Live Viewer, such as OCIO<> (and choose the output transform from the list) and it should match as well.

I am still working out the settings you need, so I may have missed something. If so, I will update this post.

[aoktar]

The new color management is badly implemented it cause serious materials issue :

Oct_color_management.zip

Also when we have OpenColorIO active viewport colors are mostly too bright :

col.jpg

Probably the new Standard Material has problem.

There are not any integration for C4D's OCIO options. Please follow what Jayroth says

[SSmolak]

There are not any integration for C4D's OCIO options. Please follow what Jayroth says

Thank you Aoktar and Jayroth for information but viewport display problem is only for Standard Surface material - way too bright. Other materials works fine.
As for settings - I have already set them as in your setup except color space in Live Viewer set to HDR/sRGB ( I'm using ACES switch in Octane Camera). When I set it to ACES the view is linearized , dark.

I think that problem is with Standard Surface Material while using C4D OCIO mode. Switching from OCIO mode to Basic mode cause that Standard Surface looks totally different - it is too bright or too dark depends in which mode we created this material.

[jayroth2020]

@SSmolak, can you include the scene file here? If not, can you file a support ticket at [email protected] and ask for me or Beppe to review it?

[SSmolak]

@SSmolak, can you include the scene file here? If not, can you file a support ticket at [email protected] and ask for me or Beppe to review it?

I isolated problem - it is caused by gradient node which works in different color space using C4D OCIO and Basic mode. But Standard Surface wrong brightness display in OCIO mode is still actual even without using gradient node. I will prepare simple scene soon.

Octane native color GUI type in C4D OCIO mode has not linearized color slider - most of the slider space is occupied by bright colors :

The same slider and color in C4D Basic color mode :

oct_color_slider_basic.jpg (9.13 KiB) Viewed 1559 times