Little issues with some textures "file names" when exporting (new fantasy morph armors and others)

Ellessarr

hello guys, i have take the advantage of the "still madness" and some extra money from my store credit and have bought both male and female morph armors and while it's really awesome and i really loved it and have a very good poly count i've ended with a small issue with it, which to be fair is not the "first time" it's happened and i've noticed it with others "armors aswell like the dark hunter armor

https://www.daz3d.com/dforce-the-dark-hunter-for-genesis-8-females

 

each of the "armor piece" basically have the same "file name" like for exemple base_color, while inside daz it's not any deal "outside daz" exporting to outside daz it's a big problem, because the "exporting system from daz get "confused" with the names and only export 1 single texture" choosen randomly from all pieces (he choose one of the pieces then export to a file) then all the pieces in the armor will use that "file" making the armor look crazy, while i can understand which i can just go and open the armor "folder" to copy all the right textures the fact which all share the same name means which i must rename all the pieces or put in a new folder, well "basically some "extra work".

 

would be good if the "creators" could pay attention to this and don't do that when creating they stuffs" could be just add at the end of the name something like "base_color_leg(for legs) which would be much better than just keep everything with the same name.

 

i found tha issue only with a 'few new stuffs" most fo the old stuff and even news don't have that issue just "some of the new or maybe armor outifts with "many parts which feel like the creators are being a "little lazy" here by using the same "generic name" for the base color texture for all the armor pieces.

FSMCDesigns

To be fair, if it works fine in Daz Studio, there really isn't a problem. I agree though, when tweaking/editing textures is does get a bit confusing with the naming. Since it seems to be directly related to how Substance Painter outputs textures, that is probably the reason we are seeing it more and more since more users are using SB.

WendyLuvsCatz

yes I find similar texture names excruciatingly annoying in DAZ studio itself too when presented with that list wanting to swap a diffuse out etc

I often want to customise clothes even in studio for a render mixing the presets

Ellessarr

FSMCDesigns said:

To be fair, if it works fine in Daz Studio, there really isn't a problem. I agree though, when tweaking/editing textures is does get a bit confusing with the naming. Since it seems to be directly related to how Substance Painter outputs textures, that is probably the reason we are seeing it more and more since more users are using SB.

well to be fair substance paint have option to "rename" the texture before save it if you want", normally the name of the texture in SP is associated to the "material name" you create, then if the material name have "diferent names" then its not supposed to generate the "same normal for all textures" of all pieces, as long each piece have a own material name.

 

   And is really a lot annoying that "Same name stuff".

SickleYield

I also received your DM about this, but at this point I don't think I would ask @Sade and Moonscape to redo all the texture names when the product is already published. This would require editing all the materials and resaving each of the armor pieces, and that's work we don't get paid for on a product that works fine for what we sold it for (rendering on G8 in DS).

Ellessarr

SickleYield said:

I also received your DM about this, but at this point I don't think I would ask @Sade and Moonscape to redo all the texture names when the product is already published. This would require editing all the materials and resaving each of the armor pieces, and that's work we don't get paid for on a product that works fine for what we sold it for (rendering on G8 in DS).

thanks for the replay well i will try to talk withthen about it, anyway at last it would be good "remember for the next works time" to avoid it in the future.