I couldn't agree more. I think what's most disappointing is Josh pretty much said HEM's Roy was in over his head and would probably not be prepared when HEM was released. Josh said he knew what to expect and they wouldn't have the same problems as HEM. Now, HEM did have a lot of problems when it was released but PT3 seems to be having just as many.

Josh also accused Roy of releasing HEM commercially just because PT3 was about to go BETA. Is anyone else starting to wonder if PT3 was released before it was ready so it could beat PokerEV???

for some reason, my bb/100 is half of what it should be. how do i fix this?

In PT2 you probably had it set to big blinds/100, PT3 uses big bets/100. I'm not sure if you can currently change it. Most people talk about it in terms of big bets anyways, even though it makes it more confusing, imo.

Anybody know if you can still pay for PT3 using Stars transfers? I saw this option on the site 3 days ago, but I can't seem to find it anymore...

https://www.pokertracker.com/support/?cat_id=39

thx. upgrading to beta 12 worked.

Always wait for the x.1 version, IMO.

1.) please add ability to export lots of hands!
2.) when is a poker ev addon (?) going to be released for pt3?

keep up the good work

Hi guys!

I really guess its to hard to read ALL the post here to find an answer to my simple question

.... Should i buy PT3 ?! .....

I have PT2+Hud and i am pretty satisfied with it!
It works good for me and i`ve never had any trouble with it, so, is PT3 a MUST HAVE?!

(1) Database --> Database Management, click on your database, click Export. It exports all of the hands in your datagbase.

(2) Unfortunately we can't give a solid ETA at this point. Hopefully soon, though first we need to finish solving the various stability issues in the HUD.

There are a lot of extra statistics available in PT3, including the ability to write your own. (Last week I wrote "Average Percentage of the Pot Bet on the Flop", which you can download from the Statistics Repository, for example.)

Since the PT3 still has a very lengthy free trial, you can always try it and see if it suits your needs. There are some ongoing HUD issues that we are working as hard as we can to resolve. For some people, the HUD is not stable yet. We intend to fix this ASAP. But since you can install PT3 and PT2 side by side without a problem, there's no reason not to try the trial. (Note: If you have postgres installed for your PT2, you can just download the version of PokerTracker 3 Without PostgreSQL.)

any possible eta on a new version or new beta or something???

will we have to pay again for updates if i go ahead and buy PT3 now?

Why don't you guys have a publicly posted "schedule", so people know what fixes and additions have priority?

Unfortunately not at this time. Hopefully, soon, but I don't have any more information than that.

If you purchase PT3 now you will not need to pay for any update to the PokerTracker 3 line (which we expect to be under development for the next several years).

The priority at the moment is HUD stability and any remaining performance and import issues. Once those are resolved, we hope to get back to implementing new features. I'll suggest a more public list of what we're doing in order, but it's unlikely we'll see one until we're past the next few releases. This fix has taken far longer than originally expected and once it's out and we're back to adding new features in I expect we'll be releasing updates much more often.

So there is no way to change this? Big bets are meaningless to me, I'm NL player.

A big bet is 2x the big blind. You could create the same statistics with big blinds using the custom statistics functions, however at the moment there is no easy switch to flip to change it. But to figure out how many big blinds your'e winning, just multiply by 2.

I don't think the option is there yet, but is it really that hard to divide by 2?

Not to be to nitpicky, but he actually wants to multiply. The big bets are twice as big as the big blinds. So if he is winning 3 big bets per 100 hands he's winning 6 (3 * 2) big blinds per 100 hands.

Personally I think it's easier to multiply by 2 than divide by 2, so it works out?

HUD only shows up on about half my tables (5/10) on both versions of PT3. Running vista w/ postgres. Halp?

Thanks for keeping up with this thread, Kraada.

You don't happen to have any general idea when Build 3 will be released, do you? I won't hold you to it.

I do the best that I can, I'm glad it's appreciated.

I wish I had a better ETA on Build 3 for you, I really do. I know Josh is working really hard on getting everything fixed. Last I heard he was starting to go through submitted tickets to see if he'd fixed everything. With at least 100 of those I'm not sure how long it will take (and of course if he finds a problem, then it takes more time). So "hopefully, soon" is about the best I can do for you.

I can't import anymore

as you know, my import speeds are painstakingly slow. I let it run all night (at a blazing fast 5h/sec )

and it seems that PT3 froze about 4 hrs into it. task manager never said it wasn't responding or anything, but nothing was importing for the last 8hrs or so
so I have to kill the process, and now I cannot import anything...
I get an error on every single hand now

here's the error:
Unable to import hand. Reason: unable to execute query: COPY holdem_hand_summary FROM STDIN;; Reason: Fatel Error (ERROR: value "86222896" is out of range for type smallint CONTEXT: COPY holdem_hand_summary, line 1, column id_limit: "86222896")


the error messages are the exact same as that one, but the 8 digit number changes on each error...

please advise

btw. this really sucks when both versions are pretty much unusable for me, and it takes me DAYS, literally DAYS to import a db that's less then 1 million hands...

I really love PT, but this frustration is about to convert me to holdem manager very shortly

Orentha,

I've gone through your hands and found a few that consistently cause problems. Looking at them, I honestly don't know why they cause things to go as slowly as they do, but it's pretty clearly them (if you change the hand # and copy the same hand into a text file 500 times it imports as 500 hands). I've forwarded these hands to Josh so that he can look at them and try and figure out what is causing the slowdown. Unfortunately I can't really do more at this point.

I understand your frustration, and I want to assure you we're working on the problem. You get that same message when importing any hands at all? If so, could you PM me a few hands that do this so that I can see whether it's the hands or your setup?

Why would you want to pay for a very flawed program? Did you read any of the hundreds of complaints?