We are posting the first of a series of new Flu puzzles that we are
very excited about.
You can read about all the details (including video interviews with
Baker Lab members and a podcast with David Baker) in David's recent
blogpost:
http://fold.it/portal/node/989769
In that blog you can also hear about an amazing recent Foldit result!
Lastly, a minor new update has been posted (which will allow you to
try out Flu Design Puzzle 1) which includes some minor changes that
might help OSX users experiencing crashes.
I'm having problems with tool shortcuts in 424. After I move/tweak, the S key does nothing and W takes forever to begin a wiggle. If I run a recipe first, the shortcuts work again. If I select Shake from the Actions menu, it works, and then the W shortcut works.
Everything was working great 8 hours ago, so I'm thinking this latest update is responsible.
Thanks for correcting for the crashes, yall. I thought it was just me.
Can you open a feedback case about this, with more specific steps? I'm having trouble reproducing it.
katling,
You may have fallen into the problem I have experienced for the last couple months.
My machine has become good instrument for measuring this problem. Briefly, every ten minutes foldit pulls down 80-100 percent of my processor; independent of anything, seemingly. With every update this window becomes longer. During this, keystrokes become irrelevant, or, if repeated enough times (usually three), hang the computer.
The length of time is dependent on the puzzle itself. The current window time for me is 1-2 minutes for a mini puzzle, 3-5 for puzzle 425 (with an additional hang at the 5-minute mark).
In my experience, the best way to see if the processor is at a temporary nadir is to have some small set of bonds visible. I try to pick the smallest set, so they many aren't required to draw. When they stop moving the processor is pinned: avoid doing anything then. The cursor will not update either, another clue.
I would humbly suggest, given my own experiences, and my works to try to find some way to get foldit to run decently on my little computer, that you learn to work with the problem, and that is why I have offered these tidbits of advice.
Seth: Apologies for irreproducibility and my delayed response. The problem continues on 426, but it's intermittent. I see by the feedback list that you've got your hands full. I'll open a feedback case later this week if/when I can identify some specifics.
Reginahaz: Thanks for the tidbits!
