Unfortunately the client still has issues which cause it to crash unexpectedly, in particular on scripts that involve rebuilds. I had to restart at least 5 times this morning. I noticed these messages in the log:
Error: Unknown enum value for Puzzle::Type: .
Error: Unknown enum value for Puzzle::Type: .
core.optimization.LineMinimizer: Inaccurate G! step= 3.8147e-008 Deriv= -698.84 Finite Diff= 1.98572e+008
and a way before that:
SRVR_THRD error: Puzzle is closed (....\src\game\application\novice\boinc\Boinc.cc:349)
Is there anything I can do to make debugging easier for you ?
When filing bug reports I also get a message on the server saying that e-mail could not be sent, this may be a server issue.
Regards, BP.
What platform are you on? What scripts crash particularly often? What is your version (from menu -> general options)?
Windows XP 32 bit, service pack 2, scripts with rebuilds in them, like overnight after a while. Some of my own scripts use rebuilds. My version is… : 21fdf490a555793ca0d1d72157357b6d.
We (group members) have also noticed that wiggling seemingly produces no result after some rebuilds.
What view options do you have on? Which interface are you using?
No view options selected, color: score, view protein: cartoon thin, view sidechains: don't show.
no music or sound effects, advanced interface, old-style gui.
Same issue here, identical setup to Bletchley Park. I'm not at my Fold.it PC right now, so I can't give you any log snippets.
Scripts (lua-style) crash the client anywhere from almost immediately to a hour or so after starting them.
Old-style recipes don't seem to cause the problem.
Also, I still have the issue of the in-game IRC connection getting broken or corrupted somehow during long-running lua script execution. Symptom of this is an error on closing the game, and no incoming or outgoing messages are possible in chat.
observation:
I had an unhanled win32 exception and was still able to move the protein, operate the user interface (change clashing importance for example) scroll the scores and open the chat windows, I posted a chat and stopped the shake that caused the exception. The text 'stopping' appeared, but then did not return to 'command mode'. The 'clock' kept running until I stopped the shake.
observation:
While simply wiggling the client crashed to a halt, no screen updates, no control whatsoever. Complete termination.
observation: crashed in module game_library.dll offset:007d706 while wiggling.
Windows 7 Enterprise
Overnight Script
df72aaf937e5773555800cc52329f0206