I stopped using that Flag altogether.
Are you using the Beta Version of the Client Software or the Current Version?
On my 1080 Running Beta I see mostly Core 21 and a random Core 18.
Their are no new Cores out that I know or any in Beta Status.

Now you Tell Us
Thanks for the Info DutchForce

Enosoma
How do you add flag to FAH?

http://folding.stanford.edu/home/guide/configuration-guide/
Start with Figure 1

Are you using the Web Client?

Does this help on maxwell as well? I have both maxwell and Pascal in my system.

My understanding is that the flag let's you get newer units still in late stage testing, thus giving a greater chance of newer work units. Generally I only use the pause-on-startup true advanced option.

bcavnaugh
I stopped using that Flag altogether.
Are you using the Beta Version of the Client Software or the Current Version?
On my 1080 Running Beta I see mostly Core 21 and a random Core 18.
Their are no new Cores out that I know or any in Beta Status.

I'm just using the current version. It was all a bit of a rush, so I'm only now just thinking about flags 😩

How's the beta client, Bcav? Any wierdness going on? Better than the current of hard to tell?

HK-Steve
 
I have found the beta a little better on PPD,
If you are going to use the beta, be sure to configure the slots manually..or it will not fold.

Please do Not use the Beta flag if you are not an Official beta tester.
When new beta projects are released, you will take these new WUs away from the Official beta testers (so, less WUs for the testers), which means it will take longer for the project owner to get feedback.  And it also will take longer before these projects can be released to advanced and full FaH.
 
And you are running the risk of getting projects that can fail or can get a PPD that is too low and have to be adjusted by the project owner.  If you think that you're getting higher PPD with the beta flag, then you just have luck.
 
Edit: I think that you're better off with the advanced flag, Steve.

I'm sorry for the misunderstanding, Steve.
I now see that you were talking about the beta Client (not the flag)... my bad!! 

BadBertie

bcavnaugh
I stopped using that Flag altogether.
Are you using the Beta Version of the Client Software or the Current Version?
On my 1080 Running Beta I see mostly Core 21 and a random Core 18.
Their are no new Cores out that I know or any in Beta Status.

I'm just using the current version. It was all a bit of a rush, so I'm only now just thinking about flags 😩

How's the beta client, Bcav? Any wierdness going on? Better than the current of hard to tell?

********** Reference ********** Beta Client V7.4.15 ********** Reference **********
Below are Know Error over at Stanford but I think it is running well. I do like the Client being a True x64 app now.
I have it installed only on one Rig my T630 with 2 GTX 1080 running between 2025-2088 NOW WITH advanced flag in place
I have not had any Failed WU with Driver 373.06 but with the three after this driver all WU failed.
Their are still small issues that have not been corrected like the errors below.
And what HK-Steve said above.
 
*********************** Log Started 2016-11-01T02:25:11Z ***********************
02:25:12:ERROR:FS01:'opencl-index'=1 is in use by another folding slot but GPU 1 matches this device's PCI bus=4 and PCI slot=0, please correct this by removing any manually configured 'opencl-index' options.
02:25:12:ERROR:FS01:'cuda-index'=1 is in use by another folding slot but GPU 1 matches this device's PCI bus=4 and PCI slot=0, please correct this by removing any manually configured 'cuda-index' options.
******************************* Date: 2016-11-01 *******************************
******************************* Date: 2016-11-02 *******************************
02:00:32:ERROR:Receive error: 10054: An existing connection was forcibly closed by the remote host.
******************************* Date: 2016-11-03 *******************************
 
New FAH software client: V7.4.15 in open beta testing August 23, 2016  by Vijay Pande ·
 
Somewhere on the Forum is a Thread about this Beta Version V7.4.15
 
This Fixes the Errors above, thanks to HK-Steve

bcavnaugh

ipkha
Does this help on maxwell as well? I have both maxwell and Pascal in my system.

NO

Can I set it for just one core, or do I just not add the flag?

DutchForce

ipkha

bcavnaugh

ipkha
Does this help on maxwell as well? I have both maxwell and Pascal in my system.

NO

Can I set it for just one core, or do I just not add the flag?

You can set the advanced flag (client-type = advanced) for each slot, so if you are sure which slot is the Pascal card then you can add this flag to that slot.  If you're not 100% sure if you have the right slot selected or that your cards could be mixed up (like my cards are), then just add the flag to both slots.

That seems to not work in the Beta Client Version.
After I added on each of mine 0 and 1 it put it under Expert and removed them from 0 and 1 Slots.

The beta client is not automatic.
 
Each GPU slot needs to be set manually for Cuda and openCl. set to 0 for the first GPU, for both,
Second GPU set to 1 for both Cuda and openCl.
Third, set both to 2 for both cuda and openCl.

DutchForce
It works for the current v7.4.4 client, both flags stay in their own slot.
So I guess the beta Client is more "intelligent", because if you have two slots and you want to use the same flag for both slots then it's easier to just set one flag in the Expert tab.

It might be, I have the same two cards so that may as well be part of the reason.
I thought you were running the Beta Client?

DutchForce
No, I prefer to stay with the "Official" / current version and wait till most of the bugs are resolved.

When my cards were mixed up I've also set the opencl-index and cuda-index manally, but they both need to be the same number for each slot.
So probably for your Slot 0: opencl-index = 0 | cuda-index = 0
                      And Slot 1: opencl-index = 1 | cuda-index = 1

Yes, DutchForce is correct..