Author Topic: Looking for clarity on Color Management in 3ds Max 2025+ with Corona 13  (Read 469 times)

2025-08-06, 10:21:15

ProxyFuel

  • Active Users
  • **
  • Posts: 9
    • View Profile
Is there an official or recommended workflow for using the new Color Management system in 3ds Max 2025+ with Corona Renderer 13? I've looked around and find answers that conflict.

So far, I’ve stuck with the legacy Gamma 2.2 setup because it gives me predictable results. But I know it's time to get familiar with the newer ACES/OCIO-based color management and how it integrates across the viewport, materials, rendering, and saving.

Out of the box, I often run into issues where what I see in the viewport doesn’t match the render, and both differ from the saved image. I’m trying to establish a consistent, predictable workflow—ideally where what I see is what I get when saving a standard JPG (let’s leave 32-bit linear workflows aside for now).

Example of the issue:
Using the legacy Gamma 2.2 workflow:

I import a JPG street photo—looks good in the viewport.

It renders correctly, matches the original.

Saved output is accurate.

Using the new Color Management workflow:

The same image looks washed out in the viewport.

The render comes out darker than the original.

If I tweak the color management settings to fix the background, then my 3D elements look wrong—as if they no longer match the photo.

This inconsistency is making it hard to transition. Has anyone found a solid setup or workflow to ensure predictable results from viewport → render → saved image, especially with standard 8-bit JPGs?

2025-08-06, 15:30:19
Reply #1

ProxyFuel

  • Active Users
  • **
  • Posts: 9
    • View Profile
The plot thickens...

I’ve discovered something odd: if I add a JPG as a background using a Tonemap Control node, disable ACES in the tone mapping settings, and hit render — everything looks correct.

But here's the catch:
As soon as I hit Stop and render again, the image goes dark. It won’t return to the correct look until I restart 3ds Max. Then it behaves — but only for the first render. After that, same issue.

This happens consistently across multiple machines, all running the same version of Max and Corona. I’ve tried different scenes and different JPGs — same result every time.

Right now, I can’t get things to render correctly with the new color management system. Anyone else seeing this?

2025-08-06, 16:38:40
Reply #2

James Vella

  • Active Users
  • **
  • Posts: 678
    • View Profile
The first question is - do you need to work in a color managed environment? If the answer is "I dont know" then you probably don't.

If you are working in a pipeline that is color managed then its useful since everything can be unified/delivered as expected. You will then need to understand how to use the transforms and workflow - or learn it from/with the studio that requires this (usually the fastest way since they have a workflow they can teach you - which gives you a way to connect the dots).

I’ve discovered something odd: if I add a JPG as a background using a Tonemap Control node, disable ACES in the tone mapping settings, and hit render — everything looks correct.

The ACES tone-mapper is just curve basically, its not recommended to use this in conjunction with color management.

Is there an official or recommended workflow for using the new Color Management system in 3ds Max 2025+ with Corona Renderer 13? I've looked around and find answers that conflict.

Try reading these first.

https://help.autodesk.com/view/3DSMAX/2026/ENU/?guid=GUID-DA8CE2F5-1400-45A9-BFCF-A4A8968175CF
https://help.autodesk.com/view/3DSMAX/2026/ENU/?guid=GUID-9FDA8D1F-1285-49F4-B025-D505D40FD24D
https://help.autodesk.com/view/3DSMAX/2026/ENU/?guid=GUID-2440635A-3E84-4215-AB09-9B3F4AB772D4

If you want to understand it more thoroughly at some point, test things for yourself etc read this by Chris:
https://chrisbrejon.com/cg-cinematography/chapter-1-5-academy-color-encoding-system-aces/

Example from Chris' page of a simplified view of the workflow:
« Last Edit: 2025-08-06, 16:49:29 by James Vella »

2025-08-06, 17:37:10
Reply #3

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 13792
  • Marcin
    • View Profile
I second what James said:
If you need the ACES workflow - use it.
If you don't - use the legacy gamma 2.2 workflow.
If you like the ACES "look", but you don't want to deal with all the color management stuff - use the legacy gamma 2.2 workflow and enable the ACES OT operator in the VFB Post tab.
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2025-08-07, 09:49:06
Reply #4

ProxyFuel

  • Active Users
  • **
  • Posts: 9
    • View Profile
Thank you for the answers. As I expected, if there’s no explicit need for this feature, then it’s not necessary to use it.

My main concern is more about why this isn't an advanced option that can be enabled and configured by those who actually need it—instead of being a default setting applied to everyone out of the box.

I’ve been using Corona since the beta days and have always appreciated how easy it is to use while still delivering great results. But small things like this can be frustrating. I can imagine how many new users might struggle to understand why their renders look off or incorrect.

I realize this is more of a 3ds Max issue than a Corona one, but I still think it's worth bringing up

2025-08-07, 14:30:49
Reply #5

James Vella

  • Active Users
  • **
  • Posts: 678
    • View Profile
My main concern is more about why this isn't an advanced option that can be enabled and configured by those who actually need it—instead of being a default setting applied to everyone out of the box.

Odd, in max2024 the default option is Gamma Workflow, has this changed in 2025?

I’ve been using Corona since the beta days and have always appreciated how easy it is to use while still delivering great results. But small things like this can be frustrating. I can imagine how many new users might struggle to understand why their renders look off or incorrect.

Heh, reminds me of the fun we had back in 2009 when we switched to the Gamma Workflow. People have been requesting color management in 3dsmax for a long while, if you need to streamline your pipeline then ocio is a useful wrapper for and end to end workflow. This way the artist doesnt have to think about LUTs, transforms, color spaces, rules etc the project lead can set this up and the artists can just work - in theory.

If you dont need this then you can just go about your business as usual - the intent was to reduce frustration from my understanding.

2025-08-07, 14:33:24
Reply #6

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 13792
  • Marcin
    • View Profile
Yep, ACES/OCIO is the default in Max 2025 and newer.
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2025-08-07, 14:34:17
Reply #7

alexyork

  • Active Users
  • **
  • Posts: 752
  • Partner at Recent Spaces
    • View Profile
    • RECENT SPACES
We've found AGX to be a better solution than ACES anyway. So for us it was a case in 2026 of having to switch back to legacy Gamma 2.2 workflow so we continue using AGX and having consistency with old projects. It's a shame AGX is more complex/cumbersome to work with, but the results are worth it.
Alex York
Partner
RECENT SPACES
recentspaces.com

2025-08-07, 15:17:46
Reply #8

James Vella

  • Active Users
  • **
  • Posts: 678
    • View Profile
Yep, ACES/OCIO is the default in Max 2025 and newer.

Ah k.

So for us it was a case in 2026 of having to switch back to legacy Gamma 2.2 workflow so we continue using AGX and having consistency with old projects.

Im confused, you are using the Gamma Workflow with AGX? Have you tried @piotrus3333 upload of the ocio for Agx (by Troy Sobotka) ?
https://forums.autodesk.com/t5/3ds-max-color-management-forum/alternative-ocio-config-for-max-and-maya-because-there-is-more/m-p/13192991#M27

2025-08-07, 15:50:25
Reply #9

alexyork

  • Active Users
  • **
  • Posts: 752
  • Partner at Recent Spaces
    • View Profile
    • RECENT SPACES
Yep, ACES/OCIO is the default in Max 2025 and newer.

Ah k.

So for us it was a case in 2026 of having to switch back to legacy Gamma 2.2 workflow so we continue using AGX and having consistency with old projects.

Im confused, you are using the Gamma Workflow with AGX? Have you tried @piotrus3333 upload of the ocio for Agx (by Troy Sobotka) ?
https://forums.autodesk.com/t5/3ds-max-color-management-forum/alternative-ocio-config-for-max-and-maya-because-there-is-more/m-p/13192991#M27

not so far - just doing it the original old-school way with manually-loaded LUTS on cams. this looks great, cheers!
Alex York
Partner
RECENT SPACES
recentspaces.com

2025-08-07, 16:03:16
Reply #10

James Vella

  • Active Users
  • **
  • Posts: 678
    • View Profile
not so far - just doing it the original old-school way with manually-loaded LUTS on cams.

Curious, if you are just using an LUT how is it more complex/cumbersome?

this looks great, cheers!

Dont thank me yet lol, using an LUT is the easiest method. @piotrus3333 Would know more than me about this stuff, I was just curious if you were using Agx through ocio.

2025-08-07, 16:10:38
Reply #11

alexyork

  • Active Users
  • **
  • Posts: 752
  • Partner at Recent Spaces
    • View Profile
    • RECENT SPACES
Yes you're right, it might not actually be *more* cumbersome, but I guess our main issue at the moment is that we can't access the coronacamera's tonemapoverride via scripting, where we'd love to make a simple button script that will load in the 2 x LUTs required to get it working on the selected camera(s). We were hoping that had changed in corona 12/13 but I don't believe it has.

Can a Corona dev chime in on that maybe?
Alex York
Partner
RECENT SPACES
recentspaces.com

2025-08-07, 16:21:21
Reply #12

James Vella

  • Active Users
  • **
  • Posts: 678
    • View Profile
we'd love to make a simple button script that will load in the 2 x LUTs required to get it working on the selected camera(s).

If I understand you correctly you want to combine LUTs? If so have you heard of 3D LUT Creator? It might be worth looking into since its pretty powerful, among other features you can do your tonemapping then put both the original image and final image in then create a LUT based on the changed values.

I wrote a short article on it here if you are interested in a quick run down. Unless ive totally misinterpreted your post

edit:
A secondary option is stack the LUTs in vray, save out a small image, then you can use the command line ocio tools to build a .cube (LUT) for the current setup. GPT could build it for you but you need to test it and when its good you have a solid combined LUT moving forward. I did this recently for a client who needed all the layers in vray vfb as an LUT, worked out well.
« Last Edit: 2025-08-07, 19:15:03 by James Vella »

2025-08-08, 10:26:49
Reply #13

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 13792
  • Marcin
    • View Profile
Yes you're right, it might not actually be *more* cumbersome, but I guess our main issue at the moment is that we can't access the coronacamera's tonemapoverride via scripting, where we'd love to make a simple button script that will load in the 2 x LUTs required to get it working on the selected camera(s). We were hoping that had changed in corona 12/13 but I don't believe it has.

Can a Corona dev chime in on that maybe?

Not a dev, but I don't think this is currently possible. I have logged a feature request on your behalf at https://chaoscorona.ideas.aha.io/ideas/CMAX-I-223
(as usual, it won't be visible for some time, until Tom accepts it)
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us