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

Houdini 20.5: Use the new cop nodes (Copernicus network) for imagesequence product #182

Open
1 task done
MustafaJafar opened this issue Nov 25, 2024 · 0 comments
Open
1 task done

Comments

@MustafaJafar
Copy link
Contributor

MustafaJafar commented Nov 25, 2024

Is there an existing issue for this?

  • I have searched the existing issues and added correct labels.

Please describe the feature you have in mind and explain what the current shortcomings are?

imagesequence product in Houdini 20.5 should use the new cop nodes (Copernicus network)
while in 19.5 it should use the old cop nodes.

Currently, publishing imagesequence product in Houdini 20.5 doesn't work.

some testing in Houdini 20.5

Currently, this validator ValidateCopOutputNode fails because the logic conflicts:

More info

In Houdini 19.5, hou.CopNode is a Cop/Composition node in image network.
In Houdini 20.5, hou.CopNode is a Cop node in a Copernicus network while the old cop nodes that live inside an image network became hou.Cop2Node

This is somehow makes us support the new Copernicus network out of the box because we are mostly using hou.CopNode along the code.

Some screenshots to tell them apart.

Image
Image
Image

Suggested implementation?

The whole logic should be revised to ensure that it works in both cases 19.5 and 20.5.

Describe alternatives you've considered:

No response

@MustafaJafar MustafaJafar changed the title Houdini 20.5 Support Cop nodes/Copernicus network Houdini 20.5: Use the new cop nodes (Copernicus network) for imagesequence product Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant