Problems starting game

[Minrhael]

This problem just started since the "games everywhere are down" thing. After I connect to Mosehansen and check my MP game, I go to play single player. I cannot start a single player game without rebooting my computer. I can click "Play an existing game" and select a game, but as soon as I click play it crashes to desktop. Also, if I click create a new game it crashes. The same for create a new god, and after the preferences button, clicking mod preferences also crashes.

After I reboot, everything runs fine again until I connect to play MP. Then I need another reboot. Is there a work around for this? All this rebooting is a little annoying.

[Gandalf Parker]

Are you sure that the patch took ok? I had the same thing happen. I figured out it was because a .trs file had not updated with the rest of the program. Im not thrilled with the installer which I have to work around every time I patch.

Do a detail view, in date order, of the dominions2 directory and make sure that these files have newer dates than your original install. I find that especially the res.trs and army8.trs cause me problems.

res.trs
misc2.trs
flag.trs
bLast.trs
army8.trs
dom2.exe

[Minrhael]

Yes, the patch seems to have taken properly; all the modified dates are later than the originals. Also, I've been using it for both mp & sp games even after the 2.11 patch, it's just today that it's stopped working.

[Johan K]

Start dom2 with the -dd switch. That will give you a file called log.txt. Look at the end of it and it might give you a hint of why it crashes. Otherwise send it to me and it might give me a hint.

[Minrhael]

Thanks, not needed now though. When the 2.11 patch came out for some reason I put --scoredump (just like that, nothing after) in the shortcut; no idea why, I think I meant to add after it. Anyway, the shortcut had been working with it so I figured I'd just leave it. When it stopped working, I deleted --scoredump from the parameters figuring by taking out all the parameters but clickvol there would definitely not be a problem there and everything is working fine again, so that must have been the problem No idea why it started acting up when it had been working fine, but oh well.