Redshift OCIO issue

[Dutchbird]

I updated Cinema4D and Redshift and got an error.
"Project OCIO settings invalid"
I noticed different settings in the Color Management.

It came up like this.

But it has to be this.

I deleted the new.c4d default scene and the preference folder and it all looked like it has to be.

After a while and a new startup of the Application the settings are wrong again.

What could possibly be wrong?

[Dutchbird]

I also notised my Color Management drop down in Redshift Render settings is gone.

[atomician]

I had some weird color management issues with redshift initially, but set these settings on my default project and it's been ok since. I have a default project that opens up whenever I create a new project in C4D.
You can change the default startup project by going to Edit > Preferences > Files and amending the settings here:

[Dutchbird]

@drawer-site
Hi. Even when a default scene is set I get the error when starting a new project.
But only after a restart of the application.

[Dr. Sassi]

Hi Dutchbird,

First, answering that without knowing any version of C4D or OCIO you use is dangerous for your outcome.

The entry for the past few versions should be $OCIO. Since I know you sometimes use older versions, something might have overwritten your older setup. (Wild guess here.

Please check with tech support to avoid a long search, or follow the wild guesses below
https://www.maxon.net/en/support-center

The change of OCIO might change all color output, and any continuity in a project may not be provided. A fast (wrong) solution, or wild guesses, might destroy the output continuity.

Is that working when you right-mouse click on the "OpenColorIO Config" and use the set to Default?

I'm unclear about what version you use, Cinema 4D and OCIO-wise. Have you changed something?

The installation typically provides all the needed data and settings if nothing has changed.

I don't say it often, but either your preferences are in need to be deleted or a new installation is due. As this is a wild guess, try first to reset the default.

The idea is that OCIO is based on a central installation, e.g., in a larger Studio. Everyone uses the same framework; if updated, the whole studio stays in sync. This allows the framework to have settings for any Color Management that is inside of that framework. Those settings rely on a specific version of OCIO, e.g., it could be based on ACES or soon ACES v2 (Whatever "soon" means…)

The error message "Project OCIO settings invalid. Falling back to default" in the context of Cinema 4D and OCIO (OpenColorIO) installation typically means that the application was unable to locate the specified OCIO configuration file. OCIO is a "color management" solution that allows for consistent color transformations and image display across various software applications. Studios use OCIO to set specific color management rules to maintain color consistency across different pipelines.

To address the concept of "falling back", here is a clearer explanation:

When Cinema 4D (or any software using OCIO) cannot find the specified OCIO configuration (which might be centrally installed for studio-wide consistency), it "falls back" to using a default configuration. This default configuration is a predefined OCIO setup that ensures the application can still function with some level of color management, even though it may not conform to the studio's custom rules.

So, in short:

• OCIO (OpenColorIO) allows for centralized and custom color management rules, often used by studios to ensure consistent color handling.
• If Cinema 4D cannot find the specified custom OCIO configuration, it will "fall back" to using a default configuration.
• "Falling back" means reverting to a baseline or default system when the preferred or custom option is unavailable.

This ensures that the application can continue to operate without the specific custom color management settings, albeit with potentially less precision or consistency compared to the studio-defined OCIO setup.

Please note, OCIO is a framework, not the Color Management itself.

All the best

[Dutchbird]

@Dr-Sassi Just as a try out I deleted Cinema4d and Redshift completely, including the prefs folder and reinstalled the latest version.
Got all running , made a new default startup scene and after a restart I got the same error message.
I followed the latest Macon YouTube with Elly about the new PBR material and noticed on her screen she had the same error.

[Dr. Sassi]

Thank you, Dutchbird.

Very nice to explore that option, and yes, I hesitate to suggest those time "eating" tips.

A few moments ago, I chatted with a colleague from the HQ, and he encountered the same. I saw Elly's alert on her screen during my QA/Timestamps session.

There is something that needs a fix. Sorry that you have to endure this!

If you have a moment, would you mind opening a ticket?
https://www.maxon.net/en/support-center
The more data, the faster the fix (typically)

Fingers crossed, it will be fixed quickly.

Cheers