[Fergus]

Okay, after first test I faced a few problems.
1) It didn't take long for all of the wing men to be wiped out, almost died with having 6 enemy fighters on me while trying to take out comms.
2) Firing off all my Stillettos at the second Comm subsystem had no effect, I was aligned but they didn't seem to do any damage.  I was however able to start to damage it after the Sopedu opens up on the other subsystem.
3) After I was told to jump out, I did, but I got the AWOL message, saying "wait till you are told to do so"

[Primus]

1) I'll try to do something about that...
2) I've noticed that too and don't understand it. Karajorma?
3) That's because I changed the endings and so on.......

Thanks for testing

[TopAce]

I will test it and see what might cause the problem with the stiletto.

[AFTER TEST]

The stilettoes worked all right, I had no problem with them.
Some things need changing:

• I get the Prom R by default by the Prom S is also available. Set the Prom S as default, anyone who discovers this will change to the Prom S.
• The Communication subsystem was destroyed but I still failed the mission because the Iceni sent the message
• Messages still overlap here and there

[Primus]

I am one lucky mother****er...


Error: Argument count is illegal.

In sexpression: ( is-disarmed-delay )
(Error appears to be: is-disarmed-delay)
File:C:\projects\freespace2\code\Mission\MissionParse.cpp
Line: 3552

Call stack:
------------------------------------------------------------------
------------------------------------------------------------------


I guess the problem is is-disarmed-delay. I made some changes to the mission, and this is my reward

[TopAce]

Can we get the SEXP tree itself?

[Primus]

I checked the disarmed events in FRED2 but I can't find the problem.. I have no idea...

[TopAce]

The version I have has no problem with that event. If you give me the mission, I will be happy to look into it for you.

[Primus]

The Buggy Mission

-Fix0red-

[karajorma]

Works for me. I'm using FS2_Open though. I'll give it a try on my second PC in a bit as I haven't installed FS2_Open on that one yet.

EDIT : FS2 retail fell over exactly like you described. I'll take a look at them mission and see if I can figure out the flaw. FRED2_Open didn't find anything wrong with the mission though.

[TopAce]

No problem for me, too.
I am thinking into the FS_Retail problem.
I tried the Retail FRED and that does not see this problem.
Do you use the old [V] Iceni? I will tell you later why I ask it, I suspect it could be the source of the problem.

SUGGESTION:
Change the faulty SEXP into 'true'.
Save the mission and see if there will be (an) other error(s). If it finds an error, then the mission code is somehow 'screwed up'. (<- Is there a more civil word instead of this?)
If the error goes away, recreate the SEXP without typing in anything manually if possible.
It is not a problem your SEXP tree will be exactly the same, if the code got screwed up, it will fix it.

If this does not work, then at least you tried.

[karajorma]

You're out of SEXP Nodes.

That's why the mission works in FS2_Open but not in FS2.

Rather interestingly you're only just over the limit so the error is not being detected by FRED and only kicks in when the game attempts to load the SEXPs used in the mission objectives. When I deleted those 3 empty events you had used as spacers in the events list the error changed to one of the SEXPs you had only used in the mission objectives.

I'm going to take a good look through the mission and see if you have been wasting SEXPs anywhere.

[Primus]

I already scrapped few events.. Including the empty ones (except those three) ..Hopefully you'll find some wasted SEXPs

[karajorma]

Myself and Topace took a good look.

We found a few at first but the big waste is in the AI section. Setting up Alpha and Beta wings with orders to disable the Damocles (~50-60% priority) and also disable the comms systems (~30%) would claw you back a huge number of SEXP nodes.

Don't worry about the fact that the Damocles isn't present at the start of the mission. The ships will patiently wait until it arrives as long as you don't give them anything else to do

It's also worth noting that the DIR - disarm damo a and DIR - destroy comms a are completely unnecessary. You can remove them and the chaining they use and the b events will work correctly because FS2 won't show the directives until the Damocles is present (Don't be too upset about not knowing that neither myself nor TopAce were 100% sure it would work until we tested it )

[Primus]

Okay.. I'll scrap'em too..

[TopAce]

Why the hell did the system send this message twice?

[TopAce]

Originally posted by karajorma
....
It's also worth noting that the DIR - disarm damo a and DIR - destroy comms a are completely unnecessary. You can remove them and the chaining they use and the b events will work correctly because FS2 won't show the directives until the Damocles is present (Don't be too upset about not knowing that neither myself nor TopAce were 100% sure it would work until we tested it )

I would have a pang of conscience if you experience something inconvenient.

[Primus]

I understood that the first time

[karajorma]

Originally posted by TopAce
I would have a pang of conscience if you experience something inconvenient.

I'd be surprised if he did. I checked that the event wasn't used elsewhere before deleting it

[Primus]

Little update:

I've scrapped some events and added a few which is like +-0

There still the same problem.. The damn fighters keep bounding Damo even when the objectives are accomplished.. The Damo must be Protected in order to prevent this, right? I gotta check that it actually is..

Also I'm editing the messages, so they won't pop up when they shouldn't...

And something else too.. Expect results.. When it's done

[karajorma]

Yep. The enemy fighters will continue to smack the Damocles around even after taking out the subsystems specified unless you protect it.