[Falcon]

Is there a way that we can loop certain events like one event enabling another event.

Heres what Im trying to do. I trying to set up an event where I enable the AI by a certain key but when another key is pressed it will deactivate it. And I want this continous to go over and over and over activating and deactivating it whensoever I please.

[karajorma]

Ah. The bane of FREDders. The linked repeating event.

Quite simply can't be done on retail.

Don't know about FS2_Open though. It didn't work last time I tried but this may have been fixed now.

[Goober5000]

Didn't CP figure out how to do this in retail?  I'm pretty sure he did because he said it no longer works in FSO.

[karajorma]

Originally posted by Goober5000
Didn't CP figure out how to do this in retail?  I'm pretty sure he did because he said it no longer works in FSO.

I tried several different ways and could never make it work. The first event repeats normally. The second event screws up (I can't remember if it just keeps repeating based on the interval time or just happens once but either way it doesn't work properly).

[Falcon]

Im using the Fredd_open version.

Oh another thing how do you get skyboxes to work to?

In Freed_open

[Arc]

Wasn't the FSO code changed to allow a -1 Repeat Count so an event would repeat forever? Err... or was that one of argv's changes that got removed...
(<- amateur FREDder, probably wrong)

[karajorma]

Originally posted by Arc
Wasn't the FSO code changed to allow a -1 Repeat Count so an event would repeat forever? Err... or was that one of argv's changes that got removed...
(<- amateur FREDder, probably wrong)

The problem is not getting the event to repeat forever. The problem is getting the second event which is linked to the first to repeat too. It never worked when I tried it. I might give it another try later today and see if it works now.

[Sesquipedalian]

Originally posted by Falcon
Is there a way that we can loop certain events like one event enabling another event.

Heres what Im trying to do. I trying to set up an event where I enable the AI by a certain key but when another key is pressed it will deactivate it. And I want this continous to go over and over and over activating and deactivating it whensoever I please.

Variables are your friend.  

1) Create a variable with a default value of zero
2) Create an event that sets the variable's value to 1 whenever you press the key you want.  
3) Create  a second event that sets the variable back to zero whenever the other key is pressed.  
4) Give both of these events repeat counts of 999999999999999.
5) Create a third event that says:

Code: [Select]

when
   =
     
      1
   
6)  Create a fourth event that says:

Code: [Select]

when
   =
     
      0
   

Give the third and fourth events repeat counts of 999999999999999 as well.

Should work.

[karajorma]

Hmmmm. Never tried that method. I was using chains but I could never get it to work with them. I'll have to give that a try.

[SadisticSid]

I've tried that in the past and it doesn't work because FS2 doesn't re-evaluate the when condition after the first time the event has fired. Has this changed?

[Goober5000]

It does for some sexps, not for others.  Not sure if the = sexp is included among them.

[SadisticSid]

I'll test this when I get back to Birmingham, if the variable method works now it'll allow me to make a cool Inferno mission I've always wanted to script

[Sesquipedalian]

One thing I should add about this method: it will repeat the action of the third/fourth event every time the event repeats.  So you may have to fiddle with this basic method depending on what sort of action you are trying to accomplish.

In the case of assigning an AI class to a fighter, it doesn't matter if the class is reassigned every second, so this will work as it stands.  If the purpose were to fire a beam, one would need to drop the fourth event, and set the repeat interval on the third event to match the usual fire delay of the beam.  You probably get the idea.

[karajorma]

Aha. I thought that might be the case.

[kasperl]

if you don't want an eternal loop on the action events, why not end them with setting the var to 3, or 2, or a or something?

so you get
when var = 0 then
when var = 1 then
when key1_pressed var = 0
when key2_pressed var = 1

[Goober5000]

[Sesquipedalian]

Precisely the sort of tweaking I mean, kasperl. In my firt post I was laying out the basic method.  With my beam example I was giving one example of how it can be modified depending on the action one wants to execute.

[karajorma]

I tried it. We're back to me being correct in the first place by the looks of it.

The problem is the = SEXP I suspect. I created the mission like this



Both events have a high repeat count (999999 or something). When run in the mission everything is fine until you press 1. Once that happens the message is repeated continually.

That's exactly what I saw when I tried this the first time using chained events. Unchaining and going on variables did nothing. Obviously the = SEXP is only evalutated once.

[Goober5000]

Okay, try this:
http://www.swooh.com/peon/Goober5000/fs2_open_r.zip

FRED your test mission, then go into Notepad and change the "when" to "every-time".  Then load it up in this build and see if it works.

[Trivial Psychic]

Goob, you wouldn't be trying to slip a new feature in during a code-freeze now would you?

*flees in terror as Goober's BFGreen charges up*