New .15 version is up.

- HU's issues resolved
- Lots of false import issues resolved

downloaded the trial today, and having the same issues using Win7+HM2

other issues I had:
-moderate flashing, not so bad
-I could only get the stats to stay in the right places if I sat in the same seat on all tables
-at some point during my session stats totally reset on 2 of my 3 tables, even though even though the table finder in HM2 still showed >100 hands on those tables

yea thats the thing though...the first table i go into the setup is correct and locked but when i try and go to my 2nd/3rd/4th table is when the names start messing up but the stats are correct just the names are messing up

If by HU issues you mean the flashing, then that isn't fixed still.

Make sure in your HUD options that seat label is set to any. I'm not a PT expert, but I have this working on all tables, no matter what seat I'm at, even 6-max and full ring mixed. I'm trying to become more of an expert with the HUD so I can give more detail. Maybe try a default bovada table? Maybe try hitting reset for the table layout, getting them set, and then just selecting save only. I'll continue to play with PT HUD's, but there is a way to get them coming up in the correct spot.

Also, make sure you're not using a preferred seat in Bovada settings. Obviously if you do this, then it's not going to align.

I'm referring to this...

Curious if getting the time bank to work is high priority at the moment, thanks.

The flashing when you are at a HU's table w/o an opponent will be fixed in next build. It's been fixed, just wasn't able to get it into the .15 build.

We're trying to figure out some ways to trick the PT HUD. It's not an issue in HM, and the developer is looking into it.

I'm using HM2 and was unable to click timebank or the last hand link - same as 4barrel

Yeah, I've been looking into this. This wasn't happening with HM2, and now it seems it's happening with both. We had over 5 months of beta testing with a lot of testers, and no one reported this, so we're trying to figure out a work around.

So I'm just going to throw this out there because I'm not sure right now what we're going to do and would appreciate any opinions.

I'm not sure the time bank or last hand will work. The Hud's are preventing them from being clicked for some reason. I've been having the developer on this project trying several work arounds without success. We're still trying a couple of more things, but it's highly possible it will not work. Would that completely turn you off to the catcher or don't care?

Personally, I pretty much never use a time bank on bovada and I've played on there for quite some time now. I don't know how big of a deal it is. Maybe a bigger issue in tournaments. For cash games, I pretty much never need more than 30 secs to decide.

Does the Bovada Hand Catcher HUD replace the Hand Grabber? I am guessing if it can scrape, import and display a HUD then it already is grabbing all the hands???

On a side note, version .16 is up for download. Some import fixes and the HU's flashing should be resolved now.

Yes, except it cannot grab zone hands.

Can confirm this is still the case with .16

Any idea on a timeframe for sngs/tourneys?

If Bovada catches you using this will they take your monies ?

More info: played a long session where the only hand that was not imported was the one where the villain was all-in preflop and busted as a result. There were other hands where we were all-in preflop but did not result in a bust, these imported fine.

I'd like to know this too.

Still no response to email sent on 6/16, sent a fresh email today.

bought the program yesterday cause I figured all the bugs would eventually be ironed out, but if I can't use time bank or click on the previous hand, I'll have to stick with Holdem Indicator, and hope you'd honor a refund

It's not against their terms and conditions. They don't want you datamining info on users, which of course you can't do on there.

So I'm confused. So you're saying it's working fine now, minus one hand that you think was missed with an all-in pre-flop correct?

We're still working on it, I was just asking the importance of it for most users. Example, for me, I don't care. It may turn out it's not possible to get that part working. I don't know for sure right now. But if you'd like a refund we can disable the code and return it no problem. Just contact support.