Previous versions of the client will not be able to load in centroid puzzles. So that's to be expected. When this actually goes out to main the server will prevent previous client from trying to load in the puzzle, but it doesn't do that for devprev puzzles since they're just there for testing.
Even when the client is not actively performing any operations it's still rendering, so some CPU usage is to be expected.
Is this something you have only seen with this centroid puzzle? Only on devprev puzzles?
Thanks for pointing this out. The reason it wasn't there was because the score terms used for centroid mode are different than normal so they were just being lumped into "Other". I've updated the code to add centroid terms to the appropriate categories. Just a note, you won't see all the same categories that you're used to with normal puzzles because not all of that data is being calculated so it's not there to show.
I have noticed it only on centroid puzzles. Will check again on others and post if I find anything on other puzzles related to wiggle.
Try this:
No bands.
Wiggle with cl = 0.00
NOTHING happens. This is in the latest client devprev 2013-04-18-54935M-win_x86-devprev.
In the initial pose the van der waals forces are basically 0 because the residues are already far enough away from each other. This is why moving the clashing importance down doesn't really make a difference when you wiggle straight off the bat.
Just a note: The tools and scoring of centroid puzzles is similar, but won't behave exactly the same as in normal puzzles. Some strategies will not work and some may need to be modified.