[1.3 opt in] Multiplayer Crashes and a workaround

A friend and I were trying to play a multiplayer game and it crashed on startup, regardless of who hosted.

I have a GalCiv3 Elite Founder's license and a secondary regular one that I got on sale.  I decided to try and troubleshoot the problem using two computers with the different accounts side by side.

The issue is evidently caused by one (or more) of the DLCs.  I registered my secondary account to get the free DLC and tried it.  The game was stable at startup with that one DLC enabled on both accounts.  I didn't play past a few moves, but it stayed connected until I abandoned the game.

I didn't try the other DLCs because I don't want to spend $10 just to troubleshoot this problem.

So those who are having crashing issues can try disabling one of the premium DLCs and then the other and we'll know which one is the problem child.

In the meantime, disable all but the free one and Bob's your uncle.

 

32,951 views 7 replies
Reply #1 Top

Can you download and run this:

http://sd.stardock.com/Support/supportToolTest/SDSupportTool.exe 

And submit a ticket here so we can check it out:

https://esupport.stardock.com/index.php?/Tickets/Submit 

Reply #2 Top

I'd be glad to when I get home.  

Do you think that'll help if I'm the only one online at the time?  My other license only has the free DLC and it's stable.  It evidently only crashes when two people with the full DLC attempt to go MP.

 

Reply #3 Top

Ticket #BWT-489-10658.

I hope it helps.

Reply #4 Top

Does this still happen with the updated opt-in that we released last Thursday (9/3)?

Reply #5 Top

Quoting pshaw, reply 4

Does this still happen with the updated opt-in that we released last Thursday (9/3)?

I don't know.  I'm reluctant to try another MP game until I hear about a fix.  Evidently, my ticket has just been sent to the devs for review.  Literally just a few minutes ago according to the email.  So a little over a week to start looking at it.  I don't suspect I'll hear anything substantial for quite some time.

 

Reply #6 Top

I actually just got your ticket for review and am looking at it now.    |-)

 

Its unlikely the fix will be in for the 1.3 release, but we'll definitely working on it.

Reply #7 Top

Thanks for looking into it.