Here is what is happening:
When using a custom color space (the "OCIO/ACES workflow"), the the VFB content is in linear sRGB instead of the expected gamma-corrected sRGB - this is why it looks "wrong". The reason for this is that with the current color management implementation, Corona does not respect the 3ds Max
Display and Views > Frame Buffer Default option.
We are working on improving the color management support and also trying to come up with a workaround that would allow users to see the image in the VFB as expected.
Also, we are planning new VFB features for Corona 12 (and a reskin), with the intention of making working with OCIO/ACES easier.
What works correctly right now is:
- Loading textures created in specific color spaces (there is a new drop-down for this in Corona Bitmap (and Corona Color))
- Rendering in a specific color space (all internal calculations are done in that color space)
- Outputting files with the selected color space and conversion (
3ds Max 2024 "color management" section in the "Save image" dialog).
What we suggest:
If you do not need to load textures created in specific color spaces or are not planning to render in specific color spaces to bring your images into 2D editors or compositing software, leave the 3ds Max color management settings at the legacy gamma workflow.
Otherwise, you can use the available options (loading textures, customizing 3ds Max color management, outputting in specific color space), but bear in mind that the result visible in the VFB will be displayed in linear sRGB.
We are also working on a color management guide that we will share with everyone.
Sorry for not fully supporting everything. We are doing our best to improve this. Meanwhile, we are still interested in hearing what color management options you are interested in and why.