[karajorma]

Originally posted by TopAce
I strongly suggest you make an FSO version.

I strongly suggest you don't. There is no need to make special versions of a campaign just to deal with FSO bugs. If you're working with FSO to add new features to a campaign then all well and good but you should never port an FS2 campaign just to cure bugs.

Instead of wasting time making a nearly identical version try tracking down what causes the bug like I did on this thread with the key-reset SEXP. Then make a detailed report on mantis and instead of us having a crappy workaround for the problem we'll actually have the problem fixed in the code where it should actually have been fixed so that the next person to use the feature doesn't have bugs to deal with.

Besides as Grunt says it's pretty stupid to make a port to cure bugs as FSO is a moving target and the bugs will all be completely different 5-6 months from now.

[TopAce]

It takes a longer time for the coders to fix a bug than porting missions to FSO, just to fix the bugs.

I will try this anyway. I am curious how this will turn out.

[phreak]

well if its any clue, the is-cargo-known-delay sexp was used.

[Grunt]

Originally posted by PhReAk
well if its any clue, the is-cargo-known-delay sexp was used.

Yea. branched from a "not" operation which is sometimes the cause of problems in FSR as well, but not in this case.
Also mission1 crashing for TopAce is probably not an FSO issue but a conflict with other installed MODs (others didn't have this issue).
Maybe TCP should be packaged into a vp file ?

[TopAce]

The only SEXP that caused problems for me while using FSR was the is-iff.

[Grunt]

Nested logicals can be nasty.

[Goober5000]

Originally posted by PhReAk
well if its any clue, the is-cargo-known-delay sexp was used.

That may have been a bug I introduced.  What exactly went wrong?

[phreak]

its hard to say.  let me get some pictures together.

[phreak]

I cut out an unneeded sexp in the middle.  Hopefully you can figure this one out.

There's one more sexp above this that "fail1" is chained to.  I forgot about it.

Code: [Select]


- Farian Docked
    - when
    - has-docked-delay
        - Farian
        - Oppenheimer
        - 1
        - 0
    - do-nothing
(directive text: "Scan all transports")


[RED DIAMOND]

Very creative idea and mod.

[Grunt]

Originally posted by RED DIAMOND
Very creative idea and mod.

Thanks.
Have you played it actually ?

[RED DIAMOND]

Originally posted by Grunt


Thanks.
Have you played it actually ?

Yes, but I can't remember if I played it all and straight. I do recall that I fought some rebels right?

[TopAce]

If you have been with the Empire, sure.

[Grunt]

Originally posted by RED DIAMOND


Yes, but I can't remember if I played it all and straight. I do recall that I fought some rebels right?

Well .. yea .. something like that. Never mind.

[Nuclear1]

I just got to playing this campaign today, and I will say that I think I've missed something recently. That was a rather fun play.

Some little buggers though. What I mostly noticed stemmed from grammar issues and large-scale battles (not BoE; simply underbalanced, kill-everything-in-your-path missions) that really got irritating after a while. It seems that all of the problematic SEXPs and events have already been noticed and mentioned here.

If you would like, I'll gladly go over the missions and grammar/spellcheck it for errors. It always makes campaigns seem much more professional, and this campaign has a lot of potential behind it.

[Grunt]

Nuclear1, I would appreciate your help with the grammar/style a lot. I tried my best but some mistakes are still there that I only noticed after release.
I realize that some missions are really tough. A variation of difficulty from mission to mission was intentional, and some of them is impossible without intensive team play. You need to call reinforcement and need to use your wingies there. Also it gets harder and harder as the player fails critical objectives. He is kinda "punished" for mistakes, but can still finish the mission if he finds the way out of these situations.
I was the only tester until now, and it's difficult when you know the mission too well, so all comments are welcome.
I'll give hints or improve the mission on a second release.

Did you play it through with FSO ? It would be good to know if the major bugs were sorted with the patch.

Anyway it's great to hear some feedback at least. Thanks a lot !

[TopAce]

Good to know that not only I have problems with grammar in my campaigns.

[Mefustae]

Just played it, a really good little campaign you've made there. I like the design of the Trifid - albiet not exactly in the style of Terran or Vasudan ships - but it's a pretty cool ship. Apart from the occaisional grammatical error - and the fact that you killed the Aquitaine (this is the third campaign i've played this week that the Aquitaine has been destroyed, not a well liked ship) - an overall good play and no show-stopping bugs...

[Grunt]

Originally posted by Mefustae
...(this is the third campaign i've played this week that the Aquitaine has been destroyed, not a well liked ship) - an overall good play and no show-stopping bugs...

Heh, I thought most ppl liked the Aquitaine (I do)..
So it was just to generate feelings. Wanted to be dramatic all the way you now.
Errmm .. isn't it a spoiler btw ?

[Akalabeth Angel]

I'm only part-way through, but one question I had is how did you make the command briefings? I'd love to do some of that for my own campaign.