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

Nuke: Instance attribute in create write render settings #2

Open
2 tasks done
MustafaJafar opened this issue Jun 25, 2024 · 1 comment
Open
2 tasks done

Nuke: Instance attribute in create write render settings #2

MustafaJafar opened this issue Jun 25, 2024 · 1 comment
Assignees

Comments

@MustafaJafar
Copy link
Contributor

MustafaJafar commented Jun 25, 2024

Is there an existing issue for this?

  • I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?

Nuke Creator instance attribute settings is confusing.
problem as reported by krishna on discord:

Just wondering whats the actual difference between these!, they both seems almost same to me, if they perform different actions, names maybe confusing

image

How would you imagine the implementation of the feature?

Better naming.

Are there any labels you wish to add?

  • I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

No response

Additional context:

I went through the code and found out (please correct me if I'm wrong):
Farm Rendering -> adds two more render targets in Nuke publisher.
https://github.com/ynput/ayon-core/blob/ec0c004765cb5cca81ec00b8b31fe8208d1f9021/server_addon/nuke/client/ayon_nuke/api/plugin.py#L334-L336

Render On Farm -> adds a Render Farm button to the instance node
ynput/ayon-core#314

[cuID:AY-5929]

@MustafaJafar MustafaJafar changed the title Your issue title here Nuke: Instance attribute in create write render settings Jun 25, 2024
@MustafaJafar MustafaJafar transferred this issue from ynput/ayon-core Jul 16, 2024
@jakubjezek001 jakubjezek001 added the type: enhancement Improvement of existing functionality or minor addition label Jul 16, 2024
@jakubjezek001
Copy link
Member

I can confirm that this needs to be streamlined. I am afraid it could be caused by some backward compatibility inheritance, but it is really time to make it a single attribute.

@jakubjezek001 jakubjezek001 added type: maintenance Changes to the code that don't affect product functionality (Technical debt, refactors etc.)) and removed type: enhancement Improvement of existing functionality or minor addition labels Sep 19, 2024
@dee-ynput dee-ynput removed the type: maintenance Changes to the code that don't affect product functionality (Technical debt, refactors etc.)) label Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants