Hello everyone,
I read a lot about ACES recently and when I looked up on the forum I could only see some info here and there but no real post.
This is a bit disappointed because let's be honest: colorspace, gamut, OETF/EOTF, ... are not easy to understand at the first glance, and when I come to set up a OCIO on 3d software that doesn't have a color manager system, it's even worse.
So this is the place where we can set up a good ACES workflow on 3ds max together and help each other.
For my concern, I'm using ACES 1.0.3 with V-Ray Next (update 2) on 3ds max 2020.
As far as I know, on 3ds max, there are 2 steps:
1. -> Convert your textures to ACEScg
2. -> setup your OCIO profile
1. CONVERTING TEXTURES TO ACESCG COLORSPACE
For my next example, I used a 8bit jpg file in Linear sRGB colorspace.
I used a photography as a texture just to see how shadows/highlights/skin tone changed with ACES.
I thought it's a good starting point as humans are good at seeing skin tone so we could see the changes better (at least more than in a concrete albedo). Let's say she's my Marcy.
I loaded my texture with a VrayHDRI map, set the color space to sRGB.
Then, I plugged a VrayOCIO node as shown:
So, we have a jpg file (Linear sRGB colorspace) and we want it to be converted to ACEScg. Sounds about right.
At this point, I think I'm good even though my texture seems darker... Let's skip to step 2.
2. OCIO IN VFB
Now, let's set up our OCIO profile in the VFB.
Alright: All our textures are converted into ACEScg and my monitor is in sRGB colorspace. Let's render!
RENDER (diffusefilter pass):

Mmmh.. Something looks wrong here. Seems like there's a 2.2 gamma curve applied to it or something..
What did I miss?
Cheers,
I read a lot about ACES recently and when I looked up on the forum I could only see some info here and there but no real post.
This is a bit disappointed because let's be honest: colorspace, gamut, OETF/EOTF, ... are not easy to understand at the first glance, and when I come to set up a OCIO on 3d software that doesn't have a color manager system, it's even worse.
So this is the place where we can set up a good ACES workflow on 3ds max together and help each other.
For my concern, I'm using ACES 1.0.3 with V-Ray Next (update 2) on 3ds max 2020.
As far as I know, on 3ds max, there are 2 steps:
1. -> Convert your textures to ACEScg
2. -> setup your OCIO profile
1. CONVERTING TEXTURES TO ACESCG COLORSPACE
For my next example, I used a 8bit jpg file in Linear sRGB colorspace.
I used a photography as a texture just to see how shadows/highlights/skin tone changed with ACES.
I thought it's a good starting point as humans are good at seeing skin tone so we could see the changes better (at least more than in a concrete albedo). Let's say she's my Marcy.
I loaded my texture with a VrayHDRI map, set the color space to sRGB.
Then, I plugged a VrayOCIO node as shown:
So, we have a jpg file (Linear sRGB colorspace) and we want it to be converted to ACEScg. Sounds about right.
At this point, I think I'm good even though my texture seems darker... Let's skip to step 2.
2. OCIO IN VFB
Now, let's set up our OCIO profile in the VFB.
Alright: All our textures are converted into ACEScg and my monitor is in sRGB colorspace. Let's render!
RENDER (diffusefilter pass):
Mmmh.. Something looks wrong here. Seems like there's a 2.2 gamma curve applied to it or something..
What did I miss?
Cheers,
Comment