[Anaz]

Originally posted by CP5670
A non-projectile based weapon? Maybe something that uses a stream of randomly-aimed particles emanating from the ships. (would be useful for "lightning cannons" or flamethrower-type weapons)

flamethrowers are actually quite easy to make. Just make an image where the weapon is a ball, set its refire rate to something very low, range to something quite short, and there you have it!

[Setekh]

Originally posted by Analazon
flamethrowers are actually quite easy to make. Just make an image where the weapon is a ball, set its refire rate to something very low, range to something quite short, and there you have it!

I think what would distinguish a flamethrower from something like that is a gun that fired in pretty random directions, within a set domain, rather than on a straight direction...

I wonder if flamethrowers would work without an atmosphere, anyway...

But then... oh, crap! Better support for atmospheric stuff?

[Sesquipedalian]

I had a situation where is-tagged wouldn't be redundant.  I was quite unhappy that it didn't work.  Has-been-tagged only returns true once, and I needed an event that would trigger every time the ship was tagged, not just the first time.

[Carl]

option in weapons TBL weather you want your laser to have additon transparency (darker pixels are more transparent) or multiply transparency (lighter pixels are more transparent)

someting like,

$trans:  multiply

this would be cool for creating smoke or dark matter lasers.

[EdrickV]

Originally posted by Sesquipedalian
I had a situation where is-tagged wouldn't be redundant.  I was quite unhappy that it didn't work.  Has-been-tagged only returns true once, and I needed an event that would trigger every time the ship was tagged, not just the first time.

You can use has-been-tagged multiple times if you set the event to repeat with about a 20 second interval. From what I've seen is-tagged was supposed to do the exact same thing, without the delay. The way it's written suggests it was a quick hack for testing other junk.

[Setekh]

Originally posted by Carl
this would be cool for creating smoke or dark matter lasers.

Only so useful... in the blackness of space, you won't be able to see Multiply Smoke for most of the time. What you really need is 32bpp image support... then you can have real transparency in there, not just relying on a white or black background to blend your image on.

[Kellan]

Originally posted by Setekh


Heh heh, how much text have you lost to that b1tch of a bug, Kellan?

Oh, about half the Derelict script just fell off the bottom of the CBs...if someone could fix this, I won't have to create 2 versions of BWO for 1024 and 640 users.

Bah.

[Shrike]

Yeah, it's an annoying bug all right.... like the failure of briefing text to wrap some times.

[Terawatt_99]

i've got an idea that might be possible, but probably impractical;

a capital ship mod:

it would have to be arranged before hand who would do what, and it would take a great deal of co-ordination to do it, but the way i'm thinking of it is this:  several people on turrets, either a person per turret, or a couple of people using several turrets each, let me explain:  each turret would be assigned a specific button (user definable) and a person (if controlling multiple turrets) could use the regular targeting method for defining what ship to shoot at, and each button, when pressed, would fire the assigned turret.  there could also be a navigator, controlling the movement of the ship, although this would require patience, which most people playing multiplayer games don't have and possibly someone controlling fighter launches, but the fighters would be controlled by bots, hopefully with improved skill over the current fs2 computer pilots


anyways, you can see why this would take a group of dedicated players, with some good coordination skills

anyways, that's my idea...  wow, what a first post...

[Setekh]

Heh, that's certainly a big idea.

And welcome to HLP, Terawatt.

[heretic]

tables, animated textures, higher polys, oh my.

[kode]

easier mod handling, perhaps one directory for every mod, instead of overwriting existing files...

[Black Wolf]

There is only 1 thing which I want to begin with...

 - Beam Free All...by default! B the Way, as long as Daveb is floating around this forum anyway, why the hell did you guys make beams locked by default anyway?

[Terorist]

Originally posted by Terawatt_99
i've got an idea that might be possible, but probably impractical;

a capital ship mod:
 ....
anyways, you can see why this would take a group of dedicated players, with some good coordination skills

anyways, that's my idea...  wow, what a first post...

Reminds me of Warbirds.
I tried it out online, once... One of the things you can do is to man a gunner's seat. I went on a bombing run in a B-17 and manned one of the guns. It involved a somewhat long wait from the field to the target, with nothing to do but chat with the pilot using the intercom, and other pilots with radio. But when enemy fighters appeared, it was quite thrilling.

In Freespace the battles come up faster, so there's less waiting. This could be fun, worth a try?

[LtNarol]

about the new sexp setup, i think it would be very nice if keep the regular SEXP setup but add an option to script lines manually so someone fluent in the language of programming can bust out and make some new funtion that he/she has always wanted to do without making it impossible for us non-programmers to build missions  compromises are nice.

[Unknown Target]

Someone should really fix the graphics code, where whenever the game has a number of ships, it gets super choppy.
Also, could someone get rid of the [forgotten] FRED 2 bug, where it crashes if you put over....60, I think...

[heretic]

Originally posted by kode
easier mod handling, perhaps one directory for every mod, instead of overwriting existing files...

yes- a "mod" menu like q3 has- that just looks for tables in a different directory, and uses ones there instead of default ones.

[CP5670]

Oh, about half the Derelict script just fell off the bottom of the CBs...if someone could fix this, I won't have to create 2 versions of BWO for 1024 and 640 users.

The command briefings in PI might have this problem as well; I'm not sure at the moment, since FS2 doesn't work for me at all on 640x480. (same results on other computers; I think that my CDs might be damaged) This is one place where a team of testers comes in handy.

I think the whole thing could be fixed by simply locking the menu resolution on 1024x768 regardless of the in-game resolution. Computers that cannot run the game properly on 1024x768 would still have no trouble with the menus on that.

On a side note, has anyone tried searching for the exact code for the "U.R.A. Moron" thing?

[EdrickV]

Originally posted by CP5670


On a side note, has anyone tried searching for the exact code for the "U.R.A. Moron" thing?

void fix_ship_name(int ship)
{
   int i = 1;

   do {
      sprintf(Ships[ship].ship_name, "U.R.A. Moron %d", i++);
   } while (query_ship_name_duplicate(ship));
}

Fred2\Management.cpp

[Carl]

Originally posted by Setekh


Only so useful... in the blackness of space, you won't be able to see Multiply Smoke for most of the time. What you really need is 32bpp image support... then you can have real transparency in there, not just relying on a white or black background to blend your image on.

real transparency never looks good for some reason. it would also double the number of images you need for a weapon. IMO just using addition and multiply would be a big space and time saver.