Exactly. It's actually impossible now to specify all scrypt settings using solely the config file, since the intensity sanity check doesn't detect "scrypt" : true from the config file.
This didn't help, and seems redundant. I've never had to specify a kernel for scrypt, only one exists anyway. I'll just wait for the sanity check code to be fixed.
It's not redundant if you use that
instead of --scrypt on the command line. I was just telling you how to put it into the config file.
I did put that in the config file (in addition to the "scrypt" : true that was already there, above the intensity line), and cgminer's new sanity check still didn't detect I was using scrypt. It's clearly tied to the "scrypt" setting, which just isn't picked up from a config file yet . The setting itself works fine, enabling scrypt mode, but the sanity check code doesn't detect it's there. It also fails to detect scrypt mode if -I is specified on the command line before --scrypt. Neither of these bugs existed before 3.3.2.
"scrypt" : true,
"kernel" : "scrypt",
"gpu-engine" : "690,550,650,690",
"gpu-fan" : "80,100,100,100",
"gpu-memclock" : "930,720,790,930",
"gpu-threads" : "1",
"gpu-vddc" : "0.95",
"intensity" : "17",
"thread-concurrency" : "8192"
The above config settings still won't allow high intensities, if --scrypt is not used in the command line. I can't see what that kernel setting is supposed to do with scrypt, since the default kernel is the only one that can/will be used.
I'm confident ckolivas can fix this easily. I was actually surprised the GPU mining code is still being modified.
