Research complete screen not closing....

from Stardock Forums
Yesterday I ran into an odd bug on the reseach complete screen. When I pressed the done button to close the screen and choose what to research next, the research droid and tech outline animations simply restarted and the description text for the tech dissapeared. Trying to close the window by either pressing the Done button or the ESC key just caused the animations to restart again.

Since the game didn't actually crash, I have no crash log, and the only unusual message in the debug.err log is 'Debug Message: AI-X: Found no places to send my colony ship.' repeated variously throughout the log, which would seem to not be related.

The only details I can recall from memory are that I picked up three research anomalies the same turn that I would have finished research on the current tech normally (I had forgotten that the survey ships were being sent to research anomalies). Two of the three were 25% research anomolies, the third was 'A waste of time.'

This is with the updated .EXE that was linked to Saturday(?).
55 views 1 replies
Reply #1 from Stardock Forums Top
I have seen this on build Beta 3z1 as well. I remember someone at SD making a comment about the research completion screen now having a button that changed from "done" to "next" if it was trying to present more than one tech completion in the same turn. I have a tendency to get complacent about what I am used to seeing and tend to miss such changes, so when it happened to me the first time I assumed the game had hung up somehow. Since then I have had the same thing happened that was described by Arturus: It just looked like the game got very confused about what it was supposed to do, including going to the next turn, even though I have autoturn off. I even had the tech completion music playing without the tech completion screen.

In short, I think multiple research completions in one turn is not being handled correctly (code error). I have found this problem to be terminal, although I have been able to restart an earlier saved game and get past this error successfully.