by techvoodoo » Mon Feb 01, 2010 11:28 am
hey i thought i'd add some more info about my problem with the rush hud and the stats lagging behind the current hand in progress.
First my PC specs are:
3.2ghz core 2 duo
4gb ram
160gb SATA 7200 hdd
winxp
My database has about 50,000 hands in it and all housekeeping has been done. My HDD is defragmented and has 95gb of free space (it's not 99% full and running slow). All drivers and OS updates are current.
The exact issue is that the HUD wants to update for every single hand played, not the current hand you are on. So for example you are at the table and mashing quick fold 8 times and find yourself in the big blind the 9th hand the HUD wants to display hand 1-8 before it will display the 9th hand, and it takes around 2 seconds (maybe slightly more) to update and display each of those HUD stats. That's 16 seconds minimum to get through all those hands but I just mashed my way through those 8 hands in about 10 seconds.
At that point it would be more useful to not show the hud at all unless I ask to see it. not that this is the solution but if I could click a button when I've decided to play a hand that says show hud now and brings up the hud for my current and, that is much more useful than waiting for the HUD to show my stats from 3 hands ago, than 2 hands ago, then 1 hand ago, then the current hand (opps you just timed out because you waited for stats on that UTG raiser to appear).
I don't feel like this is necessarily an issue with poker tracker or the HUD but an issue with the performance of my PC being able to pull the data from the DB, and draw the hud on the screen as fast as I can play (or not play and fold in this case). I normally 16 table so I can blow through hands quick folding at RUSH. Maybe it is an issue with PT3, but only that it's trying to show data on players for hands that were basicly never played which isn't useful in this type of game.
Not sure how to fix it, I don't know if you can do any performance tuning to make the hud more responsive, but it doesn't feel like what you would call a "bug" because it's working correctly, just not fast enough.