CheapAlert wrote:Usually, you're supposed to retain the original path to the skin. Yes, that means making a models/blah/blah folder where the model points the skin to. To find the skin path, try opening the model up in QuArK and look at the skin name in the tree.
Yech.
/me wonders again why iD chose to move away from just keeping the skin inside the model itself
Dr. Shadowborg wrote:
/me wonders again why iD chose to move away from just keeping the skin inside the model itself
It allows you to add new skins without having to replace an entire model, and allows multiple models to reference the same skins. This can save a lot of hard drive space and time.
Miles Invictus wrote:
It allows you to add new skins without having to replace an entire model, and allows multiple models to reference the same skins. This can save a lot of hard drive space and time.
Well, I think it would be very nice to have the option to reference the skin path relative to the model's location... instead of relative to the mod root directory.
But I can see your point on the reuse etc issues.
So, I can add more skins without changing the model? Please expound!
When my computer inevitably explodes and kills me, my cat inherits everything I own. He may be the only one capable of continuing my work.
Well, I thought you'd be able to...but I've been searching like mad for something that explains how the hell it would be done, and I haven't found much. I found one thing, from dpextensions.qc. It sounds like you should be able to do it by naming your skin "modelname_#.tga", where # would be a number higher than what the base model has. Then you set your entity's skin to be that same number. I don't know if it only works with mdl files, but it's worth a try.
From dpextensions.qc:
mdl/spr/spr32 examples:
skins are named _A (A being a number) and skingroups are named like _A_B
these act as suffixes on the model name...
example names for skin _2_1 of model "progs/armor.mdl":
game/override/progs/armor.mdl_2_1.tga
game/textures/progs/armor.mdl_2_1.tga
game/progs/armor.mdl_2_1.tga
example names for skin _0 of the model "progs/armor.mdl":
game/override/progs/armor.mdl_0.tga
game/textures/progs/armor.mdl_0.tga
game/progs/armor.mdl_0.tga
note that there can be more skins files (of the _0 naming) than the mdl
contains, this is only useful to save space in the .mdl file if classic quake
compatibility is not a concern.
bsp/md2/md3 examples:
example names for the texture "quake" of model "maps/start.bsp":
game/override/quake.tga
game/textures/quake.tga
game/quake.tga
Wow, havn't posted here in years, but I still occasionally lurk.
As you said you were looking for mechanical enemies, have considered making one from the mech model used in colony/some other mods. May or may not be the same model from BattleMech.