- Joined
- Feb 4, 2008
- Messages
- 3,511
(Just in case it was never brought up before)
So, uploading models here have this weird quirk where it forces you to upload textures that is not already in wc3 once for each model in the package.
I get the intention: Make sure custom textures is uploaded with the model.
The problem is that it does not check whether the texture is already in the pack.
So you have to upload the same texture once for each model, even if they use the same texture.
In model submissions where every model uses the same texture, like the modern barrels (4 models) I uploaded recently, this means the texture is included in the pack four times.
This cannot be an intentional design choice? It makes the model pack four times as big, since the texture is by far the largest file. Also, does it not absolutely overfill hiveworkshops database in the backend? I cannot imagine there is any advantage in doing it this way.
So, uploading models here have this weird quirk where it forces you to upload textures that is not already in wc3 once for each model in the package.
I get the intention: Make sure custom textures is uploaded with the model.
The problem is that it does not check whether the texture is already in the pack.
So you have to upload the same texture once for each model, even if they use the same texture.
In model submissions where every model uses the same texture, like the modern barrels (4 models) I uploaded recently, this means the texture is included in the pack four times.
This cannot be an intentional design choice? It makes the model pack four times as big, since the texture is by far the largest file. Also, does it not absolutely overfill hiveworkshops database in the backend? I cannot imagine there is any advantage in doing it this way.