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-6951_Blender: Create publish render into versioned directories #58

Open
ynbot opened this issue Oct 14, 2024 · 0 comments
Open

AY-6951_Blender: Create publish render into versioned directories #58

ynbot opened this issue Oct 14, 2024 · 0 comments
Labels
sponsored This is directly sponsored by a client or community member type: enhancement Improvement of existing functionality or minor addition

Comments

@ynbot
Copy link
Contributor

ynbot commented Oct 14, 2024

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

When submitting a render from Blender we want to 'increment' the output paths so that each new submission ends up in its own folder. Usually in other DCC integrations we use some scene token like in maya or $HIPNAME in Houdini so that the scene's filename becomes the unique identifier - but it seems that Blender does not support this natively.

Preferably we have something that does not interfere with regular 'custom' workflows in Blender - but does allow us to reliable make sure an artist submits to the farm in separate folders so that multiple submissions can be in the queue at the same time, without interfering with each other.

How would you imagine the implementation of the enhancemenent?

No response

Describe alternatives you've considered:

No response

Additional context:

link to discussion on Discord
(might be a private channel)

This issue was automatically created from Clickup ticket AY-6951

@ynbot ynbot added sponsored This is directly sponsored by a client or community member type: enhancement Improvement of existing functionality or minor addition labels Oct 14, 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: enhancement Improvement of existing functionality or minor addition
Projects
None yet
Development

No branches or pull requests

1 participant