New Update - Old Rebuild in the Developer Preview
Hi everyone!
First off, the previous developer preview client has been switched to main, which includes some small changes listed below.
- Developer Preview update group name changed from "beta" to "devprev".
- The alignment tool wasn't inserting cutpoints in some places where it should have - this should be fixed now.
The second bit of news is that we've released a new client to the Developer Preview which includes the Old Rebuild behavior. Many players have asked for rebuild to be reverted to this behavior, as they believe it was better, and so we're asking for your feedback on the pros/cons of the new versus old rebuild behavior. The clients (devprev and main) are identical other than devprev having the Old Rebuild behavior.
Try it out, and let us know what you think!
(Tue, 02/28/2012 - 02:41 | 10 comments)
http://fold.it/portal/node/987371#comment-10761
You can see that it was never quite clear what the difference was!
Loading this new 'devprev' version wiped out all of the user settings. Had to go through and get everything set up again.
Is there a way you prevent that on updates? It's really annoying.
The only real change I'm seeing (in the devprev version: i.e. old rebuild) is one for the worse. Whereas the number of rebuilds do_local_rebuild (and its V2 equivalent) created used to be at least vaguely similar to the number requested, now it goes berserk. do_local_rebuild (2) for example I counted doing 40-odd rebuilds.
We get to expect the unexpected.
Predictions are like that. Never fold unless you use the force of instinct. You are the only key to the puzzles. Unlock them !
don't get bogged down with the software. it's not as perfect as you will eventually will be.
Fold Hard!
It seems to give a better pose earlier when hand rebuilding.
What would be ideal is the ability to switch between them for hand builds and scripts.
that many poses how many it is told to do (in script).
do_local_rebuild(1) should make one new pose (or fail if impossible)
do_local_rebuild(2) 2 new poses etc.
Now on undo graph i see several new poses when use simple script:
deselect_all()
select_index_range(1,3)
for i=1,10 do
do_local_rebuild(1)
do_shake(1)
end
There is even 10 new poses between shakes, they are unaccesible form script and make rebuilder work much longer. It is now even "worse", in "new" rebuild it was up to 3 poses on graph.
Feedback: http://fold.it/portal/node/989670
Looks like this rebuild routine is finding "possible" poses much earlier than previous one. It is good, but it should be limited to number we need/want. This is great for hand building, but for scripts it is waste of processing power.
The feedback shows that it's not clear to some of the players what the difference is. Hopefully somebody knows; I believe this is what mottiger was asking. I'd like to know as well: there is a difference between the "new" and the "old" that devprev was reverted to, but what was the change (or, what was it intended to be)?
I agree, imo the old rebuild is far better for hand rebuilds, especially sheets, however the scripts get stuck in devprev as they don't seem to be able to rebuild one segment. As single segments appear quite often in the puzzles this is a problem. However in the new rebuild the manual rebuild seems maniacal but the scripts work.
When I want to run a rebuild script I will not do that in dev.
No good results.
I do not do much hand rebuilding so I can not comment on that.
can you explain what the old and what the new rebuild does/should do/have done?