Thanks for taking the feedback Mr. Plus and implementing it so quickly.

I'm doubling my donations for the next week.

Thanks

^  I would second this.

As a work around I use a 20 minute interval to make it less annoying on my gaming.bat

Hey Mr. Plus.

You've done some great work. Thank you for the releases.

If I could make one feature request:

Someone mentioned a similar issue in the last page. Could we have a config file box for "Gaming Mode (disable GPU 0)"?

I'm aware on how to change it on the config file side. But I swap between gaming and mining pretty often. 2 Cards are always mining but when I'm not gaming the third is as well. Nothing super critical but figured it would be worth mentioning. It would be nice to be able to flag a box at whim and toggle between mining and gaming mode.

Second a troubleshooting question for anyone:

I user shell:startup to launch the miner on reboot. It does not appear that this new GUI version can be launched in this manner. Has anyone figured out a work around or is this a problem that it localized to my rig?


Thanks!

Hello Everyone,

Just wondering if anyone else has an issue with the x17 algo taking ~5 minutes to come up to speed. I've tried a few miners: Alexis, and polytimos but they take about 5 minutes to come up to speed and im not sure why. Its a rig with 8 TI's, 40GB Page file and 16GB of ram. On either miner it reports ~36Mh/s for the first 3 or 4 minutes (like only 2 are hashing) then jumps up to ~140 to begin its climb over the next few minutes to its top speed of roughly 160 Mh/s. OC doesn't change this either. It does start all mining threads at launch.

Any help would be appreciated.

Thanks!
 

Hey Every,

I replaced KlausT's miner with just a miners fork. Just renamed klaus' to ccminer.old and named jsutaminer's to ccminer.exe. I also set the flags -i 7 -c 4 inside of the klausT powershell script. Works fine .

edit: I also saw that the interval flag was removed from the .bat files. Was this intentional?

I'd also vote to remove  Palagin. It seems hes gone mia from the dev side and it consistently just causes issues. I've been playing with justaminers fork but have been using klaus-T for the past few weeks.

Hey Mr. Plus:

I am also experience the issue with two miners being opened.

I also experience not all miners benchmarking on the first go around. If you run the reset profit script then re-launch the miner it will then see all algos and attempt to benchmark everything you selected.


I can also confirm recieving benchmark statistics that are wildly inaccurate (IE 14 GH/s for neoscrypt). I haven't witnessed this issue on x17 or this current master release specifically but I have on neoscrypt and tribus many times on previous releases.  

Win 10 rig with 8 1080TI. Nothing else special about it. Up to date.. Nvidia 390 drivers and purely used for mining.

@Mr.Plus

I have replaced the brain folder. On launch it did not appear to update profits. To remedy this I ran the reset profits.bat and it has successfully updated.

I am currently monitoring the program to see if updates are posted on the 10 minute interval set. I have an unfortunate feeling it is not but I'll update you with a definite once I know.
Edit: Thank you for the quick update. Seems to be working as intended!

Side Question:

What would be the best way for me to adjust the profits down for a specific algo? IE: I have a miner that takes a dev fee (3 minutes) but yields better results. It's worth using if I were to mine the algo for any amount of time greater than 15 minutes.

Option One) Chance sleep interval to 15 minutes and manually move the hashrate of the miner down by 20%. Any other options?

Thanks!

@MrPlus

I'm attempting to take this project for a spin but I'm not having any success with benchmarking it.

Im on a 8 1080Ti rig using Ahashpool plus. No other modifications made except changing my address and selecting the amount of GPU's correctly.

It does not appear to write the stats down correctly. Furthermore it seems to open a second miner before closing the first one and they seem to run concurrently for about 10 minutes. Then the original miner is closed but it doesn't appear to log the stats anywhere. I know I can set them manually but that's less than ideal.

Any help would be appreciated.

Thanks!