[Blazar]

Hello. I am making a very simple mission. Read and done the extended walkthrough, read the help file 3 times over.




Destroy Cancer and Leo wing appears correctly with numbers of hostiles and how many are left.
Destroy Virgo and Libra also appears correctly.
Problem: no number of hostiles.
Search 2 days on the Fred thread, read everything again.

Iam new so am trying the basics. But even with the walkthroug, the sexp's are still somewhat hard to use.
FRED 2 Open 3.6.10

 
  

[General Battuta]

Try changing the delay from 5 to 0. I have no idea if it makes a difference at all, but it might.

[Blazar]

Corrected my post above. Cancer and Leo are fully appearing with numbers and all.
Virgo and Libra only appear, but with no numers.

Thnx for the quik advise. I'll give it a try.
 

[General Battuta]

Well give us a screenshot of the Virgo and Libra events then.

[Blazar]

So Cancer and Leo were already good so i didn't change their op's.



The Virgo delay was 0, changed it to > 5, see pic (click to enlarge) above.

No effect.
What now

[General Battuta]

Simple answer. You can't use 'is-event-true-delay' in a directive without a special touch. You need to add a 'true' operator. Right click on the is-event-true-delay, hit 'add operator', go to 'logical', and select 'true'.

[FelixJim]

Simple answer. You can't use 'is-event-true-delay' in a directive without a special touch. You need to add a 'true' operator. Right click on the is-event-true-delay, hit 'add operator', go to 'logical', and select 'true'.

Wait, what? Isn't the problem more do to with the fact that the condition for the event with the "Destroy Virgo" directive is not waiting for Virgo's destruction, but for PVF Ma'at 17 to leave or be destroyed? It ought to be Virgo with is-destroyed-delay, surely?

[General Battuta]

I assumed that was part of his intent. I don't know why it would be but it's what he has set up.

[Shade]

Wait, what? Isn't the problem more do to with the fact that the condition for the event with the "Destroy Virgo" directive is not waiting for Virgo's destruction, but for PVF Ma'at 17 to leave or be destroyed? It ought to be Virgo with is-destroyed-delay, surely?

Yeah. The on-screen count only works when the condition is the destruction of something.

[General Battuta]

Okay, yes, I was maybe not answering the question he was asking. 

[Blazar]

Alas, there's no change

Event editor



Ship Editor



Should i change the op of GVFr Bes 20, because at this op the directive text is given?

Could there be a conflict with a ship editor?

Great all the reply's. My intend was very simple.
When Leo is destroyed, 5 sec later the PVFR Ma'at 17 arrives to dock with a container.
Virgo arrives to guard the PVFR Ma'at 17.




That's it. I am just beginning so i am trying to make a simple straight mission.
It's much fun but also a challenge. Like it 

[Shade]

In this case, the easy solution to your directive woes is to spin the non-working directives out into events of their own, instead of piggybacking on existing events with non-compatible conditions. So have something like this event for each of the two that are currently lacking a count, and add the directive to that:

-op when
    -op is-destroyed-delay
        # 0
        # Wing from the directive
    -op do-nothing

No need to chain it or otherwise mess with the trigger conditions, as the directive will only display once the wing referenced in the i-destroyed-delay condition arrives anyway.

[Blazar]

I thought that maybe the two events of the MA'at and Virgo are both at the same time and one of
them isn't completed, that would be a problem for the next op.

So,
I have changed the time for the GVFr Bes 20 op to > 5



But
No Change


So read the help topic again:



It seems very straight forward so the next step is;

And thought that both the Ma'at and virgo be in the op:



Still No Change.

In this case, the easy solution to your directive woes is to spin the non-working directives out into events of their own, instead of piggybacking on existing events with non-compatible conditions. So have something like this event for each of the two that are currently lacking a count, and add the directive to that:

-op when
    -op is-destroyed-delay
        # 0
        # Wing from the directive
    -op do-nothing

No need to chain it or otherwise mess with the trigger conditions, as the directive will only display once the wing referenced in the i-destroyed-delay condition arrives anyway.

Hey, this was kinda what i was thinking about doing next. So i'll give it a try!

[FUBAR-BDHR]

Why do you even have is-event-true (previous event) in the chained events?  Either chain them or use separate events.  

[Blazar]

So tried a lot of adjustments and this is the result:



Succes!!

So i had to replace the op's with the -is-destroyded-delayed
and i HAD to Chain them because i would get directives  from the last events or two directives at once.

Man lots of fun, but strange that i can't just liberally use other directives: such as has-departed-delay etc.
Because its better letting it do what you want and not the other way around.

What i mean is that you'll have to use everytime the same op's, very simplistic events!!??!!

Thnx for al the help so far. 
But i am not finished yet so i'll be knocking on your door if i'am stuck again.
But i'am doing a lot of research before asking.
 

[Blazar]

Hi again. I stand corrected, referring to my above mentioned comment.
Because I CAN use more/complicated SEXP's ofcourse!!!!
As you can see at the pic below



The problem was mainly (i think); the virgo wing had to be destroyed and that op should be used in the GVFr Bes 20 event.
This for me is a major learing point! Just wanted to share this with you guys.
Thanks again, problem solved, question answered.
Up to the rest of the mission now LOL!!!
 

[FelixJim]

Unless I'm terribly mistaken, you are currently telling FreeSpace to congratulate the player on destroying PVFR Ma'at 17 the moment it arrives. That might be what you want I guess, although it seems unlikely...

[Scotty]

Yeah, you might want to switch that operator to is-destroyed-delay and it should work.

So it'll end up looking like:
Virgo arrival cue
    ---> when
        ---> is-destroyed-delay
            ---> 0
            ---> PVFR Ma'at 17
        ---> do-nothing

with directive text "Destroy PVFR Ma'at 17"

[TopAce]

And with the event name "Virgo arrival cue," it will probably mess with the mission.

I suggest you use arrival cues as events and directives separately unless you have a very good reason not to separate the two.

[Blazar]

You'r quite right. the fact is that there is a celebratory music when leo gets destroyed although that's not what i intended it to be.
so i'am still figuring that one out.
thnx for the respons