WIGGLE LOCK - summary

Started by Rav3n_pl

beta_helix Staff Lv 1

I know we often say this: "we'll look into it"
but yesterday jflat, Seth Cooper and I sat down together for 1 hour trying to pinpoint this bug (specifically using 555 as an obvious example).

We know this is a nasty bug and hopefully we'll have it fixed by the end of this week!

tokens Lv 1

I have noticed in 555 that local wiggle is gaining a lot more points than in other puzzles. My hypothesis is that ordinary wiggle is not gaining the points it should because of the wiggle lock bug, but that local wiggle doesn't suffer from this bug. If you local wiggle say 3 segments at a time, local wiggle will especially gain points around segment 17. But also just local wiggling the whole protein at one point gained me about 50 points though my solution otherwise was quite optimized (going in score from about 9650 to about 9700).

brow42 Lv 1

I've noticed that small puzzles, particularly and especially the 2 and 3 segment design puzzles, move 10x faster with a local wiggle than with a regular wiggle. Regular wiggle: like watching grass grow.

Bletchley Park Lv 1

I have a case of total lock in the new devprev version 2012-05-17-48987M-win_x86-devprev, not sure if anyone else has noticed that. I can mail seth with a file if he can tell me how a name relates to a filename.

Bletchley Park Lv 1

558 all residues in a particular configuration. But after reloading it and hand-moving it wiggle works again. Wiggle does nothing when just loaded. I remember when saving it that it really was stuck.
You may ignore my post.

beta_helix Staff Lv 1

That sounded worse than Wiggle Lock, more like: Wiggle on Strike!

Glad reloading it fixed the issue!