[WMCoolmon]

In some circumstances you could use set-ship-position and get-ship-position to simulate it.

Edit: Sample SEXP code.

Code: [Select]

when
<
hits-left
Alpha 1
2
modify-variable
"Target ship"
"Alpha 2"
if
is-ship-class
"Available ship A"
Target ship
change-ship-class
"Available Ship A"
"Alpha 1"
if
is-ship-class
"Available ship B"
Target ship
change-ship-class
"Available Ship B"
"Alpha 1"
etc.
set-subsystem-strength
"Alpha 1"
"Weapons"
hits-left-subsystem
Target ship
"Weapons"
set-subsystem-strength
"Alpha 1"
"Sensors"
hits-left-subsystem
Target ship
"Sensors"
set-subsystem-strength
"Alpha 1"
"Engines"
hits-left-subsystem
Target ship
"Engines"
set-subsystem-strength
"Alpha 1"
"Navigation"
hits-left-subsystem
Target ship
"Navigation"
set-subsystem-strength
"Alpha 1"
"Hull"
hits-left
Target ship
set-object-position
"Alpha 1"
  get-object-x(Target ship)
get-object-y(Target ship)
get-object-z(Target ship)
set-object-position
Target ship
99999999
99999999
99999999

[Black Wolf]

Well, after several fives of minutes of poking about I declare it impossible and Kara far too clever with sexps for his own good.

Unless he's doing what WMCoolmon suggested, which is pretty hackish really, and doesn't alter the fact that you're still Alpha 1, just in a different place (for example, your dot on the wing indicator would still be in Alpha 1's spot, etc.)

[WMCoolmon]

You can fix the wingman gauge for the target ship pretty easily.

Code: [Select]

every-time
true
set-subsystem-strength
Target ship
"Hull"
hits-left
"Alpha 1"

Of course Alpha 1 will still show up as not-dead.

[karajorma]

Told you it wasn't that hard

Theres a bit more I've added to it than that to make it less hackish but that's the basic core of the idea

[EtherShock]

Originally posted by starfox
Hey there !
This may a shot in the dark, but is it possible to implement a feature/system that gives you control of some other fighter after your original one has been blown to bitts.

In example. You are controlling Alpha 1 and your fighter is destroyed, after this, controls of Alpha 2 are given to you. This cycle would continue until your wing has been completely destroyed.

I know Freespace 2 was meant to be about Alpha 1 only. But because the game lets you decide the fighters/weapons your wingmates are using, I figured why not continue playing until your entire wing is destroyed.

I personally would find this very interesting, yet very hard concept.
Any suggestions/feedpack is welcome.

PS. If the following has feature has already been asked/gunned down.
Then I will apologise.

This sounds like XvT.

[Nuke]

Originally posted by karajorma
How does doing something like this not qualify as using a trick to surprise the player? If I give away how I did it I'm likely to see other missions based on it before MG is finished and there is no surprise involved.

It's actually annoying me that I'm getting singled out for this since I've gone out of my way NOT to keep FREDding knowledge to myself. I've set up the FRED Academy and spent hours adding explainations of how variables and the new SEXPs work to the FAQ. Isn't it enough that I spend that much time trying to teach any FREDder who asks the skills that I have?

Why should I have to give away every single trick I can think of as well?

im not trying to single anyone out here. my point was simply that i dont like the true capabilities of the engine being hidden. fancy fred programming aside. if your making an effor to pass on at least some of your knoledge you are doing the community good.

[aldo_14]

Originally posted by Nuke


im not trying to single anyone out here. my point was simply that i dont like the true capabilities of the engine being hidden. fancy fred programming aside. if your making an effor to pass on at least some of your knoledge you are doing the community good.

It's not hidden, though.  Not any more than, say, the descriptions of the tbl format for ballistic primaries.  Karas said it's more than possible, there's SEXPs there, now you can go find a way.  What could be wrong with that?

[Nuke]

ok so this was a bad example.  im not a freder so i kinda misinterpreted the whole thing. but there have been many an ocasion where i heard about a feature i was waiting on that was poorly documented. working without it for some time and then in casual discussion find out its been around for months.just sorta anoying.

[karajorma]

I agree that when someone does that it is very annoying. With FRED it's a lot harder to conceal features as everything is laid out in front of you.

Whenever a new build comes out I always take a minute or two to see what was added and ask questions if I can't figure out what it does.

With modding you can't do this so I can understand your faustration with people keeping quiet but when it comes to FRED the problem is not people being unaware of the new features, it's people not playing about with them enough to see what you can do with them.

Simulating what Starfox suggested in this thread is something that most people would simply have written off as impossible without code changes. What a lot of people don't realise is that things like this are merely tricky to do without code changes. They are most definately possible and can be very surprising when done correctly.

The other thing is that few other FREDders consider it worth the hassle of implementing hacks I suggest so I pretty much gave up suggesting them with a view to seeing them used. Now I just answer posts so that I remember it's possible