Enhancement: Houdini publish existing caches/frames

[MustafaJafar]

Is there an existing issue for this?

• [X] I have searched the existing issues.

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

Problem description: Houdini simulations need many iterations so artists can keep adding tweaks and once they are comfortable they will consider publishing. Also, simulations are CPU intensive so most of times it will be a problem to re-render or re-cache to just publish (register data to AYON/OpenPype DB) However, publishing is not just about registering data to the DB, it's also about running validations to ensure these data imply to studio's specifications.

one solution that we came up with in community to have a toggle on the ROP node that skips the render action so it will just validate these data before publishing.

in this screen shot, alembic pointcache rop is reading a file read sop node.

How would you imagine the implementation of the feature?

1. add use_existing checkbox in creator plugin

2. use it in extractors so, it skips rendering

   if not instance.data["use_existing"]:
   render_rop(ropnode)

Are there any labels you wish to add?

• [X] I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

another solution would be to have a universal publish node that's only purpose to publish.

Additional context:

Feel free to add your ideas and suggestions.

[cuID:OP-7229]

[BigRoy]

Instead of a Use existing checkbox I think we're better of making an ENUM attribute similar to Fusion and Nuke does for renders. There you have the option defined here to:

• Use Existing Frames
• Local Machine Render
• Farm Rendering
• Use Existing Frames - farm

Having an enum makes it easier to understand what's going on and will also make sure that "Existing frames" + "Local or farm" etc can be tackled in unison.

[krishnaavril]

Need these options same for Review family as well please, we can take advantage of rendering opengl in deadline machines, and publish existing frames, currently there is a limitation of publishing locally, Huge size caches are eating so much of time on this limitation.

[MustafaJafar]

I got it! Totally make sense.

Here's a screenshot for reference

[MustafaJafar]

It's implemented with render but not cache re-created on ayon https://github.com/ynput/ayon-houdini/issues/19