Home   Help Search Login Register  

Author Topic: INTRO: Triggers, Conditions, and Synchronizations...  (Read 760 times)

0 Members and 1 Guest are viewing this topic.

Offline Kundich

  • Members
  • *
  • "Habit is the daily battleground of character."
My problem relates to mission intros and the normal tools available to mission editing, i.e. triggers, variables, and synchronization

I am trying to create an intro, but am having a problem with getting units in the intro to behave according to my master plan.  As it turns out, I want UNIT A to hold position until UNIT B reaches a certain position.  I have tried using a HOLD WP synchronized with a SWITCH TRIGGER, a MOVE WP for UNIT A synchronized with the corresponding MOVE WP for UNIT B, VARIABLES set to TRUE that activate either TRIGGERS or other WPs, and standard TRIGGERS synchronized with MOVE WPs.  None seem to work in the intro environment.  Does anyone have any insight into this?  This has been a recurring problem for me, one which I have not seriously tried to address.  Please help.


Thanks,
ADM

Sophion

  • Guest
Re:INTRO: Triggers, Conditions, and Synchronizations...
« Reply #1 on: 19 Nov 2005, 01:39:39 »
have a trigger with the condition line like this:

Code: [Select]
B distance A < 5
and put the type as switch if your using a hold WP.


5 is just a number i threw out there. it is the distance in meters. then synchronize the trigger with the WP of UNIT A so it will leave. synch it to the WP were you want UNIT A to stay before UNIT B gets there.

Offline Kundich

  • Members
  • *
  • "Habit is the daily battleground of character."
Re:INTRO: Triggers, Conditions, and Synchronizations...
« Reply #2 on: 19 Nov 2005, 17:55:46 »
Nice suggestion.  When I first looked at it, I was thinking your advice was basically the same as what I'd been trying.  Actually, it's only a hair different.

So here's my next question: why will the use of variables to activate triggers synchronized with WPs not work?  Here's the gist of a basic example of what caused me to go gray.

WP1 (us_Truck01):
     Move Waypoint
     CONDITION: true
     ON ACTIVATION: code_trucksHere=TRUE

WP1 (us_hmmwv01):
     Move Waypoint
     CONDITION: true
     ON ACTIVATION:
WP2 (us_hmmwv01):
     Hold Waypoint
     CONDITION: true (in some iterations, code_trucksHere)
     ON ACTIVATION:
     SYNCHRONIZATION: (1)

TRIGGER (Switch):
     CONDITION: code_trucksHere)
     ACTIVATION:
     SYNCHRONIZATION: (1)


I use several iterations of this type of variable, code_trucksHere, but nothing seems to work.  Am I doing it wrong (although my method works in missions) or is there some limitation to the language of the intro?  Is the kind of thing that can only be done using SQS files?  Using keywords, I couldn't find any tutorials on this subject.  Please advise before I start going bald, too.


Thanks,
ADM

Offline macguba

  • Former Staff
  • ****
    • macguba's operation flashpoint page
Re:INTRO: Triggers, Conditions, and Synchronizations...
« Reply #3 on: 28 Nov 2005, 19:15:24 »
If it works in a Mission it should work in an Intro.    A simple synchro of group A and group B's MOVE waypoints is all you need.   (Don't use HOLD waypoints for this.)

Create a new test missionette and see if you can get it to work there in isolation.
Plenty of reviewed ArmA missions for you to play