Do you like your 3D model bundles shared texture mapped? Say you download models of five chairs and five tables and they all share one texture around 1024x1024 to 2048x2048. Obviously, sharing a texture map can help keep the size of your project down, but what if you only like one chair out of the set and a smaller texture would have sufficed for it? Or do you feel that perhaps shared textures tend to look not as good as a texture map made exclusively for one model?
Bump
I share textures for all the reasons you listed and try to share them as much as possible. For an object that needs a lot of detail, like a character or large prop, I’ll usually give it its own texture, but for small props or tiles I almost always use an atlas.
But are these props for your personal use or for sale? If they are for sale, how can you be sure the customer will want to use all the props in the package to justify the larger (I assume larger) texture?
I like multiple (split) textures that texture similar objects or objects that have a similar theme; like what was done in the Bootcamp demo with the buildings and bridge - they both had different meshes but shared one texture and was cleverly UVed to appear different.
So if you are making sets of chairs, make all the similar chairs use one texture, as most people will want a group of stuff rather than just one model.
This is what I do for personal projects. I don’t sell assets. My view on selling assets in a group is that people pay for the group as one, so one shared texture for multiple assets should be expected as a possibility.
I would imagine the larger the package, the larger the probability that some of its contents won’t be used. My concern is if the texture is a huge 2048x2048 for one simple chair while the rest of the models using that texture are not used. I guess if the texture is made well can be smaller and still service multiple models.