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-7024_Look Assigner to combined aiStanInd issue #160

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

AY-7024_Look Assigner to combined aiStanInd issue #160

ynbot opened this issue Oct 24, 2024 · 0 comments
Assignees
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 24, 2024

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

So, take 2 assets that have been published as models (with abc extractor included) and have a look also published. Load the abc representation of those 2 assets, create a pointche instance and publish an alembic with those 2 assets together. Let's call this asset, a_b_combined If you load a_b_combined as a referenced alembic, you can run the look assigner with no issue, both assets in the combined asset are detected, looks related as well and all works fine. Now, if you load a_b_combined as a standIn, the look manager detects both assets and it's relative look, BUT the asignment will go wrong. No errors, just the logic fails since the name of the container of the alembic procedural will be the same for both assets. I think here is the logic key to this. This creates 2 issues:
even if you only select object a and assing it's look, all looks of all asset in the combined asset will be loaded
the assignemnt of looks will always be of the last look to the last asset in the loop since all nodes in the function will have the same name.

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-7024

@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 24, 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

2 participants