-
Notifications
You must be signed in to change notification settings - Fork 16
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
AY-6230 - Submitting pointcache product type to farm is always a single file #61
Comments
I just did some test.
|
ayon-deadline/client/ayon_deadline/plugins/publish/houdini/submit_houdini_cache_deadline.py Line 80 in 67fce57
This line of code seems to be the problem, if i disable the condition, the caches go through as expected. Do we know why that is in there? Maybe @iLLiCiTiT ? |
I'm sorry, but I'm not familiar with houdini, would be question for @BigRoy or @antirotor . |
Ah ok, I just tagged you because I saw your name in the code blame for this code |
No idea - @MustafaJafar any idea why that might be there? If not, let's remove it - and then test the different cases. |
I was checking #49
I think this most probably assumes that alembic is always generating a single file. So, we need a more accurate condition. |
Something similarly broken came up on community forum here: https://community.ynput.io/t/error-houdini-deadline-cache-submission/1987/4?u=bigroy Not sure if 1:1 the same thing. |
The log in that post comes from an older Houdini addon, more info check ynput/ayon-houdini@37a4e91 |
Is there an existing issue for this?
Current Behavior:
So, I've added
$F4
to my alembic rop output file to have a separate sequence of alembic files.It works as expected with local publishing
However when submitting to farm I always get one file
Although, I've set the frame per task to 1
With Bgeo, it fails completely :(
Expected Behavior:
No response
Version
1.0.0
What platform you are running on?
Windows
Steps To Reproduce:
.$F4
token in output path) or Bgeo to farmAre there any labels you wish to add?
Relevant log output:
No response
Additional context:
No response
[cuID:AY-6230]
The text was updated successfully, but these errors were encountered: