yes, support seems to be useless, there are no answers to questions
and so I used other miners, but in a single version, apparently other options need to be considered

version 3.8.0 in triple maning mode does not work well
there was some kind of failure (perhaps from the program itself or from the fact that one of the cards number 2 fell off) after which everything went wrong, the found shares were not accepted, as a result, more than six hours of work wasted
https://ufile.io/avxz53eb log

Hello
I can’t set the static voltage of the core, for example, to 1300 MHz, the program does not accept a value, I assume this is due to the hardwired reduction limit from -525 to +525 and my setting is 1300 lower than the nominal frequency in 1990, please correct this or increase the range downward
version 3.7.7
---
update
unfortunately reducing the core frequency does not reduce the voltage, then these settings do not make much sense

lowering the voltage is obtained only by lowering the power limit, BUT if mining takes place of two coins such as zil and ergo, then during the ergo mining, the power limit is set correctly, and during the mining of zil, the power limit is not enough and the hash is greatly reduced, all this is complemented by the fact that the program does not understand the second line of powerLimits in the [zil] settings and uses only the powerLimits line from the [autolykos] settings

where can I read what's new in version 0.26.5?

the new version 0.10 seems to work well with 5800/6800/580, but the video cards began to fall off periodically, I think due to the fact that the consumption has changed and the fine-tuning of the power consumption has become ineffective and you need to slightly change the voltage upwards

whatever parameters I set, for some reason the speed above 86 megahashes does not want to rise in any way, there is a similar video card there is easily 93-94 megahashes on the latest version

I had similar symptoms several times, I removed all restrictions in the batch file for this card in terms of core blocking and voltage and set the tuner parameter to automatic mode, i.e. to -1, works well, but still sometimes blocks and reduces the selected value
the same symptom of blocking / unlocking is observed when I ask to close the program for half a minute or a minute

what does the form mean on your screen, shares 1/1/1 if these are found shares, disabled shares, obsolete shares, then there are too many obsolete shares and this is nothing good

hi
I can not set the value of the parameter --cuda-devices [0,2,3,4,5]
video card number 1 still starts, although it is not on the list

noticed this feature on 3080 ti video cards, if I connect the riser with a good cable pci-e coming from the power supply unit, then the speed of the lhr is about 83-86 megahashes, if I connect the riser with a cheap Chinese 6-pin pci-e cable, and the second end is in the power supply unit, then the speed of work video cards with lxr about 88-90 megahashes and so not on one rig, but on two where I have such cards and everything would be fine, but on these nasty cables after a week or two, black wires burn out near the side of the mount with the power supply cable and the card is just falls off, changed it repeatedly and all over again...

download this or a similar program and see for yourself, but most likely there will be a selection of different ports from different pools

almost the same thing happened for me, but on the Palit 3080 ti video card with 2 power connectors, then I changed the batch file a little and brought two different pcie branches to the riser and to the power connectors, after which it became normal (~90mhs)
in the example below, the second card with lhr and batch file settings (driver 472.12)
--lhr-tune 0,74,0,0 --lhr-autotune-step-size 0.1 --validate-shares --send-stales --kernel 0 --pstate p0 --lock-cv 650,0,725,725 --lock-cclock 1005,1125,1110,1110 -i 25,0,25,25 --mclock 800,1000,980,820 --fan t:60[0-90], tm:90[0-90], tm:90[0-90], tm:90[0-90] --temperature-limit 65 --temperature-start 55 --gpu-init-mode 0 --dag-build-mode 2 --pl 54,0,74,102

by some miracle I managed to overclock it and she took 90-92 megahesh, so I agree with you everything works, apparently it helped me to switch the power cables

show your core frequency, the real one, which is displayed in hwinfo, for example, since on my 3080 TI cards it cannot be blocked and it constantly jumps up and down
I do not deny that such a result is possible, but my video card gives out otherwise

Apparently the LHR mechanism is individual and depends on the consumption of the video card, on my video card on the same drivers I can achieve somewhere 85-86 megahashes, while increasing the memory frequency over 850 MHz is not effective, the speed does not increase, and the LHR limit is reduced, as well as any locks with the parameters lock-cclock, lock-cv only reduce the speed, the optimal value is 0
I think this is due to the fact that with an increase in the clock frequency of the memory, the total consumption of the card increases and ultimately it exceeds a certain limit set for the LHR to operate

I don’t know where you saw such results, the 3080 ti video card cannot take the core frequency of the locked state in any way, the lhr mechanism will block the video card if it takes more frequency than the set limit value for bypassing lhr and therefore it is impossible to fix the core at a certain high value, which is what I have happens, in fact, therefore, the speed is 82-83mh otherwise it could be higher

not bad, on the video card Palit 3080 TI hashrate is about 82-83 with lhr 73

would anyone give the result
hashrate given by a regular 3080 video card with lhr?

thx, this problem has disappeared
BUT now another has appeared
bought a big navi 6800 video card and does not want to control the speed with the options --fan_control = 50: 60: 80: 30: 30: 90 fan_default_big_navi = 50: 60: 80: 30: 1: 90
when I start the rig with the fan_control option, then immediately the fan speed is reset to 0 and is not controlled by temperature and is constantly in this position, but if I remove the fan_control option and leave only fan_default_big_navi, then the speed decreases smoothly to the minimum stitched in the BIOS about 20% and also without control.
tried on version 0.8.5. and 0.8.6 driver 20.12.2, note that I also use the MTP program overlaying some settings in the SPPT

--lhr-tune 4
And how much does the usual 3080 hash give out in this mode and how many watts does it consume?

you need to set the parameters, for example -lhr-mode 1 -lhr 70 and then the miner will determine the optimal value by himself, decreasing by 0.1 for each lock found, this applies to versions 39.3 or 39.4