I'VE NOTICED THAT INTENSITY SETTINGS DON'T WORK--
In the most recent versions of CCminer (2.2+), intensity settings appear to be ignored, and a default setting is applied. Other users have posted about not being able to disable auto-tuning on algos like Scrypt pr CryptoNight.
Frankly, default or auto-tune settings are often the best, but I have noticed that some older tuning parameters are ignored. --scryptr
I have only been wrestling with ccminer for the last 4 hours, and can tell you for certain, every combination of INTENSITY parameter I threw at it, was ignored. The default settings are NOT the fastest for my cards. I have also been spending this whole time trying to learn this crazy "launch-config" parameter, digging through documents to find which of the 1,000 different technical specifications ccminer needs for me to accept. It's parameter list is confusing to say the least.
Intensity is hardcoded in implementations of many algos (for ccminer 2.2.4).
It's a good thing to avoid you posting on youtube that your rig is on fire
I DON'T POST ON YOUTUBE--
But I do enjoy custom-tuning my rigs. Perhaps Epsylon3 could "star" (mark with asterisk) the algorithms affected in his documentation. Then, make a note of explanation.
Scrypt, Scrypt-N, BoolBerry, CryptoNight all had difficult-to-master tuning parameters. Even NeoScrypt could be trouble as the code changed with optimization. Spending an hour on un-necessary, non-effective tuning could be avoided with a few documentation notes. --scryptr
Agreed, also intensity will NOT cause hardware failures. If you have a system that starts on fire as long as the GPU is operating within spec you've done something wrong. Mining software has never once been responsible for any miner fires, it's always people using inferior hardware or halfhazard setups, like daisy chaining splitters. Hardware will fail regardless as manufacturers usually don't test them super rigorously, which is why one of the secrets of mining is knowing the right brands to buy.
I find it hard to believe Epsylon would intentionally hardcode in a intensity value unless it's to artificially reduce performance of his miner. Tweaking intensity has been a staple of good mining for a long time.