Select a Civ = CTD

Das Boat

Chieftain
Joined
Feb 24, 2010
Messages
39
Location
United States
I started playing this mod last night with a friend of mine and everything was going fine. Unfortunately, we got a de-sync and I had to rehost. When I got to the 'select a civ' screen, I immediately get a CTD. I try hosting again and I still get that CTD at the same screen. So I try to make a game in single player, and the same thing happens: when I get to the 'select a civ' screen it crashes. The only difference is that in MP it crashes immediately when I get to that screen, while in SP it crashes when I select something other than random.

I've redownloaded the mod and nothing changed. What could be the issue here? It couldn't be graphical as I can play Civ4 on high settings with no lag or other problems and everything in the mod worked fine up until that single point.
 
OK, do you have logging on? (it is explained how to do that in the FAQs thread)

If not, turn it on and try this again. After it crashes post the logs listed there, the random logs, and the minidump. Then AIAndy can look at it and see what, if anything can be done.
 
I do now!

I hope that is everything you need. I just added in the minidump and the ThemeParsLogs (?) and zipped that all to go.
 

Attachments

I do now!

I hope that is everything you need. I just added in the minidump and the ThemeParsLogs (?) and zipped that all to go.

No, you need the Synchronization logs and the random number logs. Look at the stickied FAQs thread for how to get those.

Edit: You need those logs from both computers involved.
 
To be completely honest, I don't think it has anything to do with desyncing -- that happens to us a couple times a session. Even when we were playing vanilla. I think it has something to do with the UI with civ selection. I can start/join a game in MP just fine because I am bypassing the civ selection screen. I just cannot load/rejoin that game because it keeps crashing at that same exact screen.
 
I'm the friend in this situation. Yeah, desyncing is not the problem. That happens every night in vanilla civ. In fact, it happened less with C2C.

I can confirm that there are no problems on my end. Everything is fine for me. I can get to the Civ screen just fine and I have no problems besides the sprites changing to default units every now and then.

As 'Das Boat' explained, the problem occurs when he views the civilization selection screen. Starting a Multiplayer game bypasses this screen, however loading a game or starting a single player game doesn't work because of that particular screen. We are using the latest version that was released at the end of January via Gamefront, and we have the latest version of Beyond The Sword via Steam.
 
You'll need to provide us with the savegame. And even then it may be a longshot. Have you updated to 3.19 by the way?

The minidump he's already posted should be the single best piece of evidence. It IS in the DLL. I just don't have the right PDB to say more than that - need to know exactly what SVN rev is being run...

Edit - I tried with rev 4667 (which I **think**) is the right DLL/PDB for V28 release, and that doesn't match the dump.
 
Here is the save from my MP game. It still won't let me past the Civ selection screen. I thought I had made progress yesterday by reinstalling the mod (as I played SP and I was able to select a Civ) but now it suddenly doesn't work again.
 

Attachments

Thanks for the save. I'll try an interesting debugging effort across both computers here at home with this and see how it goes for us. But I can't promise I'll be able to get to that immediately. Will be one of the efforts I get to hopefully during the freeze. (after the 15th)
 
Ok, looked into this. I can open the select a civilization screen on your game just fine. There are passwords on your game and on your individual civilization selections so I couldn't go any further than that in evaluating but from what I'm reading here, the problem should arise before those come up anyhow. So, either its:
a) A unique problem on your system
or
b) has been resolved by another bug fix incidentally. Quite possible sometimes. You might want to update to the latest SVN version and see how it goes for you now. If it crashes again, in this case, a minidump could be helpful. BUT when posting a minidump, make sure to indicate the revision version your svn was on at the time it was dumped.
 
Back
Top Bottom