 |
In reference to option 2, if we called it a playlist mappers could just copy and past textures into said list inside DR. The list would just contain the info on the textures and wouldn't require any writing to the material definition at all. It would be handy if the mapper was able to save the list to a file, so could include it with thier mission etc. |
|
|
I like the idea of the mapper controlling this inside DR, putting textures into different family groups of their own making. I think that relying on tags or anything that lives in the material files will fail when new textures are added and the contributor forgets to add the tags (or whatever). I've already experienced this failure with the addition of new stone textures that are vine-friendly, but where the contributor failed to add that to the material definition. |
 |
Oh yeah, I forgot to add that. I was thinking about a Themeeditor inside the texture browser. You just click "Create Theme", choose a name (i.e. virtual folder) for the theme and simply pick textures from within the texture browser. The textfiles would be created automatically. In a similar fashion, you'd be able to edit existing themes, with the option to remove textures from it as well. Also, the texture editor would be toggleable between materialfolder based browsing and themefolder based browsing. |
|
|
It has also been suggested to extend this thing to the whole assetbase. Themes would contain all kinds of things, like sounds, prefaby, materials etc. |
- Anonymous
