Synchronizing Waypoints to Triggers

[Op4 BuhBye 0]

Is anyone else having issues Synchronizing Waypoints to Triggers? I have tried it 3 differand ways and none work. The AI just keeps on truckin instead of waiting for the trigger to be satisfied.

[Op4 BuhBye 0]

If noone is having this issue please tell me so I know its me and not a bug.

[fasad 1]

As in the other topic on the same issue, check that your trigger is activating and deactivating when you expect.

Try adding hint "trigger active!" to the trigger's on activation box, and hint "trigger deactive!" to the trigger's on deactivation box.

[Op4 BuhBye 0]

I did a search for "synchronize" and got nothing. Its not like Im clairvoyant with some of the topic titles people use.

In any case I already know the trigger is not active. The deactivation really has nothing to do with the issue since the Activation is the trigger.

Trigger set to Bulefor detected by civilians, the 2nd waypoint for a Civ is synched to the trigger and he runs right to the 3rd as sonn as the map loads. No detection!

By the way Fasad thanx for the suggestion but I already new that as you can also put a text message in the effects to do the same thing.

[fasad 1]

Quote[/b] ]In any case I already know the trigger is not active. The deactivation really has nothing to do with the issue since the Activation is the trigger.

The only possible thing that can go wrong in the system you describe is the unexpected premature activation of the synchronized trigger. A non-deactivating trigger remains active forever once activated, which may well be relevant.

[Op4 BuhBye 0]

Or there is a bug with the Synchronize in ArmA. Everywhere else I have used triggers they work fine. The only things I have done with triggers are "Synchronize" (didnt work) and set the "condition" to a "publicvariable" (didnt work).

I guess it could be a trigger bug specific to those commands.

Have you tried either of those Fasad?

[fasad 1]

So you used the synchronizeWaypoint command? I've never tried that myself.

What are your exact "condition" and "on act" codes?

[Op4 BuhBye 0]

Cond: this

OnAct: nothing

I just confirmed that the trigger is not going active and the AI moves to the next waypoint.

[fasad 1]

I've never seen that happen. If you are 100% sure the trigger has not activated, upload your mission somewhere and I'll take a look for you if you want.

[Scrub 0]

Just had an issue with this problem myself, was a 'load' operation, and the issue was simply that both the WP and trigger were not satisfied at the same moment. My team needed to be present at the WP (with or without the trigger) for the helo to stop and load us up. If we were not there, it just continued on.

[Op4 BuhBye 0]

The publicvariable issue was:

Made a "publicvariable" in the init.sqs set it to 0

Load = 0

publicvariable "load"

In the trigger:

Trigger is grouped to a unit (w1)

Set to: Vehicle present

Condition: this and load == 0

OnAct: gives a weapon loadout for "w1"(works)

OnDeAct: load = 1

There are 3 trigger all the same, when you enter one you get the loadout when you leave it should set the vari to 1 so the other 2 triggers shouldnt work, but they do and it adds the same loadout again ontop of the first so if you had 6 mags and 3 satchels now you have 12/6. Go to the 3rd trigger and you get 18/9.

[Op4 BuhBye 0]

You have a PM Fasad