Insideman

Thanks, it seems I missed this thread. I can report a repeat of the incident, today at approximately 20:30 BST. What happened this time was that I logged into the client. I then waited a bit (again in the range of 10 minutes or so) and then when I began to play (Hexapros in this instance), the sound was gone (confirmed by playing a YouTube video that had sound). It's like the client is disconnecting itself from the sound system after a certain amount of idle time. Like it closes the connection.

Thank you for your reply. That's a shame.

Hi. I am trying to review my play for the previous month and was curious whether it's possible to see all-in adjusted winnings. So basically anytime a had goes to all-in, how much one should have won based on the percentages. Primarily I am interested in this for cash games. I spoke to support about this, but what they sent me did not include those numbers. Before going back to support, I was wondering whether you know if it's possible to receive such data from Unibet. I noticed that from within the software there is an area that measures "luck" (in the lab area), so that would imply that Unibet is tracking said data already.

Today during my session, my hand was folded preflop, but I didn't press the fold button. My mouse also wasn't near the fold button, I clicked the 'POT' button. My time bank was low, but it didn't look as though I ran out of time. Also, if I had been folded due to running out of time, wouldn't I automatically be sitting out? I was still active on all tables and there was no prompt to sit back in. I was able to capture the incidence on video, the hand# is 1975313361.

No, there was no app crash. It was just that individual window that froze. Unfortunately I wasn't recording my screen before I clicked +1, but I started recording shortly after it froze. From that snapshot I can see that the +1 occurred at an NL table, whilst I was playing one Hexapro, with an additional Hexapro loading in the background. I was either in a waitlist for the Hexapro in the background or it just loaded when the freeze happened. I'm reasonably confident that there was no MTT lobby, since I wasn't playing any MTTs and I don't think I was browsing any lobbies either.

I found a bug whilst using the debug version. I clicked the +1 table button to open a new table and the new table that opened up froze (it wouldn't let me buy in, so no loss of funds), but otherwise the software was functional. I think I've seen this happen rarely in the past, but since I'm using this software version, Is there any file I should share with you regarding it?

Alright, thanks for the update. Do I need to do anything or will it just update and overwrite my version?

I wanted to follow up to say that I made it to the end of the quarter without crashes. I have a suspicion what might have been triggering the issue on my my machine. Shortly after I started using the debug/dump file version, my numbpad "died". I was using a detachable numbpad, connected to a USB hub. It basically stopped working in that config, and I moved it to a different port and it doesn't seem to malfunction anymore. The numbpad was what I connected to the crashes, since I would type a bet with it and then click bet and the software would crash (twice in 3 days). If I had to speculate, I would say this may have triggered something in the client as it seemingly did on my Windows 11 install (I received a USB controller error one time). It may also explain why the crashes started happening suddenly, since I hadn't observed that behaviour to that point. How long can I keep using this software version for? Thanks for the interim.

Fair enough, I will resume play as normal and inform you if I observe the crash again. Thanks for the response.

Thanks, I'm on Windows 11. I should add that I have a suspicion what might be causing the crashes. As I said, I was frustrated because the crashes happened in big pots with strong hands. I recall in both situations I typed a bet into the bet size box and as I clicked the bet button, the software crashed (to be more precise, in both situations a 3-bet had occurred preflop). I also have a recording of both crashes if you would like me to provide these files for you. I will give the special client version a try, but I will also avoid typing bets for the interim. As you can imagine these crashes are relatively expensive, so if I think I can prevent them, I won't deliberately try to cause them. It was suggested to me to use the bet slider to lower or increase bet sizes and I will try this, but perhaps you can test on your end whether typing the bets is the issue. Of course if my software crashes again you will have my debug files. Is there anything I can do about the long "I'm not a robot" dialogues? My understanding is that not everybody has these checks. I'm guessing it has to do with my location in the UK. My ISP is British Telecom. I tried my phone network and it was the same, though I have noticed that there are less checks on other clients (browser etc.). I understand if you don't want to comment on this, it would just help recovery from client crashes. I've always had a small amount of client crashes, but in the past at least I could log back in and often save the hands that I am playing. That is not possible anymore, so the issue has become much more significant.

Hi, I'm currently experiencing infrequent crashes (0-1 times per day) using client v.3.29.0. They have been additionally frustrating as they happened in big pots with strong hands, and I have been unable to log back in quickly due to the long robot check sequences. I would like to see what there is I can do, as I still need to generate some XP before the quarter is over. The most recent thread on this topic appears to be this one: Is there a new special client build I should install to try to resolve the crashing?

Thank you for your response, I have sent you a PM with the requested information.

Hi. Whilst playing today in the UK I experienced 3 disconnects. The last two were in short succession, so I had to stop playing to avoid losses. During each disconnect I was still connected to the internet and I could access any site except Unibet. I have video footage of Unibet being down whilst still being able to access major sites such as BBC, CNN, Reuters, Yahoo etc. These disconnects cost me money each time as I was forced to sit out due to the reconnect not happening quickly enough. This appears to be an issue on Unibet's side since I don't generally have any problems connecting to Unibet and my internet is working. This is additionally frustrating as I have a bonus that will expire soon if I don't clear it. Are there known server issues at the moment? Is there a time frame for them to be resolved? Can I claim for compensation for the disconnects? I can provide video footage if necessary. Thank you.

The issue is persistent for me as well.