[Closed] PT3 HUD Table stats different from pop up stats

What version are you running and have your rebuilt your cache since you noticed the issue?

PokerTracker 3 - Holdem Version: 3.06.2
Windows XP

The first thing I did when I noticed the problem was a Housekeeping including Reindex, and Rebuild Cache.

In that case I think my best suggestion is to send screenshots of the issue. It sounds like a straight up bug to me so support is probably your only hope.

yep thats what I did, sending them screenshot in the first place and then
Pokertracker.log
PokertrackerHUD.log
newest 3 or 4 PostgreSQL logs

That's after this that I have been asked to change the name of the "Layouts.pt3" file.

Just wanted to know if it happened to one of you to speed up the fixing process because my HUD becomes useless with all over the place values...:(

Are you using data mined hands? I know one of the iPoker sellers was giving out some bad hand histories in the past.

Edit: I found the thread.

http://www.pokertracker.com/forums/viewtopic.php?f=16&t=29336&p=142478&hilit=3bet+ipoker#p142478

Hi tokyoaces,

Thanks for the link. It looks like this is the problem indeed. Here is the latest answer I got from the support:

"I suspect the problem is caused by importing purchased iPoker hands which have very large stack sizes in the hand histories. Players are reported as having 10000000 stacks, which PT3 did not expect as it is bigger than can reasonably be expected.
PT3 has been updated to handle these in the 3.07.x Beta line but 3.06.2 does not import them correctly.

You will need to update to v3.07.3 if you want to import these hands correctly."

So I will do this tonight and see how it goes.
Will keep you updated

Yay! My incessant forum trolling is useful.

Sounds like a database rebuild in your future. Good luck with that. Did they warn you about the "use Rebuild Cache not Update Cache" with large imports thing?

Originally posted by tokyoaces
Yay! My incessant forum trolling is useful.

Sounds like a database rebuild in your future. Good luck with that. Did they warn you about the "use Rebuild Cache not Update Cache" with large imports thing?

They did warn me about the rebuild cache.
Looks like the update to version 3.07.3 as solved the issue.

Thanks Tokyoaces for the help.