-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to edit commands when running NiceHash Miner? #288
Comments
Unfortunately you cannot adjust commands NHM is giving Excavator (yet). I suggest you open this ticket in NHM repo. Alternatively, if you restrict yourself to daggerhashimoto mining only, you may try out following experimental wrapper: https://github.com/nicehash/excavator/tree/master/experimental It has watchdog (restarts Excavator if it crashes...) and Windows autostart service. Additionally, you may apply overclocks and no 3rd party tool is needed to take care of it. It is a pretty solid mining solution that takes care of everything. |
Thanks for the great advice, but I've solved this issue another way. Probably someone will find it useful. I've put the file with custom commands to Excavator directory in Nicehash plugins and added custom arguments to |
I believe that moving custom command-line arguments for miners/plugins to a more obvious place will make Nicehash UI more user friendly. |
Okay great! I will leave this issue open for others, if anyone wants to do the same. |
How does your commands.json looks like? {"time":10,"commands":[ Try to add this but I cannot get passed =========================== www.nicehash.com ========================= Build number: 514 [16:50:19][0x00001c18][info] Log started, build v514 |
okay, looks like I can generate the commands.json from the octune.html. |
still get a problem, when I add -c command.json, it just freeze at core initialized. |
cmd_1.json
resets and drops any changes when Excavator starts from Nicehash application. How could I apply all my API commands without using HTTP API?The text was updated successfully, but these errors were encountered: