[Rampage]

Greetings from the Inferno Team.

We are not sure if this matter has been discussed, but would it be possible for debris chunks created post ship destruction not render glow maps?  We currently have a mission in development where a capital ship w/ glow maps disabled is destroyed and then have glow maps on again on its debris chunks.  Let us know if this can be done.

Rampage
INFTeam

[zookeeper]

In case it isn't apparent: it'd have to be optional.

[Nighteyes]

you know, its pretty easy to give the debris a separate debris map that consists of the original texture with burn marks on it, this way you can decide if to even have a glow map for it

[Rampage]

you know, its pretty easy to give the debris a separate debris map that consists of the original texture with burn marks on it, this way you can decide if to even have a glow map for it

True.  Although it has been standard practice to UVmap capital ships and give their debris their own textures, we still tilemap most of our capital ships to save time.

R

[FreeSpaceFreak]

In case it isn't apparent: it'd have to be optional.

As I understand it, the ship had glowmaps disabled by SEXP - so it would just be a matter of not switching them back on on destruction.

[Rampage]

As I understand it, the ship had glowmaps disabled by SEXP - so it would just be a matter of not switching them back on on destruction.

It automatically switches back on when the debris chunks form.

R

[FUBAR-BDHR]

I don't think there is a good solution to how this would work.  There are a lot of ships that have separate debris maps with glows (some animated).  Since there is no way to specify what map(s) to disable glows on disabling them all might work for some but not for others.  Even making it optional just leaves the problem for half the people. 

The easiest solution I can think of here is texture replacement.  Have you tried replacing the -glow texture with something like nothing.dds (assuming you have one) instead of using the sexp? 

[zookeeper]

The easiest solution I can think of here is texture replacement.  Have you tried replacing the -glow texture with something like nothing.dds (assuming you have one) instead of using the sexp?

Nope, the effects of texture replace don't extend to debris.

[FreeSpaceFreak]

As I understand it, the ship had glowmaps disabled by SEXP - so it would just be a matter of not switching them back on on destruction.

It automatically switches back on when the debris chunks form.

Exactly, that's what I meant - the code would need to be adapted to remember the disable-glowmaps across destruction, instead of resetting it.

[FUBAR-BDHR]

And what do you do if you want your ship glow maps disabled but not your debris ones?  See this issue?

Now the issue with texture replacement not carrying over to debris sounds like a bug (one that I believe is reported but not 100% on that). 

Of course what really needs done is fixing all the texture replacement bugs and allowing for it to be done via sexp.  Then instead of globally disabling glow maps you could disable the specific maps you want by setting alternate textures. 

[Valathil]

what about making a copy of the model reskinning the debris without glowmaps?

[FUBAR-BDHR]

Waste of a ship slot just for one mission.  That is what texture replacement is for. 

[Trivial Psychic]

Would it be possible to have some special texture controls within the ship's table file?

$Texture Modifications:
+LOD: Debris
+Texture: hull-texture-01
+Glow Disable: YES

[Valathil]

yeah coding, testing and debugging an extra feature just to do that is much less wasteful

[Dragon]

An extra feature could be used by other mods that would also want the effect. An extra ship class is an ugly hack with it's own set of problems.