thx! i won't be able to test it for a couple days unfortunatly... but i will alert you and send the logs if any future crashes happen

Just upgraded to a new computer and Windows 10 and I constantly have individual tables not showing up in the catcher. No matter what I do it hasn't been catching them all. It only seems to be in tournaments. I 4 tabled HU cash for 8 hours yesterday with no issues. The tables are also flashing all the time and it's really annoying.

Honestly with as much trouble as I've had with this thing I'd rather just get a refund and quit using it. It's not worth what I paid considering it rarely if ever works correctly.

Back to tournament indicator and the converter I guess...

Just noticed I'm on version 4.9, maybe the new ones fix it.....

just wondering. if i buy this program but still download and import my hands via the hand converter. will pokertracker4 count these hands as double or it will it think i played 1000 hands as opposed to 500?

just wondering because i'd like to have a more accurate database . imported with the converter today and it missed hundreds of hands

Yes, try the latest version. The GUI window button you're talking about, it's going to be removed. It's really pointless to have now w/ the on table time bank and everything.

With the flashing, remove auto time bank. OR you can try the new coherence mode setting also in settings on BCC.

Actually this last version by all reports is working well. You shouldn't have any flashing at all. All hands should be getting snagged as well.

You'd have to create a separate database. I know some people have been successful with using a different Hero name in the catcher (than the converter) and then setting a timezone offset. This will put the hands in the same DB but have them slightly different. I haven't tried this myself though.

The catcher shouldn't be missing hands though. I know there's still one MTT post issue. But cash, I'm not missing hands. Is anyone else seeing any dropped hands?

2.05.1a hasn't crashed once

the converter was missign hands. not the catcher. i havt actually used the catcher yet

I have to say, the improvement made in the last few months have been impressive. I no longer have issues w/ cash except that once or twice a session, it will not catch a hand. I'm talking 1 or 2 / 300-700 hands a day. I have been mostly playing 2 tables or less FWIW. Keep up the good work and thanks.

No this is still happening. I have noticed it will catch most tournaments, but for some reason (and I may be wrong) when the tournament description is something like (7500 chips 20-minute levels) the BCC fails to find the tournament number. If it has a normal tourny description like $5000 Gtd (ss) the BCC finds the tourny number fine.

will this work on more than 1 computer? ie my desktop (main) ....laptop wen im out.

or do i have to buy another license

I have it on two comps so I know it will work on two. I am not sure how many comps it is good for though.

Ok, interesting. I don't think I've seen this, but like I said we're actually going to be removing that GUI next build any ways. It's not needed anymore since everything is on table now - yeah! And I have zero reports of issues w/ 5.1a on any forum or support emails - double yeah!

One license is good for activation on 2 systems. And then you can purchase additional activations for that license as needed.

I noticed this happen twice now, and like I said I could be way wrong (I am no software genius so I know I could be way off with my observation). I know seeing it happen twice is not really a great sample, but each time the BCC couldn't find a tournament number that was the only thing I noticed that was different, and it also happened last night. Not trying to bash the software because it's great and probably already paid for itself, and if this is the only minor issue I can totally live with that.

just played my first session w/ v.2.05.1a (Windows 7, PT4) and had a weird experience/crash.

3.25 hour session. (mostly cash, 1 MTT)... and I thought everything was working smoothly except when i was wrapping up the session i found this error window behind my tables (pic attached): "Error: We're sorry. The application has encountered an unknown error and will be terminated. Please send your BCC.log to our support."

I clicked "ok" and BCC closed. idk if my HUD had been frozen and I didn't notice or what. had to re-open BCC and reset HUD stats for the last few min of my session.

also, had a table w/ a 3-word name today that wouldn't show the HUD. hands were showing in PT4, but no HUD (old issue)

sending logs to support...

Ok, odd, but thanks for letting me know. I didn't even know that error screen existed. Yeah, if you can send your logs that would be great.

I thought the 3 word table name was fixed. The issue before was the header file was slightly different than what was in the stream. If you enabled logging before you ran, then if you can send the log that is in your LOGS directory from BCC, the developer can see what the issue would be w/ the naming. It's something simple like one character is off and doesn't match.

session #2 using v.2.05.1a created the same error window except this time i noticed it in the 1st hour of my 3.75 hour session. I just ignored the error window and BCC seemed to continue operating and catching hands.

only issue i had this session was that BCC failed working w/ 1 of my 2 MTTs tonight (waiting for tournament number). issue i haven't had in a few weeks.

anyways. i sent support all the logs and info on my 3 issues of the day etc etc. both old BCC.log and the new bigger logs. cheers

Ok, great. Thanks for sending those logs in. I spoke to the developers and they said they already know what the issue is. It's an issue with the threading synchronizing because of the extra layers of the time bank and last hand buttons added for auto time bank. So they said they can fix it pretty quick. Thanks for sending those files in. Really the most important one, if you have a crash is just bcc.log. The bigger ones I don't think we need for this type of issue.

Just FYI, if you want to remove this as an issue and use this version, just disable auto time bank and it won't crash.

I still have .43 version up as the stable release build until we get this new auto time bank issue resolved.

Cash games work great for me.

For MTTs, whenever I get switched to another table, most of the time it doesn't pick up the new table even if I restart the program and do the "Start/Stop HUD" routine. It stays with the "Waiting for tournament number"

Thanks for any help. Works awesome otherwise.

What version are you using, because this is an old bug. I haven't seen it do this in awhile. If you don't have 5.1a, the link is in this thread.

v2.05.2 Beta up for download:
http://acepokersolutions.com/poker-s...up_v2.05.2.exe

Changes:
- Fix auto time bank crash when closing out tables.

This should address anyone who had an issue w/ auto time bank. We changed the threading entirely so there's no chance of conflict anywhere. I've ran it and haven't gotten anything, but it never crashed for me or my guys before either though. But I'm hoping this should be it.

Haven't tried the latest version yet, but 2.05.1a works fine for me in Coherence mode. The "Enable Mac Coherence" button doesn't seem to have any effect, on or off. But whatever you did it works now. Thank you!

Interesting. The enable coherence mode is supposed to simulate what was in v4.6. But... that's awesome it works! I had them put it in there just for you.

I ran about 7 hours today with 5.2 and time bank enabled w/ no issues. The guys have run several hours too. Zero hand errors too, which is great. I think it's looking good.

Still haven't updated to latest version, but it seems that hands aren't importing quite as fast as they used to. Maybe 3-5 seconds longer for everything to refresh after the hand is over.

Well, the hand is written right after it's complete. Nothing has changed here about this at any point. The speed your DB picks it up and then updates stats is the lag. It really doesn't have anything to do with the catcher. And I've run several sessions and haven't seen anything like that.

But thanks for letting me know anything you see you think is odd. You never know what a potential issue might be.