[Retsof]

I just got Homesick, and I'm on the fourth mission, the one where you're escorting a convoy.  It's a Red Alert mission, and for some reason Beta wing is all dead.  I tried telling all fighters to form up before I left,  but then when I go to play the mission the game crashes.  What's going wrong?

[Hellstryker]

strange, i played homesick fine. bug free campaign. the only thing i can think of is maybe your FSO files are out of date, or maybe the mission is corrupt?

[Jeff Vader]

For the nth time, it's the evil red alert bug of doom^TM. Try getting fs2_open_3_6_7 from somewhere and play with it.

[G0atmaster]

or use VPView to extract the offending missions, then FRED the red alerts out of them.

[Retsof]

Well for one thing I already have 3.6.9, also, I extracted said mission, but how do I put it back in the vp?

[Jeff Vader]

1. I said 3.6.7 and I meant 3.6.7, not 3.6.9 since 3.6.9 has the habit of ruining Homesick.

2. You don't need to put them back in the vp. Just put them in \homesick\data\missions (create the folder if necessary).

[Tinman]

http://cp.nukelol.com/pi/FS2rc7dot9x.rar

use this FSO 3.6.7RC9 if you need it 

[Objekt]

Is there another fix?  I'm having the same problem, and I don't know how to "FRED the red alerts out."  3.6.7 doesn't help either; when I try to use it, the game crashes before I even get to select a pilot, or gets to the "Commit" screen and then crashes.

In the former case, I got a whole string of error dialogs when I tried to use 3.6.7.  Typical contents:

"Error: mv_missiles-wep.tbm(15):
Error: Required token = [$Model file:], found [+nocreate]
in weapon: Harpoon.

File:parse/parselo.cpp
Line: 551
[This filename points to the location of a file on the computer that built this executable]

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

It mattered not whether I turned all Features on or off.  I figured maybe this was being caused by trying to use the 3.6.8 mediavps, so I deleted that from the "secondarylist" in the mod.ini file for Homesick.

Now it launches, but FS2 plain ol' crashes when I try to fly the next mission (a red alert).  Again, this is what happens when running with the 3.6.7 executable.

Could it be caused by using a pilot with which I've played the previous missions under the 3.6.9 version?

[Jeff Vader]

Could it be caused by using a pilot with which I've played the previous missions under the 3.6.9 version?

Maybe. There's always a risk when switching mods with a single pilot. Switching builds can't be better in any way. I'll see if I find the time to download Homesick and pimp some non red alert missions for you.

[Retsof]

To FRED out the red alerts, just open the mission in FRED, go to editors>mission specs and uncheck the "red alert mission" box.

[Objekt]

That only worked for the 9th mission.  When I try to open what must be the 10th one (Hmsk-B1.fs2), FRED crashes.  I get the following error message:

Error: Can't open palette file <gamepalette-subspace>
File:C:\projects\freespace2\code\Palman\PalMan.cpp
Line: 317

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

So, I can't even open the mission to edit out the Red Alert.

I only started having problems with Red Alerts at the 9th mission.  It didn't crash at #4, though Beta wing was missing, as the original poster mentioned.

[Jeff Vader]

Try this, just for kicks.

[Objekt]

Thanks!  That seems to have fixed everything.

I'm still wondering why I couldn't open that one mission for editing.  Does one need to have certain files in certain places?  I thought the .fs2 file contained everything needed.

[Jeff Vader]

I wouldn't know. I just used the supreme master of all editing tools: Notepad.

[Cobra]

The only mission that I've had to edit is the second or third mission.

[Jeff Vader]

So far I've encountered the dreaded red alert bug in the ninth or so mission. Maybe I should try this fix of mine myself, since Objekt stated that it works.

[Photoncody]

Oh no, I've seen this problem before (I had the problem myself)

Ok, this is what you need to do:

Since the missions were created with the RETAIL Version of FRED, you should mark out the Red Alert in Retail FRED only. Then, put the Homesick .vp in Freespace2's main directory [C:\GAMES\Freespace2\] (Yours might be different) and run Retail FS2. DON'T run fs_open_3_6_(7/9)! Create a new pilot and select the campaign.

This SHOULD solve the problem and let you go on with the campaign.

[Cobra]

Uh, putting the Homesick .vp in the root folder does absolutely nothing besides give access to it without having to use the mod function.

[Jeff Vader]

Oh no, I've seen this problem before (I had the problem myself)

Ok, this is what you need to do:

Since the missions were created with the RETAIL Version of FRED, you should mark out the Red Alert in Retail FRED only. Then, put the Homesick .vp in Freespace2's main directory [C:\GAMES\Freespace2\] (Yours might be different) and run Retail FS2. DON'T run fs_open_3_6_(7/9)! Create a new pilot and select the campaign.

This SHOULD solve the problem and let you go on with the campaign.

Nice, but I think I've managed to do a compilation of bugfixes concerning Homesick on 3.6.9. Besides, doing bugfixing on any FRED is for girls. Real men use Notepad. And why start pushing everything into the root directory, since FSO has such a handy mod control system?