-
Notifications
You must be signed in to change notification settings - Fork 4
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
Comments
I think the issue belongs to |
could be, but pls note that there were quite a few changes in this area recently (in blender) too namely this one: |
Please confirm whether you're using latest |
yes, its been experienced with |
Great - can you provide a publish |
Yes, here you have it...note just version is upped by one from |
So the issue I think is that the There's definitely a bug there. :) I just can't quickly find where that splitting happens. |
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) |
Is there an existing issue for this?
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 value1
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:
Render
publish instanceFrames per task
Chunk Size
valueAdditional context:
Here you can see the comparison between correctly submitted job from
maya
host:and malfunctioning
blender
job which is missing that parameter:Relevant log output:
The text was updated successfully, but these errors were encountered: