Player stats reset randomly during tournament

[zdarma]

For the past few days, I've noticed that the stats for all players (myself included) reset randomly during the tournament to 1. I've tried stopping the import and restarting, but the stats are still reset to 1 or whatever hand number I did the reset at. This is particularly annoying as I multi-table and rely on those stats to see how people are playing. However, if I already have 40 hands imported for a player before the start of a tournament, those 40 hands are there when the stats reset. I was in a tournament and went from having 37 hands imported for all players and all of a sudden the number of hands showing for all the stats was 1.

I do not have this problem with cash tables.

I play on PokerStars and I am running PokerTracker version 3.12.1.

Addendum
I was paying close attention to one table and noticed the reset happen when we lost our first player. All player stats went from 4 to 1.

[zdarma]

Just an additional bit of information, the stats did not reset when we lost our 2nd or 3rd player. I think it only happens when the first player is eliminated.

[kraada]

This can happen depending on what you have the Player Ranges set at in the Configure --> Configure Hud --> Hud Options tab. The Player Ranges tell the HUD to show stats from tables with only similar sizes - so if you set those up for example like 9 to 9 and 7 to 8 then at 9 handed play you'd see 9 handed stats and 7 to 8 handed you'd see 7 to 8 handed stats - which would show you a reset after a player is eliminated. The data is still in the database, just not treated as relevant based on the settings you have (and if you saw them again at a 9 handed table those hands would be taken into account).

[zdarma]

I'd already thought that might be the problem; but when I checked I had my player ranges as 2-9. I have never changed those settings.

[WhiteRider]

What type of tournament are you playing?
If you start 10 handed (e.g. in a DON) that setting would explain the behaviour. Try setting it to 2-10, or removing the setting, which is the same effect.

[zdarma]

I am playing single table SnG, both 9 and 10 players. On PS it is the tournie types 50/50, Knockout, and normal SnG where the top 3 are paid.

I have vaccumed, analyzed, and updated the cache of my database. I removed the min./max. player ranges. I then ran the following table settings to test what happens.

Playing only at 1 tournament table, lost a player, nothing happened to the hand count (9 players)

Playing 2 tournies (both 10 players), lost 1 player at one of the tables and that table the number of hands reset to 1, the other table stayed at the right numbers. When the other table eventually lost a player, nothing happened, no other table was running at the time.

Playing 1 tournie table (9 players) and 1 cash game table, the tournie table lost a player and the hands reset to 1.

Playing 1 tournie table (10 players) and 1 tournie table (9 players), lost a player at the 9 player tournie and the hands reset to 1, a few minutes later lost a player at the 10 player tournie and nothing happened to the hand count for that table.

From what little I can figure out, if I have more than one table running with a tournament, as soon as a player is lost in one of the tournie tables, that table resets its hands to 1. I have stopped the import and re-started the imports after something like this happens, but it still only shows 1 hand or however many hands were imported since the reset to 1 and my stopping/starting of the of the imports, rather than the total number of hands I should have for the players.

[kraada]

Please try updating to our latest Beta version (3.13.7) from our download page and then restart PT3 using the Logging Enabled link on your start menu. Please reproduce this problem then and report it - your log will help us considerably in figuring out what is going on here.

[zdarma]

I think I fixed the problem, but I'm not sure why.
I exported my DB, uninstalled PT and then re-installed (version 3.13.7), re-imported my DB, vaccumed, analyzed, and updated the cache of my database. I then re-ran the tests I mentioned earlier and everything seems to be working fine. I'm not sure why, but I'm happy.

If the problem occurs again, I will be sure to enable logging and send you a log. Thanks for your help anyways.

[kraada]

Thanks for following up - let us know if it happens again.