-
Hey there, I've been playing through the Homesick mod and really enjoying it.
I just finished the mission towards the end of the mod where you battle in the subspace node that leads home and the Shivan destroyer rams the Custodian, destroying it, and collapsing the node. I think my ship may have been destroyed by the explosion from the Custodian (it happened a split second before the mission ended, but the campaign moved on anyway).
In the next mission (which is a red alert mission), my ship is frozen. I can't move, can't fire, or do anything. There is no shield indicator next to my radar map. I tried replaying the previous mission, but had the same problem there. I restarted FS2 Open, but now it crashes anytime I even try to select my Homesick mod pilot.
Does anyone know of any way to fix this? I really want to finish the campaign. I'd even settle for just extracting the individual mission files from the .vp and playing the last few that way. Anyone have any ideas? Thanks!
-
Hmmmmmmmmmm
This sounds like that ST:R bug, but I never heard of that one corrupting pilot files. Unfortunately there's no way for you to continue using that pilot, so playing the missions by themselves using ctrl+shift+s and the tech room may be your best bet.
-
(0.5: If your pilot doesn't work anymore, create a new one.)
1. Start the game.
2. Go to the tech room.
3. Go to the mission simulator.
4. Press Ctrl + Shift + S.
-
Okay, that sounds great! How do I get the Homesick campaign missions though? I loaded it with the game launcher, but the only campaign that shows up in the mission simulator is the Freespace 2 main campaign.
-
Err, the same way you did before. That is, if you had to create a new pilot, remember to first go to the campaign room and select the Homesick campaign.
-
Just select "Homesick" in the campaign room.
-
Oh, sorry, that was just me being an idiot. Of course I select it from the campaign room :)
Well, whatever the bug was it looks like it corrupted the whole Homesick mod. I guess I'll just re-download it. Thanks for all your help!
Whoa, didn't expect the campaign to end that way... :eek2:
Thanks again for helping me figure this out!
-
Hey there, I've been playing through the Homesick mod and really enjoying it. I just finished the mission towards the end of the mod where you battle in the subspace node that leads home and the Shivan destroyer rams the Custodian, destroying it, and collapsing the node.
That's funny, when I played that campaign I seem to recall that the Demon beamed the Custodian taking out its engines. They know that they can't complete the jump so they order you and your wingman to make for the node and jump out. I don't recall any ramming.
-
The Demon beams the engines and then rams the Custodian. I don't know whether or not it's possible to complete the mission before the ramming, but it might be.
-
You know, this is one of the very few classic campaigns I never finished, and thanks to the fact that you didn't bother putting that huge important event in spoiler tags now I probably never will. :(
Spoiler tags please, they are our friends.
edit: I guess it's been many years so it's pretty much my fault, I am just a sad panda
-
Hey there, I've been playing through the Homesick mod and really enjoying it. I just finished the mission towards the end of the mod where you battle in the subspace node that leads home and the Shivan destroyer rams the Custodian, destroying it, and collapsing the node.
That's funny, when I played that campaign I seem to recall that the Demon beamed the Custodian taking out its engines. They know that they can't complete the jump so they order you and your wingman to make for the node and jump out. I don't recall any ramming.
Actually, the Custodian doesn't tell you to get out, you and your wingmen just bail. Also I don't think the ramming is actually checked by an event or something in the mission, you were just supposed to jump out before it occured.
Story-wise, I did think it was a bit odd that the Shivans decided to disable the Custodian and then ram into it, but at least it avoids the discrepancy that would occur if there was an invasion during the reconstruction period.
-
Aw, wow, sorry for being a stupid noob and not using spoiler tags. I'll certainly make sure to do so in the future. My sincere apologies for spoiling the story.
-
Aw, wow, sorry for being a stupid noob and not using spoiler tags. I'll certainly make sure to do so in the future. My sincere apologies for spoiling the story.
Don't worry about it. In retrospect I was probably being a little hypocritical, this might actually motivate me to break it out and finish it!
Keep playing quality campaigns.
-
I'd like to go back and spoiler out my previous comments. How do I add a spoiler box?
Never mind, I found it.