Quote:
Originally Posted by dlmcg3
I've read that bovada thread before. I tried it again with the lobby set to casino games and even minimized the lobby and the huge spikes in CPU usage still occur. I can post 2 pictures of my task manage with and without DH running so you can see the difference if you like. My CPU usage on all 4 cores is going from <10% to 75% at the same times when the Ignition UI becomes unresponsive.
No, it's ok. I believe you. I'm just saying that it happens on their platform depending on their connection and server load. Bovada did expand their servers and speed, and it has been better, but I'm just making you aware that of course DH is going to some resources, but the main culprit is Bovada. That being said we want to find more efficient ways so that DH doesn't cause any delays w/ Bovada's table updates. As a player myself I've experienced this many times (and you can see from the bovada thread others have as well) who aren't using DH.
Someone also posted this to help, which I think mainly has to do w/ the rebuy timeout, but it might also help.
-----
Maybe this has already been mentioned but there is a Win 10 fix for the issue of lack of connection to server/not being able to rebuy at tables. This happened to me repeatedly in the past where I would "lose connection to the server" and not be able to reload at any of my tables, destroying my sessions repeatedly. I spoke to support about it and they mentioned this:
Control Panel > search "performance" > adjust the appearance and performance of Windows > advanced > click "change" under "total paging file size for all drives:" > uncheck "automatically manage paging file size for all drives: > check "custom size" and then set both "Initial Size" and "Maximum size" to the figure listed under "Recommended" at the bottom. Then click Set and Ok and restart your comp.
I've played for a few days now after this fix and haven't had the disconnection issue.
-----
We are looking into a recent issue where DH is coming to the forefront. It's the first time we've seen that, and maybe this is related to your issue. I'm not sure, but we're looking into it and I can update you when I know more. Thanks for the feedback!