ACES Maya ignores texture import settings

[hyperviktor]

When I connect a texture map to aiStandard shader, no matter what I use as the input color space there is no effect in the render.

I have ACES 1.2 installed, OCIO config loaded etc. yet I still have a number of things that don't seem to work as expected.

Any help ?

[Chtenelis]

You need to remake the tx file everytime you change the input colorspace.

[hyperviktor]

For testing I don't use .tx files as takes ages to generate,I use the original .jpg with color profile assigned within aiImage and I have .tx generation turned off , although I did tests with .tx and didn't make any difference.

[lee_griggs]

Hi Hyper, I presume you have the Color Space set to Utility - sRGB texture?

Once the .tx files are generated you should see speed improvements. Here are some of the benefits of using .tx files.

[hyperviktor]

Are you deliberately trying to be unhelpful ? We do use .tx textures in production and I'm well aware of the benefits , speed improvements etc. but in this case it's irrelevant.

My issue has nothing to do with .tx textures, I have a problem with ACES not doing what it should do. Do you have any comments on that ?

[Stephen.Blair]

If you use a tx file for your test, then we can check it with oiiotool -v --info, and see what color conversion was applied. So...change the color space on the image node, render and the tx is updated, check the tx and see what color-convert was used.

[lee_griggs]

Render the shader ball scene here and if it doesn't match, upload the results.

[hyperviktor]

I'm using 'Utility - sRGB - Texture' for color inputs, 'Utility - Raw' for data.

My problem is that in my tests changing the texture's color space does not result a change in the render.

[hyperviktor]

First thing I got was a warning that your OCIO cinfig is missing , but I'm using ACES 1.2 anyways so I guess I just point the project to that file.

[hyperviktor]

Looks different, hre's the render and the converted .tx texture fileball.zip

[hyperviktor]

Same problem - regardless what input color space I select in the aiImage, the render result stays the same.

[Stephen.Blair]

Changing the color space on an aiImage forces an update of the tx, and the tx will have a different color-convert applied. You should see the maketx in the console log, the tx file should be updated, and the new tx used for the render (maybe you need to force update?)

[hyperviktor]

Nothing wrong with the .tx converter, I deleted the original .tx before rendering so it was generated during rendertime.

[hyperviktor]

Here's what the imported .exr looks like in my hypershade editor.

[hyperviktor]

Now it looks like this, pretty arbitrary but most importantly - without any changes.

[Stephen.Blair]

The Material Viewer doesn't update to the new tx when you change the Color Space, you have to pause and restart the material viewer.

I don't have that problem with Arnold Render View

[hyperviktor]

Again, I'm not using .tx for testing, I skip converting and I apply the color space rules to the texture. It shouldn't make any difference. If you look at the image you can see the texture is .exr

THIS IS THE PROBLEM : My render with ACES looks fucked up - why ?

[Stephen.Blair]

I tested with exr, no tx. And same thing. I have to pause and restart the Material Viewer to see the update.

[Stephen.Blair]

At least if you use tx, we can check the tx files to verify that the color conversion was applied.

[hyperviktor]

I did upload it 7 hours ago because you have asked - it's the ball.zip file as it doesn't let upload .exr files