The priority is being set correctly on my rig, I got both the GPU2 clients on Realtime and the CPU client on low.

Regarding the starting the starting this program first bit, if you have the clients running and then start this program, it will use 100% of one core and hang there until you shut it down with the Task Manager. This is what happened on my machine, but the very simple way to combat that is to start the [email protected] Manager first, let it sit in the tray for a couple of second, then open it, set it up as you like it, and only then fire up the [email protected] clients.

Works great, thanks for adding the dual GPU2 clients feature!

I guess I have no excuse for not being as awesome as King... - iKillSteal

Seriously, big credit goes out to King for maintaining this list. He puts a lot of work into this thing and he deserves our thanks! - Verran

I founnd a bug if you want, you can't run all clients real time. I tried running the CPU and both GPU clients on real time, that gave me about 83% CPU usage maximum, but as soon as I set the CPU client down to High, it went back to 100%. Also, all clients on Realtime might cause the computer to freeze. After it only used 83%, my rig crashed twice in a row.

I guess I have no excuse for not being as awesome as King... - iKillSteal

Seriously, big credit goes out to King for maintaining this list. He puts a lot of work into this thing and he deserves our thanks! - Verran

Well it's common sense really not to set all clients to realtime. Nothing really should be set to realtime. Do u suggest to put a limitation on the priority? Say disable realtime? or only allow one to be set to realtime?