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

Submission to Deadline missing "chunk size" parameter / "Frame per task" not propagated from the publisher UI #88

Open
1 task done
LiborBatek opened this issue Jan 9, 2025 · 9 comments · May be fixed by #90
Open
1 task done
Labels
type: bug Something isn't working

Comments

@LiborBatek
Copy link
Member

Is there an existing issue for this?

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

Description

Current Behavior

Once hitting publish "Render" with set Frames per task to e.g. 10 this value is not propagated and submission using default value 1

Image

Expected Behavior

Frames per task if set to non default value must be taken into respect and used when rendering the job on DL.

Steps To Reproduce:

  1. Create Render publish instance
  2. Change value to non default on Frames per task
  3. Publish to DL
  4. Open DL Monitor and inspect the job and its Chunk Size value

Additional context:

Here you can see the comparison between correctly submitted job from maya host:

Image

and malfunctioning blender job which is missing that parameter:

Image

Relevant log output:

@LiborBatek LiborBatek added the type: bug Something isn't working label Jan 9, 2025
@iLLiCiTiT
Copy link
Member

I think the issue belongs to ayon-deadline.

@LiborBatek
Copy link
Member Author

LiborBatek commented Jan 9, 2025

could be, but pls note that there were quite a few changes in this area recently (in blender) too

namely this one:

#82

@BigRoy
Copy link
Contributor

BigRoy commented Jan 9, 2025

Please confirm whether you're using latest ayon-deadline.

@LiborBatek
Copy link
Member Author

yes, its been experienced with ayon-deadline 0.5.1

@BigRoy
Copy link
Contributor

BigRoy commented Jan 9, 2025

Great - can you provide a publish .json report from the submissions? :)

@LiborBatek
Copy link
Member Author

Yes, here you have it...note just version is upped by one from v024 to v025 as I had to re-run the publishing for the JSON report otherwise the same scene for sure...

B3D_publish-report-250109-16-57.json.txt

@BigRoy
Copy link
Contributor

BigRoy commented Jan 9, 2025

So the issue I think is that the renderlayerMain splits into two separate instances renderLightingMainFrnt and renderLightingMainBg - however, most likely the creator attributes and publish attributes aren't "transferred" from the original instance to the new instances - as such, they do not have the "attribute values" from the publisher UI.

There's definitely a bug there. :)

I just can't quickly find where that splitting happens.

@LiborBatek
Copy link
Member Author

I think @moonyuet will be able to locate the issue most easily as she was in charge of that PR regarding rendering (mentioned above)

or at least I hope so...reading Roys comment aka his findings, correct me if Im wrong or just nevermind in such occasion

@moonyuet
Copy link
Member

I think @moonyuet will be able to locate the issue most easily as she was in charge of that PR regarding rendering (mentioned above)

or at least I hope so...reading Roys comment aka his findings, correct me if Im wrong or just nevermind in such occasion

Roy is actually correct for his findings. It is being some of the instance data is not copied to the new instance(s). We need to fix it by copying those data back to the new instance(s)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants