HeatCloud / Dirt

[Argh]

... are both still using the default explo texture, not referencing the location of custom textures as documented I checked the source.

This means, among other things, that I dare not use my uber-leet new explosions in NanoBlobs 0.6 for certain things, because the texture rez is too high for ordinary explosions

[Tobi]

CDirtProjectile uses randdotstex:

Code: Select all

texture = &ph->randdotstex;

Fixed the CHeatCloudProjectile thing, heatcloud=explo.tga; is the default in resources.tdf.

[Argh]

So, now it's doing a TDFParser string search within that data? And I can use custom textures? Sweet, thanks Tobi! I didn't figure it was a big deal to fix, and the benefits will be... ah... kind've big... especially if JC ever gets that code working that allows multiple instances of a given Projectile within an explosion event...

[Yeha]

Setting texture=texturename in the explosiontdf should work for heatcloud and dirt projectiles.

[Caydr]

DDS working for all this fancy FX stuff?

[jcnossen]

especially if JC ever gets that code working that allows multiple instances of a given Projectile within an explosion event...

You can (not sure if its this version or 0.72b1 too). Use ANY unique name for the TDF section instead of the projectile class, and then put "class=ProjectileClassName" inside it.

Like:

[bwfdsreseowpntreoiutenwo]
{
class="heatcloud"
}

[Argh]

Aha!

The only thing that I still want, then, is an argument that allows for a time-delay. Then we can build ExplosionGenerator events of sufficient complexity that I can finally deploy the Nuke