[2.5 BUG *Game-breaking*] Cannot Invade. No Genocide Ships

After the Krynn started a war with me by invading some of my outer worlds, I attacked some of theirs. However, upon trying to invade, my transports got the error "Cannot Invade. No Genocide Ships." The Krynn are busy taking my worlds and I cannot take them back. I have played several games and not experienced this bug until now. The only difference is that I have researched Biological Warfare (I never have before). May or may not be related.

I am not in the beta opt-in, I have tried verifying all game files, I have restarted multiple times, and I have changed the design of the ship via upgrades. I am still unable to perform any planetary invasions.

17,235 views 10 replies
Reply #1 Top

This sounds like it could be some weird hold-over from Spore ship technology.  Are there such things in GC III?

 

Reply #2 Top

Have you some citizens who are generals.

Reply #4 Top

Dagnabit, was in the middle of uploading my save game to google to post here when forums went boom, and I guess several posts were lost in what I presume was a load-from-backup.

Here's a link to my savegame with this bug in, I think its the prequel 3rd mission, the first one with the Drath:

https://drive.google.com/open?id=0ByxJB3KvvsoJVU1xak9CWTNmamM

The "Cannot Invade. No Genocide Ships." error generates when attempting to invade Dratha (in the northeast part of the map) with my transport a little to the east of Dratha.

 

This is Crusade, 2.5 (no beta opt-in).

Reply #5 Top

Chibiabos,

Did you build that transport ship or was it awarded to you?  It currently has no population.  

Reply #6 Top

I built it.  The Campaign uses the older troop model where it loads population instead of garrisons (there's no leaders in the campaign), when I launched it, it asked me how many troops and drew from the population of the planets near the shipyard I launched from.

Reply #7 Top

I'm not getting that error message now (noticed there was a small update), but launching troop transports in the next campaign series starting with Arcea, its showing no troop force when attempting to invade, even though I did fill the transport to the brim when launching (again, these Crusade-prequel campaigns were before the garrison mechanic; the troops draw directly from the population of planets near where they launch instead of a global garrison source).  I'm guessing the introduction of the garrison mechanic might have broken these prequel campaigns.

Has anyone else played the campaign series since Crusade/2.5?

Reply #8 Top

Quoting Chibiabos, reply 7

I'm not getting that error message now (noticed there was a small update), but launching troop transports in the next campaign series starting with Arcea, its showing no troop force when attempting to invade, even though I did fill the transport to the brim when launching (again, these Crusade-prequel campaigns were before the garrison mechanic; the troops draw directly from the population of planets near where they launch instead of a global garrison source).  I'm guessing the introduction of the garrison mechanic might have broken these prequel campaigns.

Has anyone else played the campaign series since Crusade/2.5?

Are you launching from a planet or from a starbase?

Reply #9 Top

From a shipyard.

EDIT:  D'oh, wait, I am pretty sure I had kept it at the starbase to protect it until I knocked out all enemy ships, then re-launched from the starbase.

Reply #10 Top

Same or similar issue. Base game, latest non-beta version.

Four transports in a fleet. Population 9 in each. Moved them to a starbase to keep them out of the way and safe. About 20-30 turns and at least one save/load game cycle later, when they left the starbase (perhaps) they all had no population showing, which I discovered when I tried to use them to invade a planet.

Going to go test now if they can have any more population loaded back on them from a friendly planet.

Edit: I was able to load population back up again from a friendly planet on the transports which had lost it. It also persisted through a save/load cycle, so bug appears to be starbase related.