Are you using Build 2? If so, please download Beta 17 available further down on our Download Page.

You don't have to reimport your hands, but if you've been suffering from stat inaccuracies in Build 2 and want to correct them, then yes, a reimport would be needed.

What do you mean by tagging HH's? To tag hands for review later? If so, these two features haven't made it yet, but both are planned. Please keep an eye on the Development Timeline for updates.

I can see the reasons for that when posting to a public forum or whatnot, but from pt support? Do you really think they'll use your hhs to find your leaks and hunt you down at the tables or something?

It just seems a tad paranoid.

You are not the first one to point that out, but the first that didn't fell for their argumentation. Sad that it took 9 months and a very quick and smart thinker to not only say that something's wrong but also why.

These are the arguments that muted everyone except you!

W$SD is Won Showdown? Isn't it Won $ At Showdown?

And you are the first who doesn't agree!

Developers you could either rename the statistic so it is consistent with what it shows or calculate it properly!

Seriously.. am I the only one on vista and beta 16/17 both lock up the HUD when you close a table on stars. Happens on both laptop and desktop. Every time! I have to goto to taskmanager and close the HUD process.

No, this is a known issue, and is being worked on.

I've got Vista. HUD locked up when I switched graph types on the Graph tab.

I'm using Vista, and the HUD does this to me occasionally on FTP. I don't think that this issue is specific to Stars.

how come the import speed constantly goes down? a cpl of days ago when i was doing manual import from directories it would have 100 hands/sec, now its down to 22 per sec

is this known and worked on? i dont even try to use the HUD anymore

I have a similar problem...

Ok thank you..

Problem with HUD at Ongame. It is not possible to move stats on the hud, I think reason for this is the right click "quickmenu" which interferes with the PT3 rightclick+drag action. Is there any workaround for this? HUD is practically unusable at Ongame because of this.

Edit: On a new try I could move the boxes on first window but Save-function was not available...

Could you please enable logging and reproduce this error then attach the C:\Program Files\PokerTracker 3\PokerTracker.log and C:\Program Files\PokerTracker 3\PokerTrackerHud.log to a support ticket? It would help us in figuring out exactly what is going on here for you.

If you could please submit logs as well we would appreciate it.

Importing speeds taking longer into already created databases is a known issue that we are going to look into. I believe the reason for the decrease in speeds involves checking to see whether or not sessions have existed previously or some such, though I could be wrong about that. In any event, once we have our other known bugs ironed out we will take a deeper look into this issue to try and speed things up.

This is a known issue that should be resolved in the next Beta release.

Hi,

please add player moves to the HUD like in Poker Office. It's an essential feature for multi tabling players, and it really helps a lot while playing 9 tables and more!

I don't understand why a PT official stated it will not be part of PT3 (in the official forums).

I am currently using PT3 only for reviewing sessions, because it's not stable at all (HUD freezes, program crashes when I alter the HUD options while playing etc., using it on Vista 64).

What I really like about PT3 is the speed of importing hands, importing several thousand HHs with Poker Office is really painful.

Just checking to see if there's been any progress on this.

i play on vista. pt3 locks up my pokerstars tables everytime I try to close pt3 when im on tables. I still cannot play more than 10 without hud lag any suggestions?

Any ETA on the HUD freeze/hang problem? I cant use Betas 16/17 because of it, and Beta 15 cant import stars hands, so I'm at a complete standstill, and have been for nearly 3 weeks now....

The freezing/crashing upon PT3 closing/stopping of auto-import should be fixed for the next release.

With regards to the lag: are you using Beta 17 and have you recently cached your database? If so, please reproduce the lag with logging enabled and submit the logs to the support system. The issue where some custom stats are not being cached properly has also been fixed for the next release.

We are working on fixing these issues as quickly as possible, and hopefully they will be completely resolved in the next release.

It was decided that giving information about the current hand in play during the hand was too close to creating botlike behavior, especially given the sheer power of the PT3 custom statistics interface. I don't believe our stance on this issue will be changing anytime soon.

To my knowledge there hasn't been progress on that, however there has been progress on other issues and auto-rate functionality will be available in the next beta . . .

Is there any news on when Sklanksy bucks are going to be implemented?

I know this has been asked before but the last post I can find on this is from June.

Any update?

Thanks.

No, sorry - no update on this.
Please keep an eye on the Development Timeline for latest updates.

When will the HUD have the PAH feature allowing us to choose which tables to have the HUD display on?

Rubbish, the same information is available in table chat window

Sorry, there is no ETA for this at the moment, although it is planned.
Please see the Development Timeline for latest updates.

Thank you.

I've been a long time PT user, upgraded to PT3 when it came out, and not had any problems, apart from the odd niggle.

Today, PT3 has started "hiding". I load it up, but it doesn't show in system tray or desktop. There's no splash screen displayed (had it hang on there a few times, but this problem is different).

When I try to load it again, it says it's already running, and this is confirmed by task manager - showing under processes but not applications. Any thoughts as to why?

What version of PT3 are you running?
If you kill the process and re-run it, does it then run OK?