• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Why are texture export options so unintuitive

Explorer ,
Oct 15, 2024 Oct 15, 2024

Copy link to clipboard

Copied

Is there a reason the texture export options have to be so completely, desperately unintuitive?

 

I know this menu set existed before Adobe bought the product, but I have never, ever been able to wrap my head around what should really be one of the simplest parts of this program. It only needs to basically handle a few things:

 

1) What texture sets do I want to export

2) What channels do I want to export

3) File format and resolution

4) Naming conventions

 

Yet it's completely overloaded with options, none of which function in a remotely intuitive way to the point that even setting up a naming convention is a massive headache.

 

I've tried reusing existing templates, often having to add a version number into the string by hand (since, so far as I can tell there isn't a version token available, WTF?), only to find that even this doesn't work and my version number will get stuck on a particular version even when I update it by hand in the saved/copied template that I've created.

 

There are parts of the output names of textures that I simply do not have a clue how they are generated, e.g. a string that says "$mesh_BaseColor_Knotted_($colorSpace)_v007" will generate a texture named "Quadratus_Lumborum_BaseColor_Knotted_Utility - sRGB - Texture_v005". Where does the word "Texture" come from in this naming string? And why doesn't the version number update properly?

 

And why is the "Save Settings" button in the "Output Templates" tab ALWAYS grayed out and unavailable? It would be normal to expect this button to become active upon making ANY change to the currently open template, in order to save out a version.

 

I would not expect it to be this difficult.

TOPICS
Discussion , Import & Export

Views

53

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 15, 2024 Oct 15, 2024

Copy link to clipboard

Copied

LATEST

OK, immediately after posting I see that the export template is being run "from cache". This explains why my versions are not updating. This is idiotic. Why does a cache even exist for output templates? A totally unnecessary complication. There is no situation I can think of where you would want or need this.

 

My other comments overall stand.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources