The image should pretty much match the VFB exactly. For me reds are a little warmer and touch more saturated but that could be my old monitor profile and crap monitor.
Hi @s_gru I am not sure I understand. Don’t you agree with my post?
The way 3ds Max’s ACEScg colour space works is it automatically switches V-Ray’s rendering RGB primaries from sRGB to ACEScg and enables the “auto RGB primaries for VRayBitmap texture” and assigns the ocio correction for the VFB Display correction.
As far as I’ve tested simply enabling the ACEScg from 3ds Max 2024 is all it needs.
that seems to be what i’m seeing. my bad though is that i am so used to dragging and dropping bitmaps into slate material editor, that i have to run the conversion from bitmap > vraybitmap. in doing this, plus have 3ds Max set to OCIO, i notice every bitmap has inverse gamma - except it must know when a “data” bitmap is being used b/c that seem to switch to appropriate settings. so i manually change them all if i have an older scene. otherwise going forward i can just use the vraybitmap and set appropriately. im not into re-naming all my bitmaps at this point.
i wish i could drag-n-drop to auto create a vraybitmap
If you use exr textures you will have to rename them with a suffix or switch the RGB primaries trough VRayBitmap manually. For jpeg and png it should work out of the box.
Thanks for the clarification on this Vladimir. Do you think we could get a sticky about how all of this works now so it just becomes general knowledge to your users?
I noticed a lot of the current sticky links are very outdated and some links no longer work.
The sad reality is currently 3ds Max is ahead of VRay regarding colour management.
Automatic primaries/gamma assignments for textures: VRay recognizes only a few suffixes and 3ds Max lets you customize rules based on filenames or extensions.
3ds Max and max bitmaps are now fully controlled by your OCIO config (rules are saved into config conveniently) but VRay continues with its own implementation limited to srgb/acescg. 3ds Max just flips some switches inside VRay for you - that’s all.
No question about it.
But at the moment things are more messy than previously.
On top of that is incomplete implementation of ocio v2 (looks) in both VRay and Max.
The delay, and ensuing mess, is par for the course when you have third party tech to implement for which you can’t pick the timings.
Not the first, not the last time we’ll have to dance to a broken rhythm.
Thanks for the patience.