Hmm, so maybe I'm doing something wrong but here's the procedure:
- Create an ICC profile (via calibration etc)
- Load the ICC profile in Windows Color Management
- Start up 3ds Max, create a random color intense render and save a PNG file
- Open up Affinity (or PS), load up the saved render and make sure the ICC profile in Affinity / PS is set to the ICC (Explain?)
- Compare the VFB you have open with the file in Affinity / PS
So doing that I can see the Corona VFB matches the Affinity / PS document that is set to the ICC profile.
I've also tried live switching between the default sRGB Windows profile and the ICC I created and that also shows the difference as I switch between them.
Since I'm not touching any of the OCIO tools in any of the apps, could it be a Windows update that enabled this? :)
There is indeed auto-color management with latest Windows 11 update, or it's been there since January if you're on fast-track. I haven't tested it as I don't run these builds with it yet.
It's called..."auto-color management".
https://support.microsoft.com/en-us/windows/auto-color-management-in-windows-11-64a4de7f-9c93-43ec-bdf1-3b12ffa0870b If not that, then there are few more things to consider:
- Do you have wide-gamut Display and are you running wide-gamut mode in OSD? (Native, or DCI-P3/AdobeRGB). Unless you have monitor that greatly exceeds sRGB color gamut, you will not see noticeable color shift. This shift would also be strongest in Red tones.
ICC profile merely interprets color in OS, it runs on top of what the monitor's OSD is set to. That's why ICC is always paired to specific monitor mode, and if you switch it's not longer applicable. So for wide-gamut environment, you would run Native or specific wide-gamut mode in OSD, and then calibrate after that to ICC which matches the desired color-space. The possible working combination go from higher to lower (so Wide-Gamut to Low-gamut) or equal to equal (HG to HG or LG to LG).
- What do you mean "make sure the ICC profile is set", Working Space ? When you import file, you can
convert to profile (which should be default settings if you don't get asked), or
assign profile (which is meant to interpret colors when profile is missing). Since I am not on 2025 with OCIO, my 3dsMax (or Corona VFB for that matter) doesn't save with any color-profile attached to file formats.
- Your file (render) should be converted to space you intend to work in and the working space should like-wise be set to generic (non-device specific) color-space (sRGB or P3/AdobeRGB/.. for Wide-gamut.
If you load your monitor ICC, you will disable color-management.- If you want to be sure, set working environment in Photoshop to sRGB (that is default). On importing render, set the mode to "convert". On opening, convert the render to sRGB color-space. Make sure the auto-mode in Window is disabled if by any chance this latest update is on. And only after that, compare 3dsMax Corona VFB and your opened render.
I don't understand right now 100perc. which exact combination you're doing, but in my opinion you most probably negated color-management and are seeing incorrect (but identical) colors in both 3dsMax and PS. That's actually quite easy scenario to achieve. Seeing identical colors doesn't mean you have correct color-managed workflow pipeline.
It doesn't matter though, I can guarantee you 3dsMax until 2025 simply isn't color-managed, it can load Gamma 2.2 and that's about it. With the OLED I have right now, single-toggle of sRGB in NoVideo tool shows almost 20perc. perceptible difference in red saturation, matching the srgb coverage of WOLED panels (125perc. QD-OLED up to 150perc. even)