Last waypoint keeps switching to becoming the 2nd waypoint

[Ice84]

Yet another problem I cant find on the tutorials;
My squad's first objective (waypoint 0) is to destroy an empty stationary fuel truck. Once that is accomplished, the next waypoint (waypoint 1) is a simple MOVE waypoint, with waypoint 2 (being the last) to GET IN a boat that travels to the shoreline once a trigger realises that the truck is not "alive". This trigger is synchronised to a HOLD waypoint the boat is currently on before that causes it to switch to its next waypoint which is LOAD when it reaches the shoreline.

However, once my squad blows up the truck, for some reason, instead of showing the next MOVE waypoint, the very last waypoint which i have named as 'EVAC' appears where the very first waypoint was originally. This aint what I expected??

Anyone know why on earth its doing that? If any more info is needed i will try and provide it!
This has really got me stumped cos as far am I am aware I shouldnt have done anything wrong here but obviously it seems I have??? :-\

[Chudley]

Ok, try this

1. Remove ALL current triggers, waypoints and synchronisations from the map.

2. In the Init field of the boat, type...this setFuel0.0[/b]

3. Set a waypoint for the boat. It should be where you want the boat to go when loaded. This should be your ONLY waypoint for the boat.

3.Now place a trigger...

Axis A and Axis b = 0
Condition: "_x in boatname" count (units groupname) == "alive _x" count (units groupname)
On Activation: boatname setFuel 1.0



WAYPOINT 0 - *Make the group stay at this waypoint until the truck is destroyed*

Condition: not (alive truckname)
On Activation: <leave blank>


WAYPOINT 1 - *No conditions required*

Condition: <leave blank>
On Activation: <leave blank>


WAYPOINT 2 - *Assign group to boat*

Condition: <leave blank>
On Activation:  "_x assignAsCargo boatname" forEach units groupname



WAYPOINT 3 - *Order group board to boat*

Condition: <leave blank>
On Activation:  (units groupname) orderGetIn true

[Chris Death]

Jay, instead of a workaround for your problem i'd like to see how you did it, and how it can be
fixed. Ya must know i'm not that friend of moving around a problem just to run into it even harder
next time. 

If you could  probably recreate that without any addons (if used anyways) attach it here and
i'll give it a look.

~S~ CD

[Chudley]

Chris is right Jay....if you do what he says, he can point out your mistakes/bugs etc..

That way, you won't run into this problem again.  ;D

Try both suggestions, study them and how they work - and you've learned something. 

[Ice84]

Ok heres the .sqm for it. The map it belongs to is Everon. You can see some of the (really) basic scripting.

[Ice84]

The mission is still unfinished BTW and is designed with no add-ons (cant get my head around the long-drawn names of some of these addon units) cos I've seen how many varieties of missions there are that require all sorts of other people's addons.

[Chris Death]

I'm at work right now without access to ofp - i'm gonna give it a look tomorow. 

~S~ CD

[Ice84]

Cheers man, much appreciated!

[Chris Death]

Well, i've taken a look and found something 

I've made a radio alpha trigger to setdammage truck1.
Then i destroyed truck1 by radio alpha - and evac waypoint showed up.

Now i didn't leave the start position for that, and that was the problem.
The stock up waypoint was so close to me that once i blew up the truck1
by radio alpha, the stock up waypoint was also finished, because i was already
there. I guess you did something similar, because i then tried another variant:

I've placed me and my guys close to truck1 (setcaptive true all of us so that enemies accept us there).
Then i blew up truck1 and voilla - stock up waypoint was showing up. 

There was another thingy i noticed.

Your objective complete trigger doesn't work because of it's condition.

condition: this && !alive truck1
activation: vehicle/present grouped with truck1

Now truck1 is not inside the trigger's range thus this will never become true.
Even if you would place the trigger now so that truck1 is in it's range, this && !alive truck1 will
never become true at the same time. If truck1 is alive, then this is true.
If truck1 is not alive then this is false.
It would work if you do either:

move the trigger over truck1 so that it is in range and change the activation to:
vehicle/not present

or:

not group truck1 to the trigger - remove this && and make it just: !alive truck1
as condition.

Also you made a: hint "Objective complete, head for the extraction point" and then you tick off
obj1 - There comes the objective complete hint from your second command, but the first hint
will not show up because it gets overwritten imidiately from the second automatical one.
Change your "Objective complete, head for the extraction point" into a text message.

--------------------------------------------------------------------------------------------------------------------

The trigger which make the two chopper crews wait also doesn't work because
of the same problem, just a little bit different from objective complete trigger.

condition: this && !alive truck1
activation: none/present

This trigger will never activate - you can now again remove this &&, or even
better;

change the hold waypoints of the chopper crews into simple move wayopints and
into the waypoints condition field type: !alive truck1
Delete the trigger - it's useless.

----------------------------------------------------------------------------------------------------------------

How does a trigger become activated?

A trigger becomes activated due to it's condition.

true: the trigger activates imidiately

this: the trigger activates, once it's activation conditions above in the check boxes become true

any other condition: the trigger activates once the condition becomes true

What is the difference between a type: switch and type: none?

A switch trigger will force a unit/group to move straight to the waypoint after the one, the
trigger is syncronised to.
This can be used to switch straight forward or back to a wayoint not being the next one in order
of the chain, or to switch over an obsolete waypoint like: hold, guard, cycle, support

A none trigger will just enable the next wayoint after the one, it's syncronised to.

In your case you placed a destroy waypoint onto truck1, and it will be accomplished after destroying
truck1 - no need to syncronise the waypoint with any trigger.

hope this helps

:edit - btw - i forgot;

Next time you attach a mission.sqm, you should mention on which island it should be so it doesn't
require some play around before. 

And one more thing:

Don't use waypoints for player to show him what he has to do - most ppl are playing in veteran
mode and waypoints will not show up for them then.

~S~ CD

[Ice84]

Thanks dude, you the man. This has really helped!!! For once it actually plays through smoothly!
I'll try and get time to get it completely finished and if the missions depot gets up and running again I may try and post it

Thanks again!!