Frame buffer and Color Management settings

[Guillaume G.]

Hi,

I am working with 3ds Max 2025, and since updating to Corona 12 update 1, I keep encountering this error message: "Frame buffer uses view transform set in Color Management settings. Using ACES OT with a view transform may lead to incorrect results."

When I click on "Learn more," it redirects me to a 404 page, which isn't very helpful. I'm not very familiar with the color space settings in Max and Corona, so I would like to know how to resolve this issue.

I am also attaching a screenshot of my 3ds Max configuration.

Thank you in advance!

[pokoy]

I'm not really up to date on the OCIO implementation in Max and how Corona handles it but judging from the screenshot your OCIO setting already use an ACES view transform, which is already passed along to the Corona VFB. If that's the case, applying the ACES Operator in the VFB will result in a double application of ACES tone mapping, which probably why it's throwing the error/warning in the log. Again, only an assumption but probably the reason why the warning comes up.
I agree that a 404 is not helpful :D, and Corona could probably automatically set the correct settings in the VFB (and probably let you choose whether to apply them or not).

[Guillaume G.]

Thank you for your response. I did notice that disabling ACES OT in the VFB makes the message disappear, but now I’m unsure about the optimal way to address the issue in Max without disrupting the workflow.

[pokoy]

I see, you'll have to wait for a support response then. I know that the suggested way to handle Max OCIO was to use the 'Gamma Workflow' OCIO preset, but I have no hands-on experience with Max 2023+ and it might have changed for Corona 12 Update 1.

[Aram Avetisyan]

I'm not really up to date on the OCIO implementation in Max and how Corona handles it but judging from the screenshot your OCIO setting already use an ACES view transform, which is already passed along to the Corona VFB. If that's the case, applying the ACES Operator in the VFB will result in a double application of ACES tone mapping, which probably why it's throwing the error/warning in the log. Again, only an assumption but probably the reason why the warning comes up.
I agree that a 404 is not helpful :D, and Corona could probably automatically set the correct settings in the VFB (and probably let you choose whether to apply them or not).

Yes, this.

It is not deleted/changed automatically, because in some cases it can actually give artistically good results, so Corona just informs that there may be an issue.
OCIO should be very well supported (besides some rendering color spaces and very minor stuff), gamma workflow is "recommended" just to keep things as they used to be.

[Guillaume G.]

That’s clearer, thank you for your response.

[Aram Avetisyan]

You're welcome!