Page 1 of 1

Incorrect Pot Odds Bug?

PostPosted: Sat Mar 22, 2008 5:36 pm
by smizmiatch
It appears that my pot odds showed up incorrectly in PokerTracker's "Playback - Pot Odds" window:

Please click [urlxpg]http://bp0.blogger.com/_M8hybLanwS8/R-V5G2yaPMI/AAAAAAAAAFc/r9arq334qag/s1600-h/PTpotodds.JPG[/urlxpg] to view the problem (I couldn't get the image to embed properly).

PokerTracker shows my pot odds are $950:$535, which is inaccurate. In reality, my pot odds in this hand are $1,485:$535.

Is this a bug, or am I confused? Thanks.

Re: Incorrect Pot Odds Bug?

PostPosted: Sat Mar 22, 2008 6:30 pm
by ptrack mike
It is correct because you only have 535 to call left in your stack. This makes the actual pot size 950 since your opponent will be getting chips back if you call.

Re: Incorrect Pot Odds Bug?

PostPosted: Sat Mar 22, 2008 7:35 pm
by smizmiatch
I still don't think it's right.

Although my opponent will be getting chips back, I have to call $535 to win $1,485 ($350 in pot + my $300 bet + $300 call + $535 on top). The pot size is only $950 after my opponent calls my $300 bet. The pot size is $1,485 once you count his all-in raise.

Please let me know if I'm misunderstanding. Thanks again.

Re: Incorrect Pot Odds Bug?

PostPosted: Sat Mar 22, 2008 9:53 pm
by ptrack mike
Actually I think we both might be calculating it wrong. Please email me (or post) the text of this hand so I can see what is happening.

Re: Incorrect Pot Odds Bug?

PostPosted: Sat Mar 22, 2008 10:08 pm
by smizmiatch
FullTiltPoker Game #5685341344: Table Melic (heads up) - $5/$10 - No Limit Hold'em - 13:47:56 ET - 2008/03/18
Seat 1: Monster Kill ($1,396.75)
Seat 2: smizmiatch ($1,010)
Monster Kill posts the small blind of $5
smizmiatch posts the big blind of $10
The button is in seat #1
*** HOLE CARDS ***
Dealt to smizmiatch [4s 7s]
Monster Kill raises to $30
smizmiatch calls $20
*** FLOP *** [2s 8s 4d]
smizmiatch checks
Monster Kill bets $45
smizmiatch raises to $145
Monster Kill has 15 seconds left to act
Monster Kill calls $100
*** TURN *** [2s 8s 4d] [Th]
smizmiatch has 15 seconds left to act
smizmiatch bets $300
Monster Kill raises to $1,221.75, and is all in
smizmiatch has 15 seconds left to act
smizmiatch has requested TIME
smizmiatch calls $535, and is all in
Monster Kill shows [Qh 9c]
smizmiatch shows [4s 7s]
Uncalled bet of $386.75 returned to Monster Kill
*** RIVER *** [2s 8s 4d Th] [Qs]
Monster Kill shows a pair of Queens
smizmiatch shows a flush, Queen high
smizmiatch wins the pot ($2,019.50) with a flush, Queen high
*** SUMMARY ***
Total pot $2,020 | Rake $0.50
Board: [2s 8s 4d Th Qs]
Seat 1: Monster Kill (small blind) showed [Qh 9c] and lost with a pair of Queens
Seat 2: smizmiatch (big blind) showed [4s 7s] and won ($2,019.50) with a flush, Queen high

Re: Incorrect Pot Odds Bug?

PostPosted: Sun Mar 23, 2008 8:26 am
by ptrack mike
I knew this problem looked familiar. We made a change for this in a recent patch. See the second link on this page, v2.17.01g.
http://www.pokertracker3.com/products/PTH/download.php

After installing it you will see that the pot size becomes $1185.00 in this situation. As I look at it though it is not taking into account your initial $300 bet, and I think it might need to, but I need to see if there was a reason for this. If it is a problem we'll fix it for an upcoming patch.

Re: Incorrect Pot Odds Bug?

PostPosted: Mon Mar 24, 2008 3:01 am
by smizmiatch
Right, something is definitely wrong.
After installing the update, the pot size becomes $1185.00 as you said it would, but that is not correct.
The problem gets worse if you check the "Show odds to complete on turn" button. Now I'm getting all kinds of strange numbers.
In fact, it's even more broken now than it was before I installed the 2.17.01g patch:
[url1w4]http://bp3.blogger.com/_M8hybLanwS8/R-dREGyaPNI/AAAAAAAAAFk/LNy4u0Y5r70/s1600-h/PTpotodds1.JPG[/url1w4]
[url1w4]http://bp3.blogger.com/_M8hybLanwS8/R-dRYGyaPOI/AAAAAAAAAFs/_vdeta3Ylr0/s1600-h/PTpotodds2.JPG[/url1w4]

Re: Incorrect Pot Odds Bug?

PostPosted: Mon Mar 24, 2008 4:22 pm
by ptrack mike
Yes, there is definitely something wrong in all-in situations like this one. I am working on a fix for it.