[LtNarol]

isnt there an easier way to do this? like have the beam map tiled and translate in the direction in which the beam is 'shot'?  Then all you have to do to get different effects is change the map; which would look smoother anyways.  Some upsides is that it could be useful for other kinds of beam stuff as well

[Sesquipedalian]

That's what I was saying for the sine and cosine waves, Lt. Narol.  The helices (no, that's not a typo) can't work the same way, because they have to be 3D to look right.

[Bobboau]

this could be very cool, and the code could be used to improve other things like the damage archs

[Anaz]

My friend and I worked out some stuff for the z position of the beam:

z = sin(x) + sqrt(-(y * y));

Hope that helps!

[Goober5000]

Originally posted by Analazon
z = sin(x) + sqrt(-(y * y));

I didn't know fs2_open could handle imaginary numbers.

[Rampage]

Originally posted by Analazon
My friend and I worked out some stuff for the z position of the beam:

z = sin(x) + sqrt(-(y * y));

Hope that helps!

Nah!  Try using vector graphs.

r(t)=2cos(t)i+2sin(t)j+tk

Vectors rule!

[Anaz]

Originally posted by Rampage


Nah!  Try using vector graphs.

r(t)=2cos(t)i+2sin(t)j+tk

Vectors rule!

meh....I'm not familiar with how DirectX works...and this was a 30 second thing. I think the - needs to be moved outside of the sqrt() in what I wrote...

[Goober5000]

That would make more sense.  In your first formula, you were taking the square root of a negative number.