Unfortunately it was so long ago that I cannot find it again. But I know that it was a serine-serine-bridge between 2 adjacent strains of a 3-Helix bundle. Tried to re-model it but could not crash Foldit in today's version. Maybe this was fixed in the meantime? But back then I generally broke all bonds between adjacent helices so that they would have more freedom in subsequent global wiggling. I got immediate crashes frequently back then with manual rotamer-switching with left/right key.
Ok. I will try to work on crashing Foldit deliberately :) If that would help then it is worth trying and investigating this further.
I have one instance now where it crashes immediately.
The most crashing-on-me recipe is "Deep Remix Wiggle" (drmxw). I was able to isolate the commands that cause it to crash. You will have to run this:
function ReMix(ss,se,nrresults)
selection.DeselectAll()
selection.SelectRange(ss,se)
local nfound=structure.RemixSelected(30,nrresults)
–local nfound = 30
print("Nr of remix found "..nfound)
print("Loading remixes…")
for i=0,nfound-1 do
save.Quickload(30+i)
print("Loaded: " .. 30+i)
–structure.ShakeSidechainsSelected(1)
end
end
function main()
local Remixes = 30
print("Finding " .. Remixes .. " remixes…")
ReMix(56,58,Remixes)
end
main()
from within a recipe (I simply named it test but it probably does not matter) on the "crashtest" I shared with scientists for puzzle 1977.
If you run this recipe TWICE, then it will crash Foldit instantly at this second execution. Why there should be any difference at the SECOND execution is a mystery to me. It is even possible to reload "crashtest" before the second execution and it will still crash.
If you rather want to have a crash at the first execution, then you can uncomment the line "–structure.ShakeSidechainsSelected(1)" and for me it typically crashes at qs 51 or so. But that seems to vary. This is the full basic command-sequencing which is used in drmxw.
Even stranger is that it is not sufficient to just load the 30 remixes in the second execution (so disabling the line "local nfound=structure.RemixSelected(30,nrresults)" and enabling the line "–local nfound = 30". It seems to have something to do with twice executing the RemixSelected(). It also seems to get worse with higher number of remixes to find but 30 leads to reliable crashing for me. This is probably a generic problem and this crash-recipe can probably be used on designs of other puzzles as well since drmxw crashes on all puzzles for me.
I am pretty certain that this is not the only scenario which causes crashes because other recipes to not use remix but still crash. But it may be a hint to finding the root-cause.
Hope it helps to track this down.
