Beta 23 Released

[Myrddin84]

Oh, and: since beta 23 i get some strange hud failures, somtimes new player at the table dont get the hud even after some hands. (i have "refresh rate" to 1)

I have to admit I experienced similar problems yesterday playing on Party. I started the session without any stat on any player (new tables) and have a minimum 20 hands filter. But even after 50 hands played, the stats never showed up (though I could see the PT3 icon). I stopped / relaunched the HUD and the stats suddenly appeared.

I have to say I was configuring the positions at first. So I often "saved" the layout on one table, then "reset" it on the others (position of the mucked hands). I made this many times. At some point, I think it make the HUD stop refreshing though ...

I'll try to send some log files, but these are tough to reproduce.

[kraada]

If you could send them in we would appreciate it; once we have the log files detailing the problem, we can get the problem fixed.

[WhiteRider]

I had a similar problem with star's 4-max shootout tourneys with beta 22. I dragged the windows to the right places the first time, and saved layout (i backuped before), but the next time the hud was messed up again. And the mucked cards where at the wrong places. I guess 4-max is confusing it somehow?

The 4-max tables aren't recognized as such, and it will be using the 9-seat layout. 4-max tables aren't fully supported at this time, but will be in future.

[WhiteRider]

That made me thinking. Isn't the hud "last x hands" filter working similar to the "player range" filters? If so, they can't make use of the cache either? in other words: is the usage of mulitple player ranges (i have 7-10, 5-7, 3-6 and 2-2)a big performance handicap?

No, the player ranges are different - the cache can look up your stats for each player range and remember it, and the stats will stay the same (apart from new hands being imported and added). With the last X hands, old data needs to be removed which means recalculating the data every hand (as you remove the oldest hand) so you can't cache it.

[WhiteRider]

Oh, and: since beta 23 i get some strange hud failures, somtimes new player at the table dont get the hud even after some hands. (i have "refresh rate" to 1)

I have to admit I experienced similar problems yesterday playing on Party. I started the session without any stat on any player (new tables) and have a minimum 20 hands filter. But even after 50 hands played, the stats never showed up (though I could see the PT3 icon). I stopped / relaunched the HUD and the stats suddenly appeared.

Please check your 'Player Ranges' the lowest range must start at zero, not one, or new players will never update.

[BillyTheBull]

1. Is it recognizing the table as 6-max? PT-icon -> Configure Stats; it tells you the table size in the title bar.
If it's not recognized as 6-max either PT-icon -> Treat As 6-max or enable the 'adjust qualifying tables limits' option on the auto import tab and it should recognize them automatically.

1. I'm not sure if it recognized the 6-max table as such, but I think so. I know that I have the "adjust...." option checked in the auto import tab already. I don't play those very often, but next time I do I'll make a point to see whether or not the HUD recognizes it in the first place, and we'll go from there, I guess.
2. Thanks! I'll try that, and will let you know if I run into any problems.

[merkur33]

No, the player ranges are different - the cache can look up your stats for each player range and remember it, and the stats will stay the same (apart from new hands being imported and added). With the last X hands, old data needs to be removed which means recalculating the data every hand (as you remove the oldest hand) so you can't cache it.

Yes, that sounds totally logical. thanks for the answer anyway.

Oh, and: since beta 23 i get some strange hud failures, somtimes new player at the table dont get the hud even after some hands. (i have "refresh rate" to 1)

Please check your 'Player Ranges' the lowest range must start at zero, not one, or new players will never update.

this i don't get. my lowest player range is from two-handed to two-handed, since one-handed poker doesn't make really sense. zero-handed would be a nice option, though. do you mean maybe "refresh rates"?

[FinnOz]

If that is why the 'last X hands' option slows down the HUD, then I propose the following solution: make the option 'last X hands plus all hands in current session'. This lets you still use the cache, and the stats are just updated for the new hands like the standard HUD, but you're not seeing contamination of the stats by really old data.

[Myrddin84]

this i don't get. my lowest player range is from two-handed to two-handed, since one-handed poker doesn't make really sense. zero-handed would be a nice option, though. do you mean maybe "refresh rates"?

Thanx, I was amazed by my stupidity before reading your post

[js2002]

Im still stupid!
Why isnt it enough when I define 3 to 6 at player range, when there are always min 3 players at a table?