Devs, any luck with the invasion hangings?

The invasion hang bug is happening a lot this version. Devs, any progress finding the problem yet?

 

2,367 views 7 replies
Reply #1 Top

I sent a data package last night and within 15 minutes got an email thanking me and saying they were working very hard on it.   But no word on progress.

 

Reply #2 Top

Derek posted about it in the the thread:

https://forums.galciv3.com/464463/page/1/#3544544

he said it was going to make it to patch #2 because it was difficult to fix.  I don't know if we should keep sending saved games though.  And I don't know when is patch 2, I'm guessing early next week, or end of this week, depending on how it goes, so we can play, I mean, test the game ;)

Reply #3 Top

The difficulty is that, from my experience, the saves with the problem are not often repeatable. I get the hang, exit the game, reload and the invasion works fine. So sending a save doesn't help. : /

Reply #4 Top

Quoting TheBirthdayParty, reply 3

The difficulty is that, from my experience, the saves with the problem are not often repeatable. I get the hang, exit the game, reload and the invasion works fine. So sending a save doesn't help. : /
End of TheBirthdayParty's quote

well, sometimes, it may not hang a planet, but will on another.  Devs could play the game a few turns and only care about invading AI planets until it freezes, not about empire management.

Reply #5 Top

I think a saved game is helpful if combined with a TM forced dump before one kills the GC3 process when it happens.   I find that  yes sometimes it works and sometimes not, but if I try a few times it will fail again.    So I think there is a fair chance it might be reproducible at SD.    The crash dump has to be useful in any case, and I think that a save file helps with the interpretation of the dump file.

But it may be wishful thinking, but I agree with redviper37.   Maybe they can get lucky, and if I send a save file that I know has failed at least once, then they have a fighting chance.

It's a bad boy though for sure.

 

Reply #6 Top

In my experience it always happened the 2nd planet I invaded after i encountered the bug and reloaded.

 

So if i have 10 planets on my list to invade, and it crashed on invading the 4th planet f.e., i will load the autosave from a turn before.

Now the 4th planet invasion will go fine, but the 5th one creates a crash. Hence and repeat.

 

If the crash happens during an autosave transition however, I noticed that the game itself does not actually crash, but it merely is a graphics error. Pressing esc f.e. will 'exit' and complete the invasion, and trigger an autosave, however you are just facing a BlackSOD which you can kill with task manager.

Reply #7 Top

I posted this on Twitter about this bug.

@Stardock #galacticciv3 the main bug being the black screen as the Nvidia driver crashed out in planetary invasions about 50% of the time.

And got this reply from Brad Wardell

"@Giskarduk @Stardock we're all over that one."