Today Apple released OS X 10.10, aka OS X Yosemite. Poker Copilot works fully on Yosemite. I’ve been using the Yosemite developer preview versions for months to make sure.
However the first time you start Poker Copilot after upgrading to Yosemite, you will see this message:
Click on “More info…” and follow the steps. It is a one-time process that you’ll need just for Poker Copilot but for some other applications also built on Java.
Do note that I hope to release a new update in the next days that will prevent the need to install the “legacy Java SE 6 runtime”.
I’m working on our Windows version of Poker Copilot. We are adding a Windows-only poker network called iPoker. Skins include Titan Bet and bet365. Here in Spain we have limited access to the iPoker network, and so far I’ve been unable to get any hands for Fixed Limit Hold’em, Pot Limit Hold’em, and any variant of Omaha.
Would you like to share your collection of iPoker hands with me? It would be a great help!
Play a single hand of poker with Poker Copilot’s HUD, and you’ll learn that your adversary has a VPiP (Voluntarily put money in pot) value of 0% or 100%. Clearly both values are wrong and yet those two values are the only possibilities after one hand. This is why Poker Copilot makes the values grey until you’ve played 25 hands. After 25 hands, VPiP will have converged to a reasonably accurate number, and we then show it in full colour.
The problem is much worse with a stat that we can only measure in certain situations, such as “Folded Big Blind to Steal Attempt.” On a full ring table, a player is only on the big blind every 9th or 10th hand, and in most of those hands will not be facing a blind steal attempt. You may need to play hundreds of hands against a villain until you have accurate data for “Folded Big Blind to Steal Attempt.”
tl;dr version: convergence is a problem.
In Poker Copilot 5 we are adding a new approach to solving this problem: default values. This means that for a player you’ve never played before, instead of assuming that their VPiP is unknown, we’ll assume it is a preset default, say 20%. So after one hand, instead of seeing 0% or 100%, you’ll see 19% or 23%. Until you have 25 hands of data, we’ll fill in the missing hands with a value of 20%. After each hand, we’ll use the default value less and actual data more.
This will be much better for “Folded Big Blind to Steal Attempt”. Even though I designed and coded most of Poker Copilot, I still find myself looking at this statistic after just a couple of rounds around the table, and using it to make decisions. It is quite likely that the villain had only low hands in the big blind, and folded wisely. Or had great hands and re-raised the blind steal attempt. So I’m using the data incorrectly.
Instead we’ll use a default value of maybe 50%. Only after a significant amount of hands against a player will I now see the correct value. “Significant amount” here means we could measure the statistic 25 times.
“But wait”, you say. “Isn’t that giving me wrong values?” Yes, and no. Yes, the values are wrong, but that’s the nature of statistics – in a dynamic setting they are always partly wrong, but we make them as accurate as we can. And I believe that the default values are less wrong than the current approach.
“I don’t like this. Is it optional?” Of course. In fact, by default this feature will be disabled.
“Do we have to use the default values you choose?” No. You can choose your default value for each statistic. Or none for certain statistics. You can make the default values work for any number of hands, so that after, say, 10 hands, you see the measured values only.
We conceived this feature with the help of a online pro.
For Poker Copilot 5, we’ve create a new deck of cards for the replayer. We’ve paid attention to the details so that they work well in Hold’em and Omaha. They are more legible, and make better use of the the top-left hand quadrant of each card. I hope you like them!
Later this year we’ll release Poker Copilot 5. We have some great things planned for this version. As always, we love to hear customer suggestions.
What would you like to see in Poker Copilot 5? What would you like to see added? or changed? or improved? What must-have stats are missing? Let us know here.
The next major update of Poker Copilot will have much better integration with SharkScope. Here’s one of the SharkScope-enabled features we will be adding: better tournament filters.
If you are a SharkScope subscriber, then you’ll be able to filter tournaments in Poker Copilot on the extra data that SharkScope makes available. For example, you’ll be able to filter by tournament speed, and other tournament formats:
Want to see how you play in Double or Nothing tournaments that are not turbos? You’ll be able to do this.
Today Apple announced that the next update of OS X will be called OS X Yosemite, is available in developer preview already, and will be publicly released later this year.
As soon we can, we’ll make sure that Poker Copilot works without a hitch in OS X Yosemite.
Please note that this is an early access version. This means that the software has known bugs and may be unstable; development continues. It is a chance for you to be part of the development of Austin, by helping us find any issues we’ve overlooked. We need your feedback! Please let us know of any problems you encounter, by emailing support@pokercopilot.com, or by selecting “Report an Issue” from Austin’s Help menu.
At the end of our early access program, we’ll give away five licenses. Each one will go to a randomly picked person who gave us feedback on Austin.
