Branching waypoints?

[james mckenzie-smith 1]

Is there a way to make branching waypoints? Let's say you have a normal linear waypoint system. Would it be possible at one waypoint to have TWO possible options, where one option is taken if a trigger is activated, while the other is taken if the trigger is not activated?

[Toasted Duckie 0]

You can execute the setWaypointPosition command once a condition is met.

[james mckenzie-smith 1]

Thanks for the response. That might just solve a number of mission design issues...

[gnarly_rider 0]

This may be helpful too, I was trying to give a target opfor a series of escape options (chopper, car2 or car3) at a waypoint, depending on status of the vehicles.

http://forums.bistudio.com/showthread.php?t=90417

Could be easily modified to accommodate waypoints rather than getinvehicle commands

[james mckenzie-smith 1]

Toasted Duckie, I tried that out. Here's what I did.

1. I made a vehicle with grp1 = groupthis in its init field.

2. I made it one waypoint.

3. I made a trigger, that was activated by the presense of a civilian. I placed the civilian in the trigger's radius, and made a text event so that I could verify that the trigger had been activated.

4. In the trigger's On Act. field, I placed the following: [grp1, 1] setWaypointPosition [getPos AAA, 0]

5. I placed an invisible H on the position where I wanted the WP to go and gave it the name AAA

On starting the missing, nothing happened that was supposed to happen. The vehicle steadfastly moved to the waypoint's original position and nowhere near the invisible H. I also tried naming my own character as AAA; nothing.

Will this be a case of needing to type in the XYZ coords and forgetting the whole getPos thing?

[Inkompetent 0]

If the unit only has one single waypoint I believe that one is indexed as waypoint 0, so it should look like:

[grp1, 0] setWaypointPosition [getPos AAA, 0]

[bhaz 0]

You can also create several waypoint paths, each ending with a HOLD or CYCLE waypoint, and use switch triggers to move between them.

ie:

Path 1: MOVE > MOVE > CYCLE > Path 2: MOVE > MOVE > CYCLE

If left untouched, the group will follow path one, with the cycle waypoint (correctly positioned) to send it back to the start. To move the unit / group onto Path 2, you would create a switch trigger and sync it to the final waypoint of path 1 (the CYCLE waypoint), (When a switch trigger is synced to a waypoint, and the trigger fires, the waypoint is considered complete and moves to the next one, if one exists.)

Using multiple paths and repeatable triggers, you can make something quite complicated without touching scripting in any form. The only disadvantage is the confusion thousands of waypoints could cause in a large scale mission, which is the point where scripting becomes useful.

Edited November 25, 2009 by bhaz

[james mckenzie-smith 1]

Inlompetent, I understood waypoint 0 to be the starting location of the unit. Regardless, I did as you suggested, and once again, no positive result.

Bhaz, I know of that particular use of waypoints, and while it is most useful, it is not quite what I am looking for.

Thanks both of you for your input, notwithstanding that I am still foiled by this issue.

[bartkusa 10]

I uh made a system for branching waypoints, by using Location objects and the synchronization tool to create a directed graph :P

I'll share it one day, after I polish it. It's script-heavy, and pretty useless if you're the kind of person who can accomplish 90% of what you want through the in-game editor.

[skooma 10]

Does the Arma scripting language have conditional statements (if-then-else)?

[CarlGustaffa 4]

Do you know any languages that don't? Anyway...

http://community.bistudio.com/wiki/Control_Structures