Selecting different skins for func_model

[y00tz]

Basically allowing us to specify what skin we'd like to apply to a model.

[Garrett]

Basically allowing us to specify what skin we'd like to apply to a model.

So this will let us customize our player model like they let you do in Warsow?

[ViciouZ]

Nope, only in maps. (func_model)
There was player skin support in quake2 but it was removed.

[i_am_a_pirate]

Nah, too confusing. You're on 1 map, play for an hour and get totally confused with the next map being different player models. What if the mapper doesn't quite do them good enough and the teams look almost identical. Don't do it, jits

[ViciouZ]

Nah, too confusing. You're on 1 map, play for an hour and get totally confused with the next map being different player models. What if the mapper doesn't quite do them good enough and the teams look almost identical. Don't do it, jits

Read the thread. Make sure you have any idea of what you're talking about. I might have to write a stern letter to the Guardian complaining of my outrage, or tut loudly on your answering machine.

[y00tz]

Honestly, I should have just made this so I couldn't be misunderstood.

I'm requesting that when you add a new func_model entity, i.e. in BSP or whatever map editor you choose, you can add a key to it along side the keys it currently has. For example, just as you would specify the model key (/models/plants/bigleafx.xxx) you could also specify the skin (/models/plants/y_leaf.tga).  But the new key would allow you to select a different skin for the model, i.e. custom  textures for plants, different trees using the same meshes, and bright and dark textures for use in different mapping/lighting styles.

[Deranged]

This is an awesome idea, I have a tree I modeled a long time ago with 4 different skins for it depending o nthe time of year, and this would make it much more usable when I trim the polycount and start using it

[Garrett]

I like this idea.  Is it much work implementing something into BSP?

[jitspoe]

Code: [Select]

gi.setmodel(self, self->model);
self->s.skinnum = self->skin;
gi.linkentity(self);
It's already implemented.  I'd advise against using it with skm's, though, as the download system doesn't currently handle .skin files.

Edit: I should clarify: the skin is just an index.  You have to map the textures in the model itself.  I can't remember if you can store multiple skin references in skm's or not.  You can in md2, though, and md2's are probably sufficient for static meshes.