Yesterday I've installed HM2 trial, because I wanted to try Leak Buster, but the trial version just show that you have leaks, you have to register to really see them, right?
Shouldn't the trail version allow the user to really test the software?
One last thing, I have the HM1 version, for buying LeakBuster I need HM2?

Certain leaks up to step 6 are shown, but to see all yes, you need to register the software. We are adding a new step and expanding the trial a bit, but you'll know if it's something you'll want or not from the trial. Plus you have 14 days to request a refund if it's not for you. If you're using it correctly, it should benefit just about anyone who plays online, no matter your current skill level.

Leak Buster is also integrated into HM1. So if you purchase a license from the HM2 website, it will work for HM1 as well.

Thanks a lot, you explain it all, I'll give it a try then

Edit: In the trial on HM1 I can choose NLx in all the currencies I play, in HM2 it analyse $ or € separately..I'm I doing something wrong?( I prefer that LB adds all the NLx, no mather what currency...)

You're welcome.

So when you analyze ALL, it's not doing all currency (because it should). Now in stake level analysis it will list them separately.

On step seven In the tutorial (3-TPGK...) the guy is using HEM1 I suppose and he has all his stats and limits as we can see and underneath them all the hands. And I got two little boxes.


One with six stats that I can not change. How I am suppose to see my river call efficiency if I have only have 6 stats going on which I cant not change.

Or maybe I am doing something wrong.

How can I see my river call efficiency in this step. That applies to a few other steps.
Thanks

This specific filter it's helpful to have the river call efficiency, but isn't critical since this is looked at during complete analysis in the HM2 version when it's ranking leaks. In HM1 you could load the filter yourself as well, and look at the stats, but HM2 doesn't have that option because a lot of the filters can't be built. We have to custom query them.

In upcoming versions, the hands and more stats will be listed in step 1. It's in the works now, so it will be a lot easier to examine this issues in 1 place. Now if you have a leak in this area, it's important to look at how it's ranking it. If it's critical, then more than anything reviewing your losses for this leak, and also do the line check filters to see what approaches are costing you the most.

If you have a specific question about the leak or need more help, I'm happy to assist.

New Video content added to the no-limit members area today:

- Profitable 4-bet Bluffing
- Turning Made Hands into Bluffs

From step 1 in no-limit, click on members area (bottom right). Videos are downloadable.

How does LeakBuster react from the hands converted from Bovada?

It works perfectly, like any other hand. The only difference that we've noticed is all-in EV can be off because all of the known cards for every opponent are seen. So this calculation will be slightly off because of that. Everything else is the same, and you can do much better and more accurate filtering because you know everyone's cards.

I was just watching your 4 Bet Bluffing video, which was great. But in the beginning around the 4-5 minute mark, i think you make a small error about the combos being counted for AK, shouldn't it be 12 not 9?

Yup, it should. Someone else just pointed this out too. I realized it after I put it up. Not sure why, usually don't make those kinds of mistakes, but I'll have to go back and re-edit it. Thanks for letting me know though.

Is there any ressource Im missing that enables me to have "normal" hm2 filters that are corresponding with the step 7 filters?

No. All the filters are internal in LB HM2. In LB HM1 they were internal and also available to run though HM. We are waiting for HM2 to change a few things with their filters so we can make them for both. Right now, it's just not possible unfortunately.

I'm using LB on HEM2 and I've got a small issue with the screen size. You can see from the screenshot i've posted that certain things are just a little off (the box above the B+ grading, the text on the left for the leak, etc)

Thanks. Yeah, we the latest update we noticed that on some system configs (rare so far), a couple of text boxes are not staying aligned in the HM2 version. We've put it in as an issue. If you see it anywhere else, please let us know.

Do you have any plans for a PLO version of Leakbuster for PT4?

We do, thanks. Right now though we are doing major updates to NL, including new stat updates. I'll post more info here soon, but it's going to be pretty cool.

ETA?

I'll update when I have a better ETA. It will be soon. It's going to have updated stats along with several new stats, new videos, and it will have entirely separate ranges for micro and small/mid stakes now. Before it prioritized leaks based on stakes, but now all ranges will be separate like it is for Limit.

Sounds good.

I'll have an updated ETA this week. We're working on the UI also since I haven't been the biggest fan of it since we went into HM2. We're making more global commands and cleaning it up a lot.

After running an analysis I am showing a sample size of 1062 hands at 6 max .25.50NL, where I have booked 18k hands through Poker Stars/Pokertracker 3. Am I missing something? Is there a way to upload all hands?

Disregard last post, figured it out thanks

Getting error message when running analysis, any info on this is appreciated:

Npgsql.NpgsqlException:
column stats.flg_f_has_position does not exist
Severity: ERROR
Code: 42703
at FGqaSjL1YtFyJB2ffvc.MJc26NL2fUph0n6gxa8.QKy9bOmm9( String )
at R7xLgAXeojTOBaeum0W.N78cjBXSaJx9C6gtl2V.R9XypSKiY( String , Stake , Boolean , Boolean , Boolean , String , Boolean , DateTime , DateTime , Int32 )

So I guess this is Leak Buster for Poker Tracker and you are using it on PT3 correct? Yes, this is a known recent issues. PT3 removed this table that's getting the error. It's only in step 8. You can run an analysis on each step individually. We will be fixing this in the next release.