Puzzle 1432 "Error in sequence"

Started by Bletchley Park

Bletchley Park Lv 1

I get an "error in sequence" error if I try to share a saved solution for puzzle 1432.
client: 20170918-b1f60d5e03-win_x86-devprev

Cannot share solution with scientists for the above reason as well.

Bletchley Park Lv 1

I have shared a few nice examples of garbled solutions for you in 'scientist'.
look for 'blah' and 'BP19552.??? solo6'. the scoring is corrupted I think, as well as the representation of the ligand.

JellyJump Lv 1

I cannot even upload a file to the science team - This happens in my log:

loading solution: puzzle_2004215_time_1506301354.ir_solution
ERROR IN SEQUENCE : 199
Error in sequence. (......\source\src\standalone\application\boinc\Puzzle.cc:3102)
ERROR IN SEQUENCE : 199
Error in sequence. (......\source\src\standalone\application\boinc\Puzzle.cc:3102)
ERROR IN SEQUENCE : 199
Error in sequence. (......\source\src\standalone\application\boinc\Puzzle.cc:3102)
ERROR IN SEQUENCE : 199
Error in sequence. (......\source\src\standalone\application\boinc\Puzzle.cc:3102)

wuhongzei Lv 1

I have the same issue.
After I get 19k score and then quit and restart foldit, it shows the original puzzle(score: 15.7k) and my score on the board becomes 17k again. And it keeps repeating, if I try to save the solution and load it, "error in sequence" pops out.

alcor29 Lv 1

This error comes up when trying to reload a save. For someone who closes the client often this means that I have to start doing the puzzle over again from the beginning. So for me, the puzzle is unplayable and the only use I have for it is as a playground to discover what the different tools are.

georg137 Lv 1

The "error in sequence" bug in 1432 is major. When it hits, all work over many hours is un-retrievable. Frequent saves do not help. They all fail to load when the bug manifests on the (Window 10) client. I lost a strong solution, started over, saving all the while, and then lost the next one too…

jflat06 Staff Lv 1

I believe the latest update should have fixed this. If you still experience this issue again in the next puzzle, please let us know!