Quote from: kerney666 on April 19, 2019, 01:13:54 PM

Quote from: Kerppa77 on April 19, 2019, 01:10:49 PM

Quote from: kerney666 on April 19, 2019, 12:58:18 PM

Quote from: Kerppa77 on April 19, 2019, 12:30:01 PM

Quote from: kerney666 on April 19, 2019, 09:20:11 AM

The interleave adjustments arent always an indication of error, I have a few setups that need to adjust every 2 min or so per gpu.

The 2100 h/s is the normal Vega 64 hashrate at 14*14 or 15*15 before memory timings are applied. Have you verified that the memory tweak tool applied your timings correctly?

Last, what clocks are you using for your rigs?

Indeed,

I finally succeeded to get the --current values out from the rigs and it seems that the TRM 0.4.4. haven't managed to set updated timings on the GPUs that run with ~2100H/s... (all GPUs in the 3 rigs and one GPU from the 4th rig has still CL 20, REF 3900 RAS 33 RFC 260 etc. while other better performing 5 GPUs has CL 19, REF 15600, RAS 28, RFC 250).

What it the reason TRM 0.4.4. haven't managed to update all the timings? Or should I do manually a .bat to get things set properly? I have so far just run the TRM 0.4.4. just like TRM 0.4.2. w/o any added parameters or anything.

We dont set those timings for you, everyone needs to download ElioVPs tool themselves and include the timings mod in some .bat file Grin

. We dont want to bundle it, its a slippery slope from a license perspective imho.

I am thinking a little about building some flight control gui for TRM though that would be fully open source. No idea when Ill get the time though...

hmm.... Now I wonder how one of my rigs still have updated timings in 5 out of 6 GPUs Cheesy

I did indeed wonder the same thing. Quite certain we didnt set them for you

.
[/quote]

HAHA I found the reason

My shortcut points to old .bat which have the config I used with TRM 0.4.2. Cheesy

Now I got all fixed.... thanks for the help... awesome miner and results! Thanks!!!