Idealizing with "Auto" gives much lower result (on 856 round 3, full of unideal zones) than in High.
I would put "Auto" before "Low" in order not to confuse the player.
Idealize in high is much faster in current Foldit than in devprev. But ok it gives exactly the same points.
No crash for the moment, even using a recipe (ebola) with all types of actions on another puzzle, "Auto" wiggle power.
for the above, it's idealize+wiggle (in a recipe like micro idealize)
What you see is completely logical with the explanation of auto wiggle.
Auto wiggle is low wiggle plus repairing really bad ideality. High is doing all it can on ideality.
The logical sequence is in my opinion: low, auto, medium, high.
I've the impression that IdealizeSS does not behave like Idealize with cuts.
On a big helix 856, if I cut the ends, with Idealize, it moves not so much and I can easily close cuts (after some wiggle if necessary).
With IdealizeSS, he protein explodes. Not sure it'll get any points with recipes. So, only for very beginning of hand folding?
IdealizeSS is great for design and handfolding, especially in the beginning. I havent tried it with cuts, I dont think that would work great.
It's OK
If this is for general feedback about the latest devprev then I would like to add that I don't like it wiggle is wrong again.
The ISS is great for making helixes but can we go back to the build currently in main and just add the Indonesian translation, cut and paste, the ISS tool, ideality display and tooltips fix. Something has gone wonky with the other changes.
There is time to try again before CASP, it would help if there was a reasonably small <100segs 'normal' puzzle to test on either scoring or non scoring.
Which issues with wiggle are you still seeing?
closed