next time try thinking for more than half a second before you reply. don't bother commenting if you have no idea what you're talking about.

anyways, onto something productive for this thread, had some issues getting this program fully working with my pt3 but support was extremely helpful and got all the bugs fixed and up and running for me quickly. very useful program for the average to novice poker player who doesn't know much about stats and analyzing their game. gives a good look into specific situations and the stats involved with them and shows you how to do it all with your pt3 or hm.

That will be in the next version. We're going to have a system hard wired to your brain though, so no ear piece necessary.

Bugs should be all worked out now for the PT3 version of Leak Buster.

I downloaded LeakBuster and thought it was potentially useful. I emailed you regarding payment via FT and you responded quickly. I then emailed you asking about your methodolgy, got no response, resent the email through your website and still no response. You promise to reply to queries within 24 hours. It's been 5 days so far. Not impressed.

Sorry, our support (which is US based) was closed over the Holiday weekend. They started answering e-mails Sunday so I know they are a bit behind.

We pretty much never close (it was a first), and the support team is very quick with responses on non-holiday situations. I'll make sure they find your e-mail.

Hi

I tried to load my PT3 database but i get the following error...

Server: localhost
Database: PT3 DB
Port: 5432
User: postgres
Pass: dbpass
PlayerID:

Npgsql.NpgsqlException:
column holdem_hand_player_statistics.cnt_players does not exist
Severity: ERROR
Code: 42703
at Npgsql.NpgsqlState.<ProcessBackendResponses_Ver_3> d__a.MoveNext()
at Npgsql.ForwardsOnlyDataReader.GetNextResponseObjec t()
at Npgsql.ForwardsOnlyDataReader.GetNextRowDescriptio n()
at Npgsql.ForwardsOnlyDataReader.NextResult()
at Npgsql.ForwardsOnlyDataReader..ctor(IEnumerable`1 dataEnumeration, CommandBehavior behavior, NpgsqlCommand command, NotificationThreadBlock threadBlock, Boolean synchOnReadError)
at Npgsql.NpgsqlCommand.GetReader(CommandBehavior cb)
at Npgsql.NpgsqlCommand.ExecuteReader(CommandBehavior cb)
at Npgsql.NpgsqlCommand.ExecuteReader()
at PostgresConnection.f_OlDbReader(String query)
at LeakBuster2.e.a(Boolean b, Boolean b, Boolean b, Boolean b, DateTime b, DateTime b)
at LeakBuster2.e.a(Boolean b, Boolean b, Boolean b, Boolean b, Boolean b)
at LeakBuster2.Mainf.a(Object b, DoWorkEventArgs b)

Any ideas?

Looks like you are trying to import info that isn't no-limit. LB will only work with no-limit currently, but Limit and Omaha are on the way soon.

I only have NLH hand histories in my DB though.. still getting the error box pop up saying ".. leakbuster has encountered an unhandled error"..

Shame because this prog seems really cool

trying to give this a run, but it's installing so slow... any ideas why? Like 25 mins now and the bar just moved...

It took a while but very intersting... I ran it on a sample of 10k hands and going to play 10k more with it's suggestions...

so the .hud file you include in this isn't for PT3 correct? I'm confused since the video shows you how to import it, yet after doing so in PT3 nothing changes in hud...

Hi, I bought LB yesterday to work with PT3. You have to click on the HUD thingy at the top when it comes up on the table and select the new HUD to change it. Also, make sure you select the option to make this the defaullt HUD. I like this HUD - the color coding and the stats it displays are a lot more useful than the simple PT3 HUD.

When I imported my PT3 hands, LB highlighted 10 leaks in my game, even though I am winning 5.88 bb/100. I wondered about the optimal ranges in LB as I only play deep stack tables, but John Anhalt, the developer, kindly looked at my results and gave his interpretation. Basically, I am not aggressive enough preflop and should be 3 and 4 betting a lot more than I do. OTOH I am too aggressive on the turn and river, which means I should be more circumspect about double-barrelling and triple-barrelling. My biggest leak is that I don't win enough at showdown, so I'm probably pushing too hard with hands like TPTK. I have to remember Harrington's mantra: "Small hand, small pot; big hand, big pot."

Apart from the benefits of the LB program itself, which I believe will highlight problem areas in my game, an unsung benefit is the advice given through the videos on how to use PT3 productively. I just use the PT3 HUD but have never used probably 95% of PT's capablities, so the pointers on how to use the PT3 database to identify and plug leaks is very valuable in itself.

On the whole, I think this will prove to be $75 well spent. It may not be so useful at the higher limits beyond $2-4, but I think it will help to progress to those limits and it gives you a methodical approach to questioning your game when you go into the inevitable drawdown.

Despite my post above about support (out for Thanksgiving), I got quick responses to my questions from support and from John.

I tried to copy/paste my LB results but I couldn't find out how to put a png image into the post. If anyone knows how to do this, I can post my actual results from LB as an example of its feedback.

ty very much ernie, :-) had to do that last part, I couldn't figure it out was driving me crazy....

I think I'm going to also give this a try as I was surprised that even though I'm winning around 2.4bb/100 it said I was awful in some areas... lol some of which I'm partly aware of.

The one thing I really am having a hard time understanding is it says my c-bet % is rated 10, it's fine... but my flop Agg is too high? Don't these contradict each other?

Not necessarily. You could also raise the preflop bettor or donk-bet, both of which count towards flop aggression.

truth, thx for replies, looking forward to trying this

Help me understand how you set the time for importing stats.

1) I assume you are using HEM's hand database and not raw HH's, correct?

2) Does HEM's "day starts at" effect LB?

3) If I set LB & HEM to "yesterday" LB reports on 215 hands, HEM = 905 hands.

I only play in the evening, so I tried to just look at the last 24 hours this morning. It shows 902 hands. Close. (20 & 30 hours show the same.)

I did request thru email and received a response within 24 hours, but it said that you would get back to me. Thought someone in this thread might be able to help.

----------------Kitty

Not sure kitty. i use PT3. I don't think 900 hands is a sufficent sample size for the stats to be useful so doing a daily check wll probably not be beneficial. Maybe do it each week or every 5000 hands or so.

Appears to only be for cash games.

A couple points.... First I agree with you about the sample size issue, It should NOT be counted on, but if I was playing 12/8 and my daily stats show 22/18, it means I am most likely doing better. Using my feelings about how I'm playing and also the numbers do have *some* meaning.

The more important point is that if they are basing their total usefulness on the number (ie 22/18 is better than 12/8) then I should be able to expect that at least they can do the math right.

HEM bugs the s@#t out of me because after usually 20-30 hands I'll show a profit/loss of XX.X4. Sorry, but you only play with nickles, not pennies at the NL50 & NL100 tables. And guess what, my daily HEM profit / loss doesn't match my HEM profit / loss. And I depend on this program to calculate numbers and they can't even add + subtract correctly!

--------------Kitty

Also bugs me when someone says our tech support responds within 24 hours. Well, they did, but all they said was they were looking into it and have never responded after that.

Granted, these are not huge issues and I still depend on HEM every day I play, but as a paying customer I still retain my right to B#$*3. (especially after a bad day at work. )

We weren't ignoring you. I'm not sure if you were expecting that we'd have it all figured out right away, but we have been looking into it. Keep in mind that we do have a series of things we're working on.

The issue with synching clocks depends on several factors. There's the time of the actual server you're playing on, the time difference that you may have adjusted or no adjusted on the site and how it writes to the hand history. Lastly your local time on your system. Leak Buster doesn't access any of the raw hand histories, or this would be a very simple issue. We're taking the data from HM, and so we're working with them on how they are working out the offset times. It will get worked out, but like I said, we have a ton of new features that are going into Leak Buster which right now do have priority.

Thanks for bringing this to our attention though, we do appreciate it.

Thanks for the feedback. Glad you're enjoying it. In all fairness, I'm not the developer. My company, and my idea, but I'm not the developing programmer.

Keep us posted on your progress.

About the workshop: We'll be doing a live interactive workshop about how to use Leak Buster, how to get those most out of it, and talking some poker theory as well. It's Free and available for anyone to attend.

We will post a login link to the workshop in the next couple of days. Owners of Leak Buster will receive an e-mail with an invitation link.

Workshop will start promptly at 3pm PST/ 6pm EST on Dec 13th. It is FREE and open for anyone to attend.

Interesting. Looking forward to it. Are there a limited amount of spots available?

I would really recommend you to join this workshop. This is a very powerful tool if you take the time to go over all the available information.

It's going to be limited to the first 50 people. We'll go through how to get the most out of Leak Buster long term, and talk some poker strategy at the end as time allows.