Dread Lords appear and game crashes out to desktop

I have GAII, DA and TotA installed.  Except for some minor bugs (ship sprites dissapearing for example), the game runs flawlessly.  I'm playing a random map (not campaign).   However, whenever the Dread Lords show up (message appears), the game crashes out on the next turn ALWAYS!  What could be doing this?

Thanks for your help!

 

8,144 views 8 replies
Reply #1 Top
I had the same issue with CTD but it crashed directly after the Dread Lords announcement, not the turn after.
Reply #2 Top
I might be incorrect - it might have crashed once right after the announcement and then another time on the turn. Did you manage to figure out why?
Reply #3 Top
Please install 'SmartException' from the free stuff section in Stardock Central. Make sure that SE is running and start your game as normal. If the game crashes it will generate an exception report that can be emailed to gc2bugs@stardock.com.

Include in/attached to the email:
+ A description of what you were doing at the time.
+ How to reproduce the crash (if possible).
+ A zipped save (if applicable).
+ The appropriate debug.err file.

The devs cannot help if you do not provide these details!
Reply #4 Top
I appreciate this, but it is impossible for me to force the variable - which is the Dread Lords appearance - so this is not of much use to me.
Reply #5 Top
WWW Link

This page has a listing of cheat key combinations. Obviously by using the cheat mode the game will be flagged, but of particular interest is the ability to force a Mega Event with Ctrl + Y. I don't know if you get to choose which Mega Event you get but if you do get the Dread Lords event and the game crashes again, Smart Exception will be useful for holding onto the debug information.
Reply #6 Top
I managed to get the bug while running SE and an e-mail was sent.

Couldn't find the "The appropriate debug.err file" though
Reply #7 Top
Couldn't find the "The appropriate debug.err file" though
End of quote


That would be the debug.err from the session that crashed. It is *usually* included in the SE log so it's probably ok.