[SOLVED][FTE]Retrieve entity shader in CSQC

[toneddu2000]

[Shpuld]

Considering that it's possible for an entity to be using multiple shaders, this sounds like a difficult thing to achieve. I'd approach the problem by maybe having custom fields where you can manually set the "default" shader for that entity, or just have default shaders for different types of entities stored in constants or something, might not be applicable for your case though.

What I would like to see would be being able to remove forced shader without having to actually know the originals, the engine should already know it.


EDIT: Actually that seems to work, if you do self.forceshader = 0; it seems to use the original shader again

[toneddu2000]

self.forceshader = 0; works like a charm, even on multi material entitities! incredible, it was so simple!

thanks a lot Shpuld, you saved me LOTS of head-walls interaction!

[Spike]

[toneddu2000]

thanks Spike for the explanation, but still I don't understand how skin format is structured, could you please post a .skin example? And which name should I use? I saw that SteelStorm (2011, Darkplaces engine) uses the format foo.dpm_0.skin. Steel Storm used dpm model format, but it's the same. Is it right the nomenclature?

Thanks

[Spike]

you pasted it yourself, loadcustomskin's documentation specifies the accepted .skin file lines (ie: replace "surfacename" "replacementmaterial" one line per surface you want to override).
Also, use those optional args (and give an empy skinfilename) to avoid using actual files, generate that data at runtime if you want.

the foo.iqm_0.skin etc files are automatically parsed by the model loader (in both fte and dp) by just concatenating it onto the end of the model's name, and thus are limited to just replacements. Its probably worth noting that many model formats(md3/iqm/dpm) don't support numbered skins (like those used for progs/armor.mdl) but this gives you a way to define them without any extra code.
Steelstorm is a viable example I suppose, Xonotic also has a number of similar overrides.

[toneddu2000]

Yeah, thanks Spike I only tried the foo.iqm_0.skin replacement, probably that's why it didn't work. I'll try to use custom skin and see if it works, I'll try also optional args to create skins on the fly
Thanks both for you help!