My system has two GPU's. I have a GTX 680 that runs Boinc 24/7. I also have a GTX 780 Ti that my monitor is hooked up to. The GTX 780 Ti runs Boinc projects when I am not at the PC.

When I am at the PC I want to remove the 780 Ti from being available for Boinc projects and be dedicated to games or playing videos. If I have the 680 on one project and the 780 Ti on another this isn't an issue since I can just suspend the project the 780 Ti is working on. But when I have both GPU's on the same project that will not work. Well, it does but it also shuts down the 680, which I don't want to do. The way I have been handling this has been to go into the config files and editing a exclusion line for just the 780 Ti.

Is there a simpler way to do what I have described without having to edit the config files every time?

No, not at this time.

---

My system has two GPU's. I have a GTX 680 that runs Boinc 24/7. I also have a GTX 780 Ti that my monitor is hooked up to. The GTX 780 Ti runs Boinc projects when I am not at the PC.

When I am at the PC I want to remove the 780 Ti from being available for Boinc projects and be dedicated to games or playing videos. If I have the 680 on one project and the 780 Ti on another this isn't an issue since I can just suspend the project the 780 Ti is working on. But when I have both GPU's on the same project that will not work. Well, it does but it also shuts down the 680, which I don't want to do. The way I have been handling this has been to go into the config files and editing a exclusion line for just the 780 Ti.

Is there a simpler way to do what I have described without having to edit the config files every time?

You could automate the process a little for yourself.
Configure cc_config1.xml with <ignore_nvidia_dev>#</ignore_nvidia_dev>
Configure cc_config2.xml without <ignore_nvidia_dev>.
Then run a script before playing a game like

copy BOINCdata\cc_config1.xml BOINCdata\cc_config.xml /Y
boinccmd --read_cc_config

He'd need to do a

boinccmd --quit
boinc

with some extra command line switches on that final restart. BOINC can't enable/disable GPUs on the fly, it has to be a stop/start.

He'd need to do a

boinccmd --quit
boinc

with some extra command line switches on that final restart. BOINC can't enable/disable GPUs on the fly, it has to be a stop/start.

I had forgotten about that.
The <exclude_gpu> option could be used with --read_cc_config to stop the GPU from being used without restarting BOINC. However BOINC would have to be restarted after the standard config was put in place to get the GPU to be used again.