[LAW ENFORCER]

I need to know! About engine glows, I though I saw a pussycat, err... engine glows unglowing (OFF) when blowing up PER engine but when I try even if you destroy 8 out of 9 engines they are still ALL their (I matched up the thrusters to their names in PCS) Any info there?


I would also like to know if anyone knows any info or 'of' any info about editing beams... Which entries effect the beam and which don't, what files do what, what a 'section' is etc... ??? well??

------------------
I like to MOD!
I can try and make an entire TC myslef.
GRDLA, TSC, SSPF, Bandits, Aliens - ah pants!
 www.ARMOUREDSTAR.com

[vadar_1]

um, well your question about the beams, just open weapons.tbl and its pretty easy... the comments are very helpful too

[LAW ENFORCER]

Yes I know, I have edited some beams I know quite a lot, but not ALL and not enough about beams!

[WraithHost]

I think it has something to do with what you put in the thruster properties section .

'$engine_subsystem = $NAME' where NAME is the name of the subobject the engine is tied to.

[Zeronet]

Check out Freespacewatch, they have a weapons tutorial.

[LAW ENFORCER]

Wraith, yes I know but when I put in the names of my engines it dosn't work, can they be letters for the name? or actualy geomertery for the engine?

That weapons thing looks bigger than the last time I saw it (or something very like it)
but it had nothing about the 'section' thing...

Thanks anyway

[Starwing]

I think the "sections" are the "layers" of the beam, in z direction.

[LAW ENFORCER]

Beams are 2D which way is Z?

[Starwing]

z is towards the player. Beams are not really 2D, they consist of several layered 2D planes.

[LAW ENFORCER]

they 'look' 2D... I though you meant like layered up ontop of each other but coud't be sure, can some sections be hidden behind others? what determins the layer order?

[WraithHost]

I think NAME is the name of the destroyeble subobject that makes the engine geometry.

Check out a Volition model.

[Starwing]

Code: [Select]

$Section: ;; one section of the beam (you can have up to 5)
+Width: 62.0 ;; width of the section
+Texture: enemybeam ;; texture for this section
+RGBA Inner: 255 255 255 255 ;; rgba values (only for non-textured beam compiles)
+RGBA Outer: 150 150 150 10 ;; rgba values (only for non-textured beam compiles)
+Flicker: 0.1 ;; how much it flickers (0.0 to 1.0)
+Zadd: 2.0 ;; hehe
$Section: ;; one section of the beam
+Width: 140.0 ;; width of the section
+Texture: enemybeam ;; texture for this section
+RGBA Inner: 160 160 0 255 ;; rgba values (only for non-textured beam compiles)
+RGBA Outer: 60 60 0 10 ;; rgba values (only for non-textured beam compiles)
+Flicker: 0.1 ;; how much it flickers (0.0 to 1.0)
+Zadd: 1.0 ;; hehe
$Section: ;; one section of the beam
+Width: 165.0 ;; width of the section
+Texture: enemybeam ;; texture for this section
+RGBA Inner: 255 0 0 255 ;; rgba values (only for non-textured beam compiles)
+RGBA Outer: 60 0 0 10 ;; rgba values (only for non-textured beam compiles)
+Flicker: 0.1 ;; how much it flickers (0.0 to 1.0)
+Zadd: 0.0 ;; hehe

That's from my X-ray beam. The first line shohs how wide this layer is, and the zadd shows the z offset from the lowest layer.   put the widest layer as last, but probably that doesn't matter, since the zadd value determines the offset the layer is placed to.

[LAW ENFORCER]

Thanks! The rest seems noraml, flicker, RGB values (If you want solid colors I supose) but what is the A for in RGBA, additive? is that trasparency?

Wraithhost, mabey I ddin't explain my self clearly...
I have geomerty engine subsystems (they explode to!) but when I do a thruster, and put the $NAME into the PCS textbox (in engines bit) (after the other letters) you have to destroy ALL the engines to kill the lights... in ANY order... as if they connected to the engines but not to EACH engine... Is this becasue I use letters enginea, engineb etc? (Truespace2!) or mabey because it has real geomertry?

[Starwing]

I have no idea, but those are unused if you use a texture for your beam.