WIGGLE LOCK - summary
| Case number: | 845813-992677 |
| Topic: | Game: Tools |
| Opened by: | Rav3n_pl |
| Status: | Open |
| Type: | Bug |
| Opened on: | Tuesday, May 15, 2012 - 22:31 |
| Last modified: | Friday, May 25, 2012 - 09:31 |
I decided to make summary for tis one.
Looks like random puzzles are suffering from this nasty bug.
I hope dev team will search and destroy it very soon.
Small ones like 555 are unplayable because of it - banding scripts are NOT WORKING AT ALL.
Bug posted in feedbacks:
http://fold.it/portal/node/991000
http://fold.it/portal/node/991397
http://fold.it/portal/node/992629
http://fold.it/portal/node/992648
Setting them all as duplicate to this thread.
| Status: Open » Open |
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!
beta you are the Best :)
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).
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.
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.
On what puzzle and what residues?
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.
That sounded worse than Wiggle Lock, more like: Wiggle on Strike!
Glad reloading it fixed the issue!
A total wiggle strike I have experienced also. See: http://fold.it/portal/node/992533
@timo: that is a very interesting and similar issue !
@beta: reloading itself did not fix the issue. The model has a lot of light red areas which in my perception should start a wiggle somewhere but it does not. Loading it and wiggling does nothing. Only after I start tweeking the model manually (moving it apart) wiggle starts to work again. I have found the model and can send it via mail if needed.
I have seen this MANY times and it is very frustrating. Wiggle just won't do anything at all, and I'm not talking about some near optimal configuration, I'm talking about < 10k, < 8k, sometimes < 0 configuration. Wiggle does nothing, even if I change clash importance, sometimes to 0! I have to do a manual pull to get it to move again (which of course lowers the score a lot).
YT video:
http://youtu.be/UOgzjz7ovQk