[Katana] Importomatic asset name wrongly populated

[vNicolini]

Describe the bug The Importomatic asset name when a cache is ingested is abc_test_group

To Reproduce Import Alembic cache from Tik4 Main UI

Expected behavior Importomatic asset name should match a syntax like as follow:

Screenshots If applicable, add screenshots to help explain your problem.

DCC Please complete the following information:

• Dcc name(s): Katana
• Dcc Version(s) 7.0v2

Desktop (please complete the following information):

• OS: Windows 11
• Version [e.g. 11]

[masqu3rad3]

Good point. I will take a look at this. Thanks for informing.

[masqu3rad3]

@vNicolini I pushed a fix to the master branch for this, will you able to take a look and check if it is working for you?

[vNicolini]

Just gave it a try (update function in Tik4 main UI doesn't do anything btw, not sure if it's intended or not);

It appears to be populated "correctly", the whole syntax needs some polishing imo but it definitely is better than the placeholder text from before! :D

In regard to the syntax, here's the current name: main_Model_caitlynGun_aa_v001_abc whereas it would be cleaner and more reabable if it was Model_caitlynGun_aa_v001. Hopefully that makes sense! Don't take that as high prio though, current naming is enough at the moment!

Thanks for the hotfix!

Cheers, VNI

[masqu3rad3]

right okay, thats better I agree.

What about just: main_Model_caitlynGun_aa This could make more sense. Imagine that you are iterating versions and update this file on next versions.

btw I am thinking about a simple methodology and tooling for updating the ingested versions, just couldn't come up with something as elegant as I would like it to be.

[vNicolini]

What about just: main_Model_caitlynGun_aa This could make more sense. Imagine that you are iterating versions and update this file on next versions.

ehhhh i kinda am skeptical about not having the version displayed if you know what i mean

btw I am thinking about a simple methodology and tooling for updating the ingested versions, just couldn't come up with something as elegant as I would like it to be.

i've hit the same wall with my own loader both in Katana and Gaffer actually ... If you want you can check my code in the Katana exemple i've sent you earlier (see the video to how to find it). It's not super clean or anything and was written to work with Prism's structure.

https://github.com/masqu3rad3/tik_manager4/assets/57097563/ed415d2c-71e3-4df2-92f6-d43e3b77f6c0

[masqu3rad3]

I am doing something similar with my trigger (rigging utility) workflow. However I am thinking to find a solution querying the tik manager similar to what the work and publish files to. It becomes much harder as it requires a different approach for each dcc.

about not seeing the versions on the node name.. If you increment the version of the file with a script, manually or with a future tik manager update, that would mean that group name needs to be renamed with the correct version as well right? A misleading version number would be far worse than no version number.

[vNicolini]

that would mean that group name needs to be renamed with the correct version as well right?

Yup

A misleading version number would be far worse than no version number.

100% agree on that 👍