Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Unable to publish renders in Houdini with AOVs added in OP Arnold ROP #5280

Closed
2 tasks done
krishna8008 opened this issue Jul 12, 2023 · 4 comments · Fixed by #5281
Closed
2 tasks done

Bug: Unable to publish renders in Houdini with AOVs added in OP Arnold ROP #5280

krishna8008 opened this issue Jul 12, 2023 · 4 comments · Fixed by #5281

Comments

@krishna8008
Copy link

krishna8008 commented Jul 12, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior:

Trying to publish renders through OP in Houdini 19.5.569, Publishing is not working with custom AOV's added in the arnold

Expected Behavior:

Publish should be successful and must see Job in deadline submitted succesfully

Version

3.15.12

What platform you are running OpenPype on?

Windows

Steps To Reproduce:

prepare a sample scene in houdini.
assign material standard surface and create custom aov plugged in it.
create a ROP using OP and add the custom AOV inside.
try to publish the ROP using OP.

Are there any labels you wish to add?

  • I have added the relevant labels to the bug report.

Relevant log output:

No response

Additional context:

image

[cuID:OP-6355]

@MustafaJafar
Copy link
Contributor

@BigRoy
I have found out something

if not rop.evalParm("ar_enable_aovP{}".format(index)):

I think it should be

        if not rop.evalParm("ar_enable_aov{}".format(index)):

Reference, this is how enable parameter looks like in my arnold version
image

@BigRoy
Copy link
Collaborator

BigRoy commented Jul 12, 2023

Yes, does look like it 👍 - must have been a typo I assume.

@BigRoy
Copy link
Collaborator

BigRoy commented Jul 12, 2023

Actually, yes. Pretty sure this was a typo by @antirotor when resolving conflicts - see this commit.

@MustafaJafar
Copy link
Contributor

@BigRoy Thanks for confirming, I'm going to make PR if you hadn't do that already XD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants