[TrashMan]

It should undock first... I re-did the Legion 3 times and changed the docking paths..same things with the argo going trough it happens every time..go figure.

[BustRobot]

Hi there.

I appear to be experiencing the Fury bug in mission 11R. i.e. It just sits there and gets blown up. And besides not moving, it doesn't even have any turrets with which to defend itself. All of the subsystems are at 0% as well, besides the fighter/hanger bays.
And also, when I complete the mission - which I have to do by cheating just for the Fury to survive - nothing happens.

I downloaded the file from Hades Combine yesterday. (24th January.) I've also tried re-downloading it from the page on here and from Hades Combine again today.

*Crys to the heavens*It's the Diablo bug from Inferno all over again!! Noooooooooooooo!!!

I've tried uploading the mission file in FRED, but it keeps telling me that it's unable to load the file. (I do extract the mission files from the VP file.) I can only guess that I'm doing something wrong here. (Even if I did upload the file, I wouldn't have the foggiest idea of what to do, besides removing the "Red Alert" flag.)

Any help would be majorly appreciated!


P.S. Another amusing little bug I expericed, in the mission where you need to capture the Legion, the argo docks with the Legion and then undocks... but it in fact doesn't undock, (I think it tries to but fails), it jumps out and takes the Legion with it!    Apparently Ole has seen it too.
It didn't have any effect on completing the mission whatsoever.

P.S. P.S. I'm loving the campaign so far. I find that many campaigns I play don't engross me into it, but this one does. I especially like how you link it in to the main FS2 campaign really neatly. Can't wait to get back to playing it.

[TrashMan]

11R..work with me here - that's the one right after you try to join the assault on Sirius that goes terribly bust and now you must run (red-alert).

IIRC, the Fury and your wing are the only ships with the red-alert flag, so all damage and stats from the previous mission should carry over. The Fury follow a waypoint and then jump, it's really a short mission, and I can't understand what is wrong.

I'll take a look in FRED.

B.t.w. - you need to tell FRED to use the ships and tables from the VP before he can open the mission. There's a flag for it, I just can't recall how it goes atm.

A way around it is to extract all the files from the VP's into your Freespace/Data folder, then it should automaticly use them. It shouldn't overwrite anything stock.

[BustRobot]

That's right Trashman, that's the mission.

While the damage to the hull of the Fury is carried over, (i.e. if the hull went down to 88%, it'll be 88% in the red alert flagged mission), all of the turrets disappear, (including any undamaged ones), and all the subsystems are at 0%.

Good luck with it Trashman.

Also, thanks for the FRED thing. I'll give it a try, and if it works I'll see if removing the red alert flag does anything.

EDIT: I tried the FRED thing, and the missions still say that they are unable to load.  Ah well.

EDIT2: For the time being I've decided to skip the mission by failing it 5 times and using the "Advance to Next Mission" option. If you ever need me to test mission 11R to see if it works properly for me, just let me know.

EDIT3: Have also experienced the bug with the Fury not jumping at the Deneb Jump Node. (Mission 13, I think.) Again, have used the trick of failing the mission 5 times and using "Advance to Next Mission."

[TrashMan]

mission 13?
That's the one where you have to kill or scare off the Hecate?

Well, the Fury doesn't jump there..it's waiting for you to land in bays 1 or 2..
There should be a directive there.
Strange how suddenly errors are appearing when it worked O.K. before.

[BustRobot]

Oh, I see. Well, I must never have gotten the directive to land on the Fury in that mission.    I certainly never got told in a bit of dialogue to land of the Fury.

Well,  I've managed to finish the campaign, and I have to say that despite the little annoying (or amusing) bugs, I really enjoyed it.  As I've already said, I love the fact that you tie it in seamlessly with the original campaign, with lots of missions having plenty of familiar links to said original campaign. 

Fantastic work indeed, and I hope and look forward to a Chapter 2, whatever it may contain. 

[lobisomem]

mission 13?
That's the one where you have to kill or scare off the Hecate?

Well, the Fury doesn't jump there..it's waiting for you to land in bays 1 or 2..
There should be a directive there.
Strange how suddenly errors are appearing when it worked O.K. before.

Hi again trashman!
I have experienced that problem too....
in this mission if you don´t destroy the hecate, the mission simply never end

I have just finished the chapter 1.
It was absolutely amazing, and i want to play the chapter 2, as you are developing the chapter 3...
I really enjoyed a lot. How can i download the chapter 2?
Thanks for the campaing and for the help during my playing.

[TrashMan]

There is no chapter 2...long story and a big naming mixup...

FOW - Coming of the Storm (a.k.a. - chapter 3a) has a lot of missions done, but my FREDer (with 4 mission on his HDD that he never sent to me) dissapeared


This part needs about 6 more missions (not counting the missing 4), everything else is practicely done. It will come in time..ATM I'm not doing any FREDing.

[Darksider]

Hi, I'm new to the HLP forums, and was wondering if this glitch has been mentioned before.

In the mission where I have to destroy the Zhidov, and other NTF ships and escort the fury to the node, once the fury reaches the node, nothing happens. Command tells me to land in one of the fighter bays, but for some reason The mission doesn't end.

[blowfish]

Hi, I'm new to the HLP forums, and was wondering if this glitch has been mentioned before.

In the mission where I have to destroy the Zhidov, and other NTF ships and escort the fury to the node, once the fury reaches the node, nothing happens. Command tells me to land in one of the fighter bays, but for some reason The mission doesn't end.

Yes, it seems that if you don't destroy the Hecate, then the SEXPs don't trigger properly.  I've looked at the mission file and it looks like this is the case.  The SEXPs at the end of the mission need to be redone (a few of them anyway).

[TrashMan]

If I recall correctly, the landing SEXP is triggered by the Fury ending it's waypoints, not the Hecates destruction.

Note that you are cleared to land in Bay01 and 02...NOT 03 and 04 (if you try and land in one of those, the comms officer will call you a retard).

Sometimes it does happen that the ship doesn't "hit" the last waypoint precisely, but I thought that thing was fixed ages ago.

[blowfish]

No, the SEXPs are set up incorrectly.  The "finish mission" event (the one that ends the mission when you land) is chained to the "Mission complete" event (Fury waypoints are done), but "Mission complete" is chained to "Mission success" which only triggers when the Hecate is destroyed.

[TrashMan]

 

But...how....can't....

How the hell did my Beta testers miss that?
How the hell could I have linked the events like that in the first place?..

urg...I'll have to fix that.

[Snail]

Maybe you uploaded an older version by mistake.

[TrashMan]

I just fixed the issue....Any more bugs or problems I should know about (that are fixable) before I upload the fix?

[TrashMan]

Here are the fixed mission files. They should fix the issues with missions 2, 4 and 13 .

CLICKY

Just put this in the FOW1/Data/Missions

EDIT - FOW works normally with the newer version of the Orion and Typhon. To use them just put them in the FOW1/Data/models folder and change the pof name in the ships.tbl

[Akalabeth Angel]

 

     Yeah, I had a hell of a time with that mission where you have to protect the Fury after the failed assault.
     I downloaded the missions above, but it seems broken still unless I did something wrong ( FoW/data/missions ) folder??? Or does the VP overwrite the data folder? I dunno.

     

Spoiler:

The Fury didn't fly any waypoints. Instead it just sat there, then a Levy jumps in right behind it, has to fly up just to avoid running into the rear end. So there I am, trying to shoot down two wings of bombers and bombs meanwhile getting shot to pieces by Lokis and 4 AAAf beams. Then another Fenris jumps in and adds more AAAf to the fight. I tried hiding under the hull, firing trebs at the bombers and prom-s at the bombs but the Fury still got waxed . .. so when it offered to let me skip it, I did First time I've done that in a while. What I don't get is why a Fighter Carrier with 4 launch bays only launches 4 fighters for a total of 8??? (oh, and 1 support ship). But anyway, I'm on the next mission . . . another bloody leviathan

[TrashMan]

As far as I know (from personal experience), stuff on the ModFolder/Data folder always overrides anything in the VP.

Some of those errors I just don't get... the Fury clearly has initial orders to follow the waypoints once and I have no clue why it doesn't do it. It's random errors like these that set my blood pressure cooking. 

As for the fightercount...gameplay. I probably should have made it so that the Fury launches more fighters

[Akalabeth Angel]

As far as I know (from personal experience), stuff on the ModFolder/Data folder always overrides anything in the VP.

Some of those errors I just don't get... the Fury clearly has initial orders to follow the waypoints once and I have no clue why it doesn't do it. It's random errors like these that set my blood pressure cooking. 

       I had the same problem with my campaign. Had some convoy mission where the freighters wouldnt move, so the rearguard cruiser just rammed into them willy-nilly on one player's computer. I don't know what the problem was . . . couldn't really help the guy in the end.

       I mean if I do a mission, and I screwed up, then that's cool. I can fix it. But if it doesn't work for no real reason, yeah I know where you're coming from it is frustrating for sure.

[Akalabeth Angel]

     Hey man, thanks for the campaign. It was pretty fun.
     It's also pretty cool to have it run parallel with the normal FS2 campaign. Sorta interesting.
     Some spoiler-esque comments:

Spoiler:

One bug I noticed. In the mission where the Delacroix bites it, I lost it to bomber attacks and was able to advance. But the debriefing makes it pretty clear that I should've lost it to the Ravana instead.

I don't know what happened to everyone. Like Iceman, Razor, and Vixen. In the other "survive" nebula-gankfest mission, it seemed everyone bought it. Then next mission they were all there again. Then after that I didn't notice what the heck happened to them, they just sorta disappeared. I think Razor may have been at the science-guard sathanas thing but didnt know if he was around for the next one. It seemed a bit like the character stuff was emphasized for the first bit, and afterwards it sorta wasn't.

Some of the missions I thought could've used a little more backstory. One mission I'm fighting the NTF, next I'm deep in the nebula. Would've be cool to have some more . . . command briefings just to help set the context of the mission. (ie, the Fury has been redeployed to the nebula) Some things didn't really make sense either, the one cargo guard mission (ETAK?) really early on: The captain says "we're all grounded". Next mission, flying no problem. Unless I misread it and it was just her who had her flight status revoked.

And one thing I thought was, the campaign sorta didnt give me enough information about what was happening sometimes. It sort of assumed I knew the parallel story in the FS2 campaign a little too much. And of course most people who play it, will have also played FS2. But whether they remember it or not is a different matter entirely. Personally, sometimes I didn't really know what was going on in the grand scheme of things and it seems like I was supposed to.

For the end cutscene. I think you should've had the story bits, and then the credits. Having them both run at the same time meant that a person didn't really read the credits and that's a bit of a shame imo.

I would've liked it if uh . . . the briefings would tell me what ship I'm flying. Sometimes I'm in Gamma, sometimes in Delta, etcetera. I'd get confused as to where the hell I was. I'd loadout a plane and discover I was flying something totally different not even on the select screen. And sometimes I'd want my wing to cover me but I wouldn't even know what wing they were. Maybe it said on the map, I dunno. I usually just read the text.

I think the tone of the some of the briefings could've been better. Like some of the later missions, the wing leader's saying I did a fantastic job and everything but really . . the whole fleet should be ****ting their pants and thinking only of their imminent DOOM imo. A little more sense of urgency might've been cool. I was also surprised that the death of the Colossus wasn't mentioned at all. That would've been a deathblow to morale I'd a thought (for someone like Vixen anyway). There were quite a few grammatical mistakes, especially from one mission onwards (can't remember which). But it didn't bother me TOO much to be honest. One thing I've thought of, if I ever do more missions is to type up everything in Word first and then fix the mistakes there. Then just cut and paste later on. Might work well, might not.

      But don't take any of that too harshly. Just giving some constructive criticism/feedback and trying to uh, make your next campaign even better It was a lot of fun.  Good stuff