Strange WCP issue; self-destructing destroyers

  • Thread starter Thread starter Unregistered
  • Start date Start date
U

Unregistered

Guest
Im on mission 207.0, AKA G'wriss 2a : Alien Starship Encounter. Strangest thing happens; the moment I get to the nav point with the destroyers, they explode automatically. Before my wingmen can even finish talking about how big they are and to be careful around them. Before they even START, actually. Its an automatic mission success, but as Im playing on the second highest difficulty I think I want to challenge myself a little bit this time, and as such want to earn this victory.

What could be causing this? Ive tried quite a few things. I was until this point just disabling sound acceleration to get the game running, but Ive tried using HCI's patch, which while nice and convenient (and I will probaly continue to use now), did not solve this issue.
 
So, no one knows of this issue? My system is a little old, but still ultimately winxp based. 1.2 GHz Celeron, 256 MB RAM, and some integrated video, but I dont see how this could be a hardware issue.
 
Yeah, it doesn't sound like a hardware issue at all. I recall a few isolated incidents like this, but I don't recall anything reproducable. If I had to make a guess, I'd say it might be related to the 'Carrier is Destroyed' mission you get at launch later in the game if the Midway takes launch bay damage. The solution here might be to zero out the system somehow. Try deleting your autosave.gsw file or playing another mission with Orcas and then reloading from the flight history terminal.
 
You're right, that behavior is odd. The only thing that reminds me of is the "dynomite" cheat in WCP, where you can destroy any target with ctrl+F12 (yes, I confess - I used that the first time around).

If it does it by itself, there's something seriously wrong with your installation. To be on the sfe side, backup the saved games, and reinstall without patches, check, then add patches. Maybe something you did while or after installing interefered with the game, be it patches, hardware changes, or something unrelated, like going to bed without brushing your teeth...


EDIT: Okay, by any means try Chris' approach first - he is closer to the technological side of the game.
 
It actually has to do with how much damage the Midway took in the previous mission. If Midway received no damage to a major system, Bridge or Engines, the destroyers blow up on their own. If Midway is slightly damaged(one engine destroyed), the mission becomes more difficult, the destroyers don't blow up when you arrive. If both engines are destroyed or 1 engine and the bridge, then the mission becomes really difficult. So let the bugs damage or destroy 1 engine or the bridge and they won't blow up.
 
If this sites' own game guides are any indication, they should not be blowing up on their own. The mission IS supposed to be easier if the midway took no damage, but not this much so.

Zorching autosave.gsw did nothing. I might try the reinstall trick later when I have more time. Thanks for the help, I figured this was an obscure one.
 
Back
Top