Random() not working

[LostOblivion]

1.

 

I'm trying to insert a random fighter attack into my mission with 33 % spawn chance that should happen 180 seconds after a flag has been set, but it seems to spawn all the time. Does the random condition only work alone?

 

ONCE(Random Attack)

 

RANDOM(33)

TIME SINCE FLAG(3, 180)

 

GROUP ACTIVATE(Rus Fighter)

 

2.

 

I've made a CAP flight that I've given the Engage Targets Enroute Task within 25 nm, but they still seem to fly anywhere and shoot down everything. Do I need to turn off the CAP ET completely and only go with the Engate Targets ET?

 

I've done the same with SEAD, and afaik it only seems to attack within 25 nm of its route when both SEAD ET and Engage Target ET is on.

Edited August 2, 2011 by LostOblivion

[GGTharos]

Can you post the mission? Or an example mission of this happening at least?

[Sleem]

Once does not work like that!

 

Somewhat counterintuitively it is repeatedly evaluated until it is true once, then deleted. In other words once random will always be true eventually!

 

You can use another flag to ensure it only gets evaluated once.

[snwboardn]

yea once does act like that... It doesn't just evaluate it once and then if it isn't true discard it... It keeps evaluating it until it becomes true and then discards it...

 

I think you will have to make a once for a random flag becoming true so if you want 33% have flags 10, 11, and 12 evaluate so only one of them becomes true, and then make that particular jet spawn when say 11 becomes true...

[nomdeplume]

I've made a CAP flight that I've given the Engage Targets Enroute Task within 25 nm, but they still seem to fly anywhere and shoot down everything. Do I need to turn off the CAP ET completely and only go with the Engate Targets ET?

 

I've done the same with SEAD, and afaik it only seems to attack within 25 nm of its route when both SEAD ET and Engage Target ET is on.

Yes, the default will basically engage anything it can detect. This is fine for a simple mission where every unit on the map is involved in the same mission, but doesn't work so well in more complex situations.

 

I nearly always delete the default tasks (the -a ones) in order to provide better control.

 

It may be that the SEAD flight isn't detecting any other targets so they're behaving themselves. If you have one of the really long-range SAMs in the mission they'll probably up that radar and go zooming off across the country to engage it.

[STP Dragon]

Use MISSIONSTART trigger to set a flag randomly to TRUE.

Now use this flag for the condition of your "unit activate" trigger.

 

 

Triggertype: MISSIONSTART

Condition: Random 33%

Action: Set Flag 99 ON

 

Triggertype: ONCE

Condition 1: Flag 99 is true

Condition 2: Time since Flag 3 - 180

Action: Activate group - Russ Fighters

[LostOblivion]

Ah, great, thanks.