Quote:
Originally Posted by ranka
Sorry if this question is already asked but everytime if I filter my stats then tracker start updating the player list first. After the player list is loaded and populated then it start loading my requested stats.
The problem is, if you are filtering huge data then you have tons of player and it take 4-5 minutes to load and populate player list and its annoying.
This will be changed to load the player you last had active at the same time as the player list, thus saving you from having to wait until the player list is completely populated.
Quote:
Originally Posted by ICMoney
Re: For the filters - can I search by when playerX raises flop and goes to showdown, when he called pfr, etc?
I wasn't think about hands I've played against someone.
I was talking about looking through my FT datamined hands and picking up patterns.
Yes, you can filter by all this criteria. Click the Filters button, choose what you want to filter by and apply.
Quote:
Originally Posted by Melchiades
I will if/when I switch to PT3. For the time being I'm still using PT2/PAHud on one computer and Holdem Manager + HUD on another one. I'm just importing to PT3 to test the program, if the HUD/additional features lives up to the speed and feel of the program so far I'm pretty sure I'll end up with PT3 everywhere. It's fast.
You can use PT3's auto-import alongside PT2 or any other software, just make sure you don't have PT3 moving processed files.
Quote:
Originally Posted by WoolyHat
How come duplicates kill the import speed so bad?
Import speed overall has been great, btw (300 hands/s ). I was just curious as the performance hit seems counter-intuitive to a technical moran like me.
When PT3 encounters a duplicate, it checks the data in the duplicate hand to what you currently have in the database. If the new hand has more info than the old one, the old data is replaced. This way, if you have an observed hand in your database, and you import a new version with more hole cards in it, the new hand will update the old information. It's this checking that causes the slowdowns.