02 Feb 12, 12:02PM
(01 Feb 12, 07:01PM)tempest Wrote: Well, I don't know, but IMO it just makes more sense to keep things together that belong together, e.g. model and skin.tbh it won't really make much a difference since the whole process would still be the same, on the other hand (now it's the modeller talking) having all skins in a single folder will be easier to find a texture.
An idea would be to use a more specific structure for models which share a skin (and therefore are probably similar in other respects as well), if they already exist. Like this:
And you'd use it as md3skin "../skin.png". Otherwise, if you want to add such an additonal model later, you'd just put it into a separate broken_bench directory and use md3skin ../bench/skin.png And if you want to use the bridge texture on the gas tank, that would be possible as well.[SELECT ALL] Code:mapmodels
>| benches
>| bench
| md3.cfg
| bench.md3
>| broken_bench
| md3.cfg
| broken_bench.md3
| skin.jpg
(01 Feb 12, 07:01PM)tempest Wrote: The problem with this is how it currently worksAs I said I had no idea on how it works, now you've explained it a bit but I need more infos, I'll try to get hold of you folks on irc.