bug fix on getting aov expected files when global aov mode disabled in Redshift

[moonyuet]

Changelog Description

This PR is to fix the bug on getting AOV render products as expected files when global aov mode is turned off in Redshift renderer

Additional info

Wait for the merge #173 and #184 before testing

Testing notes:

1. Launch Maya via AYON
2. Create Render Instance with Redshift as current renderer
3. Disabled global aov mode
   
4. Publish

[BigRoy]

I didn't test the functionality - but code makes sense. On to @LiborBatek for testing.

[LiborBatek]

I have run this test, first adding some AOVs for render aka enabling those...

Cryptomatte
Z
N

Run Validate action via Publisher so I have proper AOVs naming via Repair action so validations goes well.

Then cancel the publishing and finally Disable Aovs via that RS option we are refering to in this PR.

After submitting it to DL my job fails on Publish Job due to expected Cryptomatte aov...

obviously when inspecting my JSON, it still expect those files...

So my question is, does this PR solves this scenario too? Speaking of Cryptomattes as optional AOVs with Global AOVs switch Disabled...

Right now it does not solve this issue.

[LiborBatek]

Im enclosing the JSON for rendered frames and scrn grab of the error from DL log console... just as additional info for you

renderLightingMain_metadata.json.txt

[moonyuet]

Im enclosing the JSON for rendered frames and scrn grab of the error from DL log console... just as additional info for you

renderLightingMain_metadata.json.txt

Which means by this case we need to also exclude the cryptomatte.

[BigRoy]

Im enclosing the JSON for rendered frames and scrn grab of the error from DL log console... just as additional info for you
renderLightingMain_metadata.json.txt

Which means by this case we need to also exclude the cryptomatte.

But.. doesn't this code already exclude that? It excludes all AOVs - also the Cryptomattes, right?

[moonyuet]

Im enclosing the JSON for rendered frames and scrn grab of the error from DL log console... just as additional info for you
renderLightingMain_metadata.json.txt

Which means by this case we need to also exclude the cryptomatte.

But.. doesn't this code already exclude that? It excludes all AOVs - also the Cryptomattes, right?

for some reason, it doesn't work in my side too. It can be the merged PR from the renderlayer-related changes.

[LiborBatek]

@BigRoy @moonyuet could be that RS always keep Cryptomatte as separate files always? (to my surprise, as Arnold dont do that by nature when multilayer exr enabled)

[moonyuet]

@BigRoy @moonyuet could be that RS always keep Cryptomatte as separate files always? (to my surprise, as Arnold dont do that by nature when multilayer exr enabled)

If AOV mode is globally turned off, Redshift won't render Cryptomatte no matter what. It's just beauty rendering out.

[LiborBatek]

All working now without any errors shown... there werent other files expected besides the renderLightingMain one, so all good.

My job successfully finished on DL.

Note: For some reason my rendered frames when integrated didnt produce any reviewable mp4 and thumbnail. Is it related to this PR or not? For this reason, Im enclosing DL publish job LOG too

Job_2024-04-05_09-48-47_660facdfc97c3c722d19f16d.txt

[moonyuet]

@BigRoy if you are happy with it, we can merge this PR.

[moonyuet]

All working now without any errors shown... there werent other files expected besides the renderLightingMain one, so all good.

My job successfully finished on DL.

Note: For some reason my rendered frames when integrated didnt produce any reviewable mp4 and thumbnail. Is it related to this PR or not? For this reason, Im enclosing DL publish job LOG too

Job_2024-04-05_09-48-47_660facdfc97c3c722d19f16d.txt

I dont think it is related to this PR as this PR is just about redshift aov being enabled globally in maya host.
This is more likely about submit publish job have encountered some issues. Can you try with different renderers to see the issue still exists?