I can't find my last post about CPU being enabled on various projects in their project pages.
But the situation still seems to happen occasionally.
Like today, my laptop loaded a Collatz CPU WU, which I only want to run GPU WUs from them.
I went to my account page, and checked the settings, and yes, it was enabled.
I'm not sure if BAM is to blame for it, or why GPU projects always want to run CPU projects.
It's annoying, to always have to visit the site and deselect the CPU.

I've had it happen on Milkyway, Collatz, Einstein, and a few others...

Aside from GPUGrid all other projects are CPU projects with GPU applications added. Meaning there aren't really many pure GPU only projects, and when they exist they'll disable giving the CPU preference from their server's config.xml options. Otherwise CPU is always enabled, by default, because all capable computers have a CPU that can be used to do work on.

What you were pointed at in the past is to check if the option "If no work for selected applications is available, accept work from other applications?" is set to No. Make sure it's set for the correct venue or location. And yes, if you use an account manager, to check that this is set there as well.

---

Aside from GPUGrid all other projects are CPU projects with GPU applications added. Meaning there aren't really many pure GPU only projects, and when they exist they'll disable giving the CPU preference from their server's config.xml options. Otherwise CPU is always enabled, by default, because all capable computers have a CPU that can be used to do work on.

What you were pointed at in the past is to check if the option "If no work for selected applications is available, accept work from other applications?" is set to No. Make sure it's set for the correct venue or location. And yes, if you use an account manager, to check that this is set there as well.

Yes, only CPU only projects have this option enabled.
GPU projects either don't have the option, or it is disabled.

I think I may have isolated the problem, to the use of BAM manager.
Whenever a project is imported in BAM, it does not honor the project website's settings.
It'll download CPU WUs, even if the CPU settings on the website are disabled.

I really think this whole Boinc thing needs a serious revamp!
Almost like overclocking a Ryzen CPU. Things pulling left and right, and when a setting is set, it's not honored because of multiple other settings..

I've never been a fan of decentralized (global) settings for all clients; and still am advocating that the client should be able to import BAM settings, but overall it should be in charge of the settings on that computer; and there has to be some sort of local override setting for each project on the local client.

I think I may have isolated the problem, to the use of BAM manager.
Whenever a project is imported in BAM, it does not honor the project website's settings.
It'll download CPU WUs, even if the CPU settings on the website are disabled.

I really think this whole Boinc thing needs a serious revamp!
Almost like overclocking a Ryzen CPU. Things pulling left and right, and when a setting is set, it's not honored because of multiple other settings..

I've never been a fan of decentralized (global) settings for all clients; and still am advocating that the client should be able to import BAM settings, but overall it should be in charge of the settings on that computer; and there has to be some sort of local override setting for each project on the local client.

I had a brief flirtation with account managers (gridcoin) and decided that was enough. Too many problems where it wanted to do things differently and how to sort things out was while not difficult, was certainly not intuitive.