Is being handled

The bug is back in 20180711-7bdda27475-win_x86-devprev. The image below demonstrates the faulty math.

This looks like it's doing the correct penalty, albeit with a strange interface.

+-651.8 = -800 + -1.7546 + 150

Are you saying that it isn't actually subtracting that from the score?

I've blacklisted the current devprev client scoring temporarily until we verify this one way or another.

I've verified this is working by disabling the filter and adding a bunch of residues. Upon re-enabling the filter, your score goes down.

I've re-enabled scoring for devprev. Let me know if you still think there is a problem.

Hmm... while the penalty is working properly while the filter is enabled, it appears to not invalidate your score while disabled. I'll be re-blacklisting this client until we can come up with a fix.

I am getting a message that my client is out of date and my scores will not be recordsed - Devprev

I switched to 'main' and I am getting the same message.
And it is game-dynamic not foldit

Sorry, the screen shot didn't really convey the situation that well. The buggy part was the high score shown on the right. While it's too high, it's not off by the 800 point segment count penalty.

I was a little confused by the whole thing.

Shared with scientists 1546@11975.

Goes to 12627 with any recipe which checks for bonus by disabling and enabling filters or conditions or objectives or whatever.

While I expect some improvement, I doubt I'll be able to catch that score.

I experienced similar. Got message about scores not counting, update client when opening in devprev, switched to main, got the same. Got a slightly inflated score. When shared, the score needs a huge amount to evo... example, puzzle came in scoring 13039 but when loaded into the 32 bit client score came in as 12224. So evo would require 817 points. ... and I am posting a fresh track of the solution mentioned above (loaded in an old 32 bit client) to see if the score/evo issue persists there. (not sure how it could but team report suggests it might).

And as to Mike Cassidy's comment up thread, mac client has been "game dynamic" at least since 2016. This is apparently not a bug. Jeff Flatten said at some point in time that game_dynamic is a cosmetic issue only (devs feel free to correct if I have this wrong)

ALso on 1547 my puzzle went off the screen and Q is not bringing it back. I was wiggling when it drove off the right side.

I think it is a mix of going off the screen AND disappearing into the screen
SO 'Q' (and now J) maybe bringing it to center back it is so tiny it can not be seen