Many players have complained in global that 670 is extremely laggy, but it doesn't look like anyone has feedbacked it yet. The puzzle is unplayable for me - wiggle updates score and protein position on screen only every 2 seconds; one iteration of wiggle takes several minutes to run. It's nearly impossible to tell when wiggle is slowing down. The client I have on 670 is using ~600 MB of RAM, which I gather from other posts is about normal. My other two clients (on 669) are running at normal speed. I have closed and re-opened the 670 client multiple times with same result.
Win 7 64, latest release of devprev.
i'm om main. it does lag for me, but not so bad, but it is crashy for me.
very slow but normal amount of memory that is less than 400 for me in win7 with max graph length at 25
670 froze my client today (Mac os 10.7.5).
I had only done hand work, no mutate. Started a script (no mutate in script), then changed my mind and cancelled. It froze on the cancel.
When I opened that puzzle yesterday for the first time, I did see the erratic wiggle behavior - it sits for a few seconds, then jerks - then sits again - then jerks. There was no smoothness, just fits & starts.
Yesterday I did see that the memory increased on my machine, but I don't have the tools or the tech to say how much (my istat bar graph was much higher, almost doubled, when 670 was open). I also noted that the foldit program file size was 349mb on old program - 416mb on current program that had had 670 opened - and on reboot, current program size 408mb.
I've also heard of many more client crashes than usual since the update, not all related to 670.
Completely normal for me, as a mutable puzzle it is slow, more so then non-mutable puzzles, but not laggy in the least and no crashes whatsoever in the last 16 hours on two clients on updated clients. Win 7 SP-1 x64.
However I cannot say what it might do with other recipes besides what I am and have been running.
I played it for two hours.In the beginning was it ok but after running timos DRW with mutate options it was veeeeryyyy laaaaggyyyy. Like Susume discribed it, so I closed it, it's no fun.
Win 7, latest update of main.
Alright folks, I am running presently 8 clients of 669 and 6 clients of 670 on ONE computer. 669 s behaving EXTREMELY WELL. 670 however is somewhat less then would be normally appreciated. HOWEVER I do NOT hold that against the CLIENT, I simply hold it against trying to RUN to many mutable puzzles against MY resources.
NUFF SAID
What 670 is proving is that all those who think their computers are normal, are NOT normal!!!!
There is definitely something wrong with 670 and probably related to the latest update. Its very slow and crashes when running rebuilding scripts frequently. Mutate does not seem to brother it; I have mutated manually and with scripts for long periods of time without crashing though it is very slow.
Perhaps you should have stopped at "enough said"…
While you may have the luxury of configuring a computer to maximize running foldit, most players can't do that - many people need to use their computer for work purposes, or it is shared by a family.
You also assume that mac users can use your method. Or linux users. No one gets to say what's "normal".
After reflection, if you would like the comment deleted, please ask.
