Bletchley Park Lv 1
Similar issue to the other bug report. Different puzzle though.
Solution uploaded to scientists as "flapping sidechains"
BUG
Similar issue to the other bug report. Different puzzle though.
Solution uploaded to scientists as "flapping sidechains"
BUG
Hmm, the backbone of this solution is extremely deformed. Something definitely went wrong somewhere.
Can you say anything about how you made this solution? Did you use any different recipes than usual?
I did not make this solution, it is the original starting position that did not wiggle.
@"Bletchley Park" Can you share some more information about your system? What operating system and version are you running? Is there anything non-standard about your hardware? Are you using a typical x86 CPU? Or are you somehow running Foldit on an ARM processor?
Somehow, it seems that your client is loading the starting solution with funny coordinates. Specifically, it looks like the (x,y,z) coordinates of all the protein atoms have been rounded to integers (they should be floating point). If you change your View Options to use Stick mode, you might recognize that all of the bonds have funny angles and distances (also, the "Show backbone issues" option should flag virtually every residue). This same thing also seems to cause of the bug you reported with the most recent devprev puzzle.
This is really strange, and unfortunately we haven't been able to reproduce this on any of our development machines. What's more, we are not seeing this kind of thing in solutions from any other users. Do you have multiple Foldit installations, and do you see this behavior on all of them? If you download a fresh install of Foldit, does the behavior persist?
Bkoep,
As I mentioned in my other comment, after resetting the puzzle the scores seem ok and I can use the puzzle. So seemingly in the initial loading something gets corrupted. I have deleted the files in the default directory and reloaded the puzzle, this time it loads fine.
Maybe there is a new routine that in the initial download, unpacking and setup uses a variable that is declared as integer instead of float or double ? Maybe a library function that is evaluated in a different order or evaluated without braces ( ) ? A backward division (a\b) instead of a forward (a/b) may also be a tricky bug.
This compatibility issue with MSVC might be interesting as well:
https://devblogs.microsoft.com/cppblog/microsoft-visual-studio-2022-and-floating-point-to-integer-conversions/
Hey @"Bletchley Park", do you know which library you installed to get 64-bit working? I am wondering if the version you installed is a slightly different 'flavor' that may be causing issues.
Hi @jflat06 , I installed Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.32.31332
Not sure if it's related, but here's a crash with stuff like this:
core.kinematics.AtomTree: {0} [ ERROR ] Atom3 position -nan(ind)-nan(ind)-nan(ind)
That's after running a ligand tweaking recipe overnight.
No sign of problems on restart.