[CP5670]

The fighter AI is actually the thing that I would most like changed; if only I knew more C++ I would start working on that myself. They really need better algorithms for close-up fighting. Currently, all they do is simply run circles around you without firing anything as long as you are facing them; they should try to run away instead and come back for another attack run. Some sort of collision detection might be useful as well, as I'm sure we have all seen AI fighters crash repeatedly into their wingmen (without making any attempt to move away) when trying to fly the same path.

[Mr. Vega]

Originally posted by CP5670
One thing I forgot to mention in the other thread that might be nice is to have the player's weapons become slightly more powerful when all of the available energy is diverted to weapons. Maybe something similar could be done with shields as well. The effectiveness multiplier shouldn't be very high, but there should probably be some small bonus for having energy on weapons.

I think the main reason that's not there is because having the weapons at higher power level would burn out the heat sinks.

[Alikchi]

Well then, that's a risk you take sometimes.

[Darkage]

I think we should focus on simple modifications rather then code intensive stuff. aim for stuff like the ambient lighting Avenger/malard added. We can add biger modifications later when the programes have a better look at the code.

[Ashrak]

it's a risk allright and not a small one but when you are facing 8 shivans you have 20% hull integrity and 1 wingman you divert all power to weapons and engines to take out as many of them as you can why tha heck is the VWBB down?

[Sesquipedalian]

My first request would be to have those SEXPs which don't function (i.e. orders, is-tagged, another one that I forget now) fixed so that they start actually doing what the Help says they do.

Secondly would be the addition of more SEXPs, or better yet the ability to create them as a Fredder saw fit.  Perhaps a programmer could make us a program that scripts SEXPS to be inserted into the engine.  Then one could even post new SEXPs on a board somewhere for others to download and install in their engines. :D:D

[Alikchi]

Here's another for you. Make some SEXPs applicable to jump nodes i.e. the ability to make it invisible, etc.

[Kellan]

Please dear God, just make some sliders for the Command briefing screens....

[Alikchi]

Oh, that reminds me! Let quotation marks be used in messages and briefing and etc.

[an0n]

Originally posted by Alikchi
Here's another for you. Make some SEXPs applicable to jump nodes i.e. the ability to make it invisible, etc.

Uh....no. Jump nodes are just HUD projections of recorded nodes and probably some sensor data. If they're invisible, then they wouldn't be detected and wouldn't be on the HUD.

[Alikchi]

Well, for one mission I'm doing, you discover a new jump node. Command scans the area and the node is SUPPOSED to pop up on radar. Unfortunately, it can't do that because FRED 2 doesn't see it as a ship.

[Nico]

Originally posted by Alikchi
Oh, that reminds me! Let quotation marks be used in messages and briefing and etc.

not possible, they're usind to start/end the comm if you look at the txt version.

[CP5670]

The quotation mark thing is fine; you just have to use two apostrophes instead. (they look exactly the same as quotes in the game) It might be nice to have semicolons allowed, though.

[mikhael]

Originally posted by EdrickV


SEXPs can do pretty much the same thing, except using a percentage rather then absolute hp value. It's rather pointless though, support ships don't repair the hull. (Though they could with the right SEXPs or code changes.) SEXPs are a scripting language, just not one where you type everything out and have to worry about typos.

Rip out the SEXPs, attach something like the python runtime library to the project and the reimplement SEXPs in python (or other scripting language). Why? Because one of these minutes, I'm going to think of something you can't do with any combination of SEXPs. Better yet, I'm going to think of something you can do with an ass-backward combination of SEXPs and would rather do with just one clean new SEXP that I can code myself and hand out as a single unit.

Oh and while were requesting things, lets make texture transparency colors and transparency channels work, 'kay?

[Nico]

Originally posted by mikhael
Oh and while were requesting things, lets make texture transparency colors and transparency channels work, 'kay?

actually: make them work on voodoo cards too
semi transparency, tho, that would be neat too
Nut on a side note, that would be better if the opactu of a map could be set directly in a pof editor ratnher than in the modeller, coz that would be another converting pain...

[YodaSean]

I want higher resolutions

[Bobboau]

yes I would like ambiant mapping

[##UnknownPlayer##]

I would note that given all the suggestions coming in here we need to have someone set up an online source database where all the generally agreed upon changes can be sent to be included. FSF especially needs this.

[Setekh]

Originally posted by Kellan
Please dear God, just make some sliders for the Command briefing screens....

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

[EdrickV]

My first request would be to have those SEXPs which don't function (i.e. orders, is-tagged, another one that I forget now) fixed so that they start actually doing what the Help says they do.

Well, I found out why order doesn't work. Even you non-programmers can get this:

int sexp_order(int node)
{
   return 0;
}

Is-tagged is redundent and I think was made earlier then has-been-tagged-delay. The code is a lot simpler and doesn't have very good checking for unusual situations. (Like checking to see if a dead/not arrived ship is tagged.) Error will work under debug builds but not under release builds. It calls int3() which does nothing on a release build. Ship-Guardian and Ship-No-Guardian work but not the way you might think. Find the "Most Useless SEXPs" thread in FS Modding for details.

As far as ripping out the SEXPs, that would screw up backwards compatability with regular FS2 missions. If possible, some sort of SEXP set to use functions from some external scripting system might be useful to some people, but I doubt all the mission builders want to learn a whole new scripting language. Something like the system D3 uses: Regular Dallas scripting with support for scripting via C.