• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

RC4 issues, bugs & feature requests

Status
Not open for further replies.
There's something weird going on with the options screen, specifically when you click the Apply button after making some change, that spikes CPU usage to the max for far longer than seems reasonable. Once the OK button eventually becomes clickable, CPU usage drops way back down and the slowdowns-to-the-point-of-complete-unusability I've been having mostly go away. They only mostly stay away though with Darksend disabled.

edit: ignore the above, still getting random periods of CPU being hammered and GUI halt. Can't see anything in the debug log as it scrolls by that obviously precipitates this behaviour, or ends it. Grump.
 
Last edited by a moderator:
I think the client needs an auto-update downloader or at least an update check dialog as I can't keep up with checking forums every 5 minutes for new releases. No sooner do I download a new binary and update another update comes out and im behind again.
 
Bug (that you're probably already aware of): Invalid number (-2) in "Darksend Rounds" column in the Coin Control window. (v10.12.29 linux)

darkcoin_coincontrol20140815.png


We have reproduced the issue, still looking at it. Stick to rounds=1 in the meantime.

Thanks for addressing this, I was experiencing issues with this as well.
 
In the latest version, in the send page, funds selection defaults now always to no preference after restart.
Is this planned change or mistake?
 
In the latest version, in the send page, funds selection defaults now always to no preference after restart.
Is this planned change or mistake?
This is a planned change. The default behaviour of the wallet re. Darksend was changed to "Darksend disabled" in v29. That's why we changed the funds selection to "no preference" as well.

When Darksend functionality has stabilized and people have adopted how it works and feel comfortable about it, we will revert the default to "Darksend enabled" again ;)
 
Breaking stuff is how you learn! :grin:

Use testnet, with tDRK it doesn't matter and the principles are all exactly the same, so you'll know what you're doing (and what not to do!) on main-net.

My wife is away on business next week. I can see a lot of evenings spent in a darkened room with takeout and terminal sessions :D
 
Eh? You know what? I give in. I'm totally out of my depth. I haven't got enough DRK to keep paying Yidakee to update my nodes. Every time I try to follow instructions I end up breaking something. And there I was thinking that I had to update my masternodes to 29 and I think I've broken one of them whilst trying to do so. I'm just going to go to bed early (GMT+1 here) and see where things are in the morning and if there is any more clarity on what needs to be done, to what and by who I'll be a happy man. /rantover (more upset that I've been tinkering and been caught out again :( )

Don't give up! I don't know what your depth is, but I assure you that with some reading updating a masternode is super easy. Having said that, sometimes stepping away for a few hours is a good idea. I'm quite confident with my MNs and I have done everything by myself since the beginning, but the other day I mixed files from two masternodes when restarting them and broke both. I had no time to repair things, so I just stopped everything and came back next day. Bonus 1: I skipped one update. Bonus 2: the problems my masternodes had caused had gone from everyone's memory and fixing them was much easier than if I had tried when I broke things.
 
This is a planned change. The default behaviour of the wallet re. Darksend was changed to "Darksend disabled" in v29. That's why we changed the funds selection to "no preference" as well.

When Darksend functionality has stabilized and people have adopted how it works and feel comfortable about it, we will revert the default to "Darksend enabled" again ;)

Hi flare,

Darksend is not disabled by default in windows wallet though. The box is unchecked on the wallet gui. I'm running the wallet in testnet, it does the denominating as usual when i start the wallet because DS isn't disabled.
 
Don't give up! I don't know what your depth is, but I assure you that with some reading updating a masternode is super easy. Having said that, sometimes stepping away for a few hours is a good idea. I'm quite confident with my MNs and I have done everything by myself since the beginning, but the other day I mixed files from two masternodes when restarting them and broke both. I had no time to repair things, so I just stopped everything and came back next day. Bonus 1: I skipped one update. Bonus 2: the problems my masternodes had caused had gone from everyone's memory and fixing them was much easier than if I had tried when I broke things.

I'm a programme manager specialising in virtualisation and storage who has managed to avoid touching Linux for the past 15+ years. I'm pretty deep in my field but I'm about ankle deep in altcoins :) I'm loving learning something new.

I do think it would be useful to provide a little pre-amble with the new release notices i.e what needs to be updated and by who.
 
Hi flare,

Darksend is not disabled by default in windows wallet though. The box is unchecked on the wallet gui. I'm running the wallet in testnet, it does the denominating as usual when i start the wallet because DS isn't disabled.
Did you start off with a fresh installation of Darkcoin v29 and deleted the registry keys in

Code:
HKEY_CURRENT_USER\Software\DarkCoin\DarkCoin-Qt
HKEY_CURRENT_USER\Software\DarkCoin\DarkCoin-Qt-testnet

before? If not your previous settings are retained of course.
 
Did you start off with a fresh installation of Darkcoin v29 and deleted the registry keys in

Code:
HKEY_CURRENT_USER\Software\DarkCoin\DarkCoin-Qt
HKEY_CURRENT_USER\Software\DarkCoin\DarkCoin-Qt-testnet

before?

Oh.. No.. Let me do it. Thanks.
 
Status
Not open for further replies.
Back
Top