Bug: Houdini Publish error when publishing Bgeo Bgeo.Sc (single Frame / Frame Range)

Lyon-Rosenblatt-Ynput commented 5 months ago

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior:

when Publishing Bgeo sequence from Houdini the Integrate Hero Version errors do to missing Values.

File "/home/workh/Ynput/dev/OpenPype/openpype/plugins/publish/integrate_hero_version.py", line 363, in integrate_instance head, tail = _template_filled.split(frame_splitter) ValueError: not enough values to unpack (expected 2, got 1)

When Publishing Bgeo in Single Frame mode. publish deletes the .bgeo / bgeo.sc extensions from the files that are stored in the Vxxx and hero folders. The Work file Export is fine tho.

Expected Behavior:

Expected behavior would be that the Export copies/published the right files into the Vxxx and Hero founders i would also expect that hero integration would get the right Data in order to process the integration on sequence files.

Version

3.18.5

What platform you are running OpenPype on?

Windows, Linux / RedHat

Steps To Reproduce:

For Sequence

Open Houdini Create some points
Create a Bgeo export from the Create menu
Set the Export to single Frame
Look into the error logs and go to Integrate Hero Version

For Single Frame Export

set frame range ENUM (Valid Frame Range) to (Current)
Publish
Look into Hero/Vxxx foulder // the file extension will be . instead of .bgeo.sc / .bgeo

Are there any labels you wish to add?

[X] I have added the relevant labels to the bug report.

Relevant log output:

------------------------------------- Frame Range --------------------------------------

File "/home/workh/Ynput/dev/OpenPype/openpype/plugins/publish/integrate_hero_version.py", line 363, in integrate_instance
    head, tail = _template_filled.split(frame_splitter)
 ValueError: not enough values to unpack (expected 2, got 1)

------------------------------------- Single --------------------------------------
DEBUG: Integrating source files to destination ...
DEBUG: Checking file ... /home/workh/Documents/AyonUsd/Usd_Base/Assets/sim_r42/work/test_sim_r42/pyblish/pointcacheGustaf.1126.bgeo.sc -> /home/workh/Documents/AyonUsd/Usd_Base/Assets/sim_r42/publish/pointcache/pointcacheGustaf/v005/UB_sim_r42_pointcacheGustaf_v005.
DEBUG: Copying file ... /home/workh/Documents/AyonUsd/Usd_Base/Assets/sim_r42/work/test_sim_r42/pyblish/pointcacheGustaf.1126.bgeo.sc -> /home/workh/Documents/AyonUsd/Usd_Base/Assets/sim_r42/publish/pointcache/pointcacheGustaf/v005/UB_sim_r42_pointcacheGustaf_v005.

Additional context:

No response

[cuID:OP-8055]

MustafaJafar commented 5 months ago

As far as this issue is consisting of two parts:

Set Houdini hero version template (as the default hero version is doesn't include frames by default <.{@frame}> )
A bug with publishing the current frame in Bgeo which has nothing to do with the hero version (I hope.)

Regards the hero version template:

you can either update the default hero version or create a new hero version for houdini.

you will need to add hero_ prefix when using custom hero template.

Bgeo Current frame bug.

Publishing the current frame was not favored as from pipeline perspective there is no clue what is the intended frame to publish. That's why we added this logic

https://github.com/ynput/OpenPype/blob/b921d4384d32d24e428532a461fa238a223b5453/openpype/hosts/houdini/api/lib.py#L602-L653

@BigRoy mentioned that many times in different discussions I'll put their links for reference later.

When publishing, there are 3 cases:

Set Frame Range [Start, End] Frame Range in loader is set properly to start, end
Set Frame Range [Frame, Frame] Frame Range is set properly to the given frame.
Use Current Frame. Frame Range is set to the current frame