Attribute Manager - Materials

[Anonymous]

Hi,

is it a bug or why can't I download Material texture settings from another file? I get only the other settings for material, not the file settings..

/Tobias

[Anonymous]

I found a solution.

Open original file : save as *.aat file
Open new file and import *.aat file and then it works.

/Tobias

[Ignacio Azpiazu]

Somehow related: how should one handle composite names as they evolve over time?

After several years of working pretty much on my own with my own fairly-fine-tuned system, I am now working as part of a team where composite definitions have been evolving over time, appearing during the process in different files and projects (sometimes it is the composite dimensions and fills that change a bit, sometimes it is pens only).
The problem is that when you import attributes or get a module or copy-paste an object from another file that has a 'different' composite by the same name you end up getting, for example, '4 in gyp' and '4 in gyp (1)'. Which is very upsetting and disconcerting. You don't get a warning asking if you want to replace etc.

Starting fresh from templates and attribute files keeps you safe with new stuff. But should one also add a date or version to the composite name in order to avoid this type of problem when reusing old stuff?

[Ignacio Azpiazu]

Ignacio wrote:
Somehow related: how should one handle composite names as they evolve over time?

After several years of working pretty much on my own with my own fairly-fine-tuned system, I am now working as part of a team where composite definitions have been evolving over time, appearing during the process in different files and projects (sometimes it is the composite dimensions and fills that change a bit, sometimes it is pens only).
The problem is that when you import attributes or get a module or copy-paste an object from another file that has a 'different' composite by the same name you end up getting, for example, '4 in gyp' and '4 in gyp (1)'. Which is very upsetting and disconcerting. You don't get a warning asking if you want to keep the old, replace with the new, or rename the new.

Starting fresh from templates and attribute files keeps you safe with new stuff. But should one also add a date or version to the composite name in order to avoid this type of problem when reusing old stuff?

[Anonymous]

Ignacio wrote:
Starting fresh from templates and attribute files keeps you safe with new stuff. But should one also add a date or version to the composite name in order to avoid this type of problem when reusing old stuff?

My problem was that when I made my template file for AC9 all texture settings disappear and I don't want to start from scratch too do a new template when I use AC9 default material settings. But that problem is solved.

But I'm agree with your post. Maybe a possibility too write longer composite names than it is today? Today we can't write complete definition in composite name.

Hope you understand my sometimes bad english.

/Tobias

[Anonymous]

The problem is that when you import attributes or get a module or copy-paste an object from another file that has a 'different' composite by the same name you end up getting, for example, '4 in gyp' and '4 in gyp (1)'. Which is very upsetting and disconcerting. You don't get a warning asking if you want to replace etc.

Couldn't this be avoided by having a set of .aat's on the company's server? If loading the composite's full .aat when starting up a new project (from a company template) everybody will have the same sets. If a new composite or an existing one needs to be adjusted, give it a new name + export/update the servers .aat so that the rest of your co-workers can up load the new composite.
Also, could you a more specific system of giving (both new and old) composites names? This way it will be easier to define similar composites that f ex only have a slight difference in thickness of one material ...