Hero HUD not showing all hands in a DB
Posted: Tue Jan 09, 2024 6:17 pm
Hi,
Today I tried to see my HUD in a legacy DB (1 year old) when I played lower stakes. The DB has 107k hands from January till March 2023.
When I load that DB and run reports, overviews, leak Analysis, etc everything works fine, It is based on the 107k hands stored in that DB.
But when I try to see my HUD by opening a hand in the reviewer, I select "Hero Lifetime Stats" and it only shows 3.5K hands (when not selecting Lifetime it shows 50, so at least is doing something)
In my default DB, the one I'm using to play regularly these days, selecting Lifetime Stats in the reviewer works fine, it shows the actual total number of hands in the DB.
Any ideas?
PS: Currently using v4.17.11 for Mac (Opened a ticket for v4.17.12 and v4.17.12.1 for HUDs not working properly in PS Zoom tables). The legacy DB was created and populated using an older version of the SW (the one that was last at that time of the year) and during 2023 one of the PT SW updates required an upgrade in the DB SW as well (higher Postgress version?). Just in case the problem is there...
Today I tried to see my HUD in a legacy DB (1 year old) when I played lower stakes. The DB has 107k hands from January till March 2023.
When I load that DB and run reports, overviews, leak Analysis, etc everything works fine, It is based on the 107k hands stored in that DB.
But when I try to see my HUD by opening a hand in the reviewer, I select "Hero Lifetime Stats" and it only shows 3.5K hands (when not selecting Lifetime it shows 50, so at least is doing something)
In my default DB, the one I'm using to play regularly these days, selecting Lifetime Stats in the reviewer works fine, it shows the actual total number of hands in the DB.
Any ideas?
PS: Currently using v4.17.11 for Mac (Opened a ticket for v4.17.12 and v4.17.12.1 for HUDs not working properly in PS Zoom tables). The legacy DB was created and populated using an older version of the SW (the one that was last at that time of the year) and during 2023 one of the PT SW updates required an upgrade in the DB SW as well (higher Postgress version?). Just in case the problem is there...