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

AY-6230 - Submitting pointcache product type to farm is always a single file #58

Open
2 tasks done
MustafaJafar opened this issue Jul 31, 2024 · 6 comments
Open
2 tasks done
Assignees
Labels
sponsored This is directly sponsored by a client or community member type: bug Something isn't working

Comments

@MustafaJafar
Copy link
Contributor

MustafaJafar commented Jul 31, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior:

It happens with Alembics and Bgeos

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
image
However when submitting to farm I always get one file
image
Although, I've set the frame per task to 1
image
image

With Bgeo, it fails completely :(

2024-07-31 18:21:16:  0: STDOUT: Missing expected files: ['pointcacheBgeoCache.0999.bgeo', 'pointcacheBgeoCache.1000.bgeo', 'pointcacheBgeoCache.1002.bgeo', 'pointcacheBgeoCache.1003.bgeo']
2024-07-31 18:21:16:  0: STDOUT: Expected files: ['pointcacheBgeoCache.0999.bgeo', 'pointcacheBgeoCache.1000.bgeo', 'pointcacheBgeoCache.1001.bgeo', 'pointcacheBgeoCache.1002.bgeo', 'pointcacheBgeoCache.1003.bgeo']

Expected Behavior:

No response

Version

1.0.0

What platform you are running on?

Windows

Steps To Reproduce:

  1. publish abc (with .$F4 token in output path) or Bgeo to farm

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:

No response

[cuID:AY-6230]

@MustafaJafar MustafaJafar added type: bug Something isn't working sponsored This is directly sponsored by a client or community member labels Jul 31, 2024
@SzabadosA
Copy link

looking at the manifest, it seems like the frame always gets set to 0 and the output dir/file does not get resolved:

image

@SzabadosA
Copy link

SzabadosA commented Aug 1, 2024

I just did some test.

  • Bgeo does work without issues
  • ABC breaks in deadline, but the manual fix is manually setting the frame range properly from 0 to the correct range
    = > will compare the code differences between bgeo and abc and come back to you

@SzabadosA
Copy link

https://github.com/ynput/ayon-deadline/blob/67fce57874ba293a754c1adae93202c1d071a20c/client/ayon_deadline/plugins/publish/houdini/submit_houdini_cache_deadline.py#L80

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 ?

@iLLiCiTiT
Copy link
Member

I'm sorry, but I'm not familiar with houdini, would be question for @BigRoy or @antirotor .

@SzabadosA
Copy link

Ah ok, I just tagged you because I saw your name in the code blame for this code

@BigRoy
Copy link
Contributor

BigRoy commented Sep 5, 2024

https://github.com/ynput/ayon-deadline/blob/67fce57874ba293a754c1adae93202c1d071a20c/client/ayon_deadline/plugins/publish/houdini/submit_houdini_cache_deadline.py#L80

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?

No idea - @MustafaJafar any idea why that might be there? If not, let's remove it - and then test the different cases.

@antirotor antirotor changed the title Submitting pointcache product type to farm is always a single file AY-6230 - Submitting pointcache product type to farm is always a single file Sep 10, 2024
@MustafaJafar MustafaJafar self-assigned this Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sponsored This is directly sponsored by a client or community member type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants