Mod Question Repository... Questions come in, answers go out

Argh · Post by **Argh** » 27 Aug 2007, 01:10

Sorry, that's incorrect, PL. 1024+ is reserved for FX. 2048+ is for emitting a Weapon Particle (i.e., shooting stuff), and 4096+ is for emitting a weapon's relevant Explosion, which is actually a Weapon (kind've confusing, really, but that's how it works).

Here's an example, from my tank in PURE:

FBI:

Code: Select all

[SFXTypes]
	{
///////////////////////////////////////////////////////////////////////////////////////////////////////////////RESERVED
	explosiongenerator0=custom:SMOKEPUFF_FX;
///////////////////////////////////////////////////////////////////////////////////////////////////////////////END RESERVED
	explosiongenerator5=custom:TANKGUN_LAUNCH_FX;
	explosiongenerator6=custom:TANKGUN_GROUND_FLASH;
	}

BOS:

Code: Select all

#define SMOKEPUFF_FX 1024
#define TANKGUN_LAUNCH_FX 1024+5
#define TANKGUN_GROUND_FLASH 1024+6

FireWeapon1()
{
emit-sfx TANKGUN_LAUNCH_FX from flare;
}

One quick note about this... it really, really, really helps, if you keep the names the same everywhere! I've read through some of CA's stuff, and they use bizarre names that don't obviously coorespond with a given Unit, and they don't use the names within their BOS code. Must be a bear to work with, unless you're the guy who coded it, and you have an incredible memory :-/

Bad practice, all around- it's sooooo much easier to debug / modify if you have 1:1 matches for names throughout, frankly.

For many more examples on how to integrate FX, explosions, timed application of FX scripting into your games, etc., please read through NanoBlobs, it has a lot of examples

Pressure Line · Post by **Pressure Line** » 27 Aug 2007, 01:20

i thought Snipa was having a blonde moment and forgot how to emit fx :/

Snipawolf · Post by **Snipawolf** » 27 Aug 2007, 01:23

So, 2048 is teh number I need?

BTW, I am EXTREMELY organized. The texture is the same name of the unit name. The FX's are all in their own files, and named extremely relevant to their weapon/unit.

Snipawolf · Post by **Snipawolf** » 03 Sep 2007, 05:43

Ehhh...

Is the blue value in second textures even used? >___>

Pressure Line · Post by **Pressure Line** » 03 Sep 2007, 06:25

KDR_11k · Post by **KDR_11k** » 03 Sep 2007, 07:05

Not yet.

Snipawolf · Post by **Snipawolf** » 05 Oct 2007, 04:26

Alright, in Scriptor, in a move command.

What does [1] equal?

Peet · Post by **Peet** » 05 Oct 2007, 04:27

163840

Snipawolf · Post by **Snipawolf** » 05 Oct 2007, 04:32

Thanks, because no matter what number I entered, my move commands were abysmally small. So, I started using that, and it made them a lot larger, but more unwieldy, too.

Archangel of Death · Post by **Archangel of Death** » 05 Oct 2007, 06:28

Your scriptor lost its constants. There are many things that can cause this, including opening up more than one instance of scriptor (most common for me). You'll need to reset them (in Settings) to Linear 163840 and Angular 182.

yuritch · Post by **yuritch** » 05 Oct 2007, 08:27

Also, a [1] in Scriptor equals 1 distance unit in 3DO Builder. However, Upspring uses different units (I don't remember exactly what the ratio to 3DO Builder ones is, but it's about 1 Upspring unit to 2.8 3DO Builder's).

Pressure Line · Post by **Pressure Line** » 05 Oct 2007, 08:31

yuritch wrote:Also, a [1] in Scriptor equals 1 distance unit in 3DO Builder. However, Upspring uses different units (I don't remember exactly what the ratio to 3DO Builder ones is, but it's about 1 Upspring unit to 2.8 3DO Builder's).

my calculator says 2.8125 :) but 2.8 should be good enough unless you need super presicision

KDR_11k · Post by **KDR_11k** » 05 Oct 2007, 12:38

Should be 2.5.

When Spring interfaces a float with COB the float's value is multiplied by 65536. 65536 = 1.0 elmos. Unless you're working with OTA content you should really use [1] = 65536.

Reminds me, the build laser on the socket in KP should move 32 elmos or so, I didn't manage to figure out how many [1] that is until after the script was handed off to Zwzsg.

Snipawolf · Post by **Snipawolf** » 05 Oct 2007, 12:57

Thanks for the help guys, learning is always a good process.

rattle · Post by **rattle** » 05 Oct 2007, 16:56

Angular 182.

182.044444444444444444444444444444444...
Makes a huge difference :P

[Krogoth86] · Post by **[Krogoth86]** » 05 Oct 2007, 18:25

1.)
I saw a deployable bridge on Unit Universe for OTA (which is down now so i can't link to it). Would something like this be possible in Spring or would this totally fuck up the pathed wayfinding when loading the map?

2.)
Was there any attempt yet to do a "dying animation" i.e. to get some more satisfaction when killing a Krogoth for example (-> he would fall on his knees or something before exploding just like the Colossus in Supcom)?

3.)
I recently had a look into unit development and I still have a n00b question:
I couldn't figure out how to animate anything. All I have found yet were some "funny" maths on movement for OTA units - but even here no editor or clue how this was made (please let there be a GUI or converter for this

). So maybe you could point out what to do for animating units (and which tools to use)...

KDR_11k · Post by **KDR_11k** » 05 Oct 2007, 18:51

1. That doesn't work
2. Yes, has been in since 72b1 or so.
3. You have to use a BOS script, animating in Spring isn't WYSIWYG.

[Krogoth86] · Post by **[Krogoth86]** » 05 Oct 2007, 19:44

KDR_11k wrote:1. That doesn't work
2. Yes, has been in since 72b1 or so.
3. You have to use a BOS script, animating in Spring isn't WYSIWYG.

Thx! Concerning animating:
So there never was something like Servo (S.o. still has a working download link for this?) or another keyframe converter?

rattle · Post by **rattle** » 05 Oct 2007, 21:40

Upspring has a LUA exporter for that but I'd rather do them myself.

yuritch · Post by **yuritch** » 05 Oct 2007, 22:46

Servo should work with Spring just as good as with OTA, BOS language is the same (well, at least the part of it with which Servo deals).

Spring RTS Engine

Mod Question Repository... Questions come in, answers go out