Folding Forum

@Folder_0815: It's good that you've been able to see you had version 0.0.5 @ 2020-05-29 and 0.0.2 @ 2020-06-03, which narrows down the window to a week. Is it possible to determine at what point exactly the version was downgraded? You should see lines in the log saying the core was downloaded similar to what you've seen this week. You can post the logs online if you don't have the time to go through them. It'd be interesting to know what caused this

Newbie again question....

I've had both Core 21 and Core 22 jobs that used the .2 core version in the last few weeks. But they followed with .5 version so I never thought anything of it, and assumed both just got used as needed. Is this not normal activity?

It is quite normal. v0.0.5 of Core 22 was released on 24th April, 2020. If you've been folding on the GPU before this time, chances are you'd have had v0.0.2 of Core 22 in your FAH setup. If the projects you received after v0.0.5 was released continued to have 0.0.2 as the minimum required version, your setup would have happily continued folding with 0.0.2. At some point, you'd have received a WU for a project that asked for 0.0.5 core as the minimum version and your client would have then downloaded the latest version of the core, which happened to be 0.0.5.

In OP's case, the weird behaviour is that they had 0.0.5 in May but then for some reason got 0.0.2 downloaded. As far as I know, projects specify the core version as the minimum requirement (>=0.0.2), not as a required version (=0.0.2). So if it indeed was a project that caused a WU downgrade, that is very strange.

I'll collect all required data and i'll post everything here tonight or tomorrow night, takes some time....

anandhanju wrote:It is quite normal. v0.0.5 of Core 22 was released on 24th April, 2020. If you've been folding on the GPU before this time, chances are you'd have had v0.0.2 of Core 22 in your FAH setup. If the projects you received after v0.0.5 was released continued to have 0.0.2 as the minimum required version, your setup would have happily continued folding with 0.0.2. At some point, you'd have received a WU for a project that asked for 0.0.5 core as the minimum version and your client would have then downloaded the latest version of the core, which happened to be 0.0.5.

In OP's case, the weird behaviour is that they had 0.0.5 in May but then for some reason got 0.0.2 downloaded. As far as I know, projects specify the core version as the minimum requirement (>=0.0.2), not as a required version (=0.0.2). So if it indeed was a project that caused a WU downgrade, that is very strange.

Thanks for the explanation.

I hope the OP figures out what nuked the newer version from his setup. Strange indeed.

I hope the OP figures out what nuked the newer version from his setup. Strange indeed.

I am working on it.
Currently there is a possibility that I made a rollback of a driver and through that Version 0.0.5 was deleted.
I'll keep you updated.