I'd even pay $20 to Pokerstars for this feature. I mean, it's not even integrated into any desktop PC software (i.e. PokerStove, Equilab etc.) I know of - which is a shame - and it's just soo time saving and useful.

Rj,
Can the stats feature be used just like Flopzilla? For example, does the "Topcard" stat mean top pair?

The app's Deal-To-Flop feature (and flop texture analysis) is just like Flopzilla in general, but this one stat in particular is different than the "TopPair" stat. The full name of this stat in the app is "Hit Board's Top Card" and I worded it exactly as it means in the app. It's more general than TopPair, some examples:

1) For AK: If the flop is K32 then this case is included in the stat (the TopPair case).
2) For AK: If the flop is KK2 then AK has hit the board's top card (K) so this case is included in the stat.
3) For QQ: If the flop is Q32 then QQ has hit the board's top card so this case is included in the stat. So you can use this stat to see how often a pocket pair will flop top set.

The bulk of this stat's meaning is TopPair, but this stat also includes TopTrips or TopSet or even quads. The latter cases are low prob. and usually won't contribute much of a %age to the stat.

At least several people have suggested that I add some more stats like TopPair, MiddlePair, BottomPair, etc. and it's on my to-do list but I haven't gotten there yet. Just a note, that this app's first goal is 10 player fully general hand ranges equity calc like PokerStove (feature 1a). Deal-To-Flop and flop texture analysis are more like feature 1b. I guess if I take feature 1b to the max this will truly be a PokerStove + FlopZilla app, but that's pretty ambitious for this mobile app, so I won't make any promises : ).

Thanks for the quick reply !

I just bought an ipad mini, ( i already have PCruncher on my itouch ) , is there any difference on the PCruncher for iPad other than the screen size? I have no problem paying for the ipad version, just wondering about any different/added features?
Thanks

For the millionth time: PLO please.

I would gladly pay for another app.

:-)

There are no differences wrt the stats and calculation/analysis features. The only differences are UI and layout improvements like:
* Use full iPad screen, all views laid out flat next to each other.
* Rotate to both portrait and landscape orientation.
* Small additional UI touches like larger cards and assign-card keypad, histogram bars for stats, view all stats together (no scrolling), tap player's Equity stat to fold/unfold, etc.

Basically, no calc engine differences, just UI/layout differences.
Thanks in advance for buying both versions.

Hey.
Thanks for being a user and supporter of the app for years : ).
Yeah PLO has been on my long term to-do for a long time. I've postponed it thinking that the market for PLO would only be a fraction of Hold'em, so I've concentrated instead on improving the current apps further. But yeah a PokerCruncher-Omaha would round out the app set well.

I'll look into it but won't make any promises. Maybe one of these days (months, years) ..

Hello!

I am relearning/reeducating myself at poker and have had your app on my phone for a very long time

But I've misused it (only checked it for reference purposes)

After actually reading your tutorials it has helped me understand much more and better yet - how to apply it

It's a fantastic app- I only wish I had utilized it earlier

Great to hear! Thanks for being a long time user of the app.
Yes it's a 50/50 thing, having the app (tool) is good, but knowing how to use/apply the tool to improve your thinking process is the other 50%. Glad I wrote the tutorial (years ago now), and added a link to it in the app. I've added some more sections to it recently e.g. the section on hand range weighting/combinations.

If you're up for it, pls. do consider writing an App Store review/rating for the app. Reviews and word of mouth help small indie developers especially a lot. Thank you. -RJ

Will do

If I may add - I noticed a bit of an inconsistency with my app and the tutorial

- when I ran the Hit Stats portion of the app I noticed that the stat you mentioned "pair plus overpair" is not showing on my app - thus my app is not showing the same as your screenshot. Perhaps this is due to an update comparison with the age of the screenshot?

The tutorial doesn't mention a "pair plus overpair" stat (this is redundant because an overpair means you start with a pair). The tutorial says:

=====
... when this range hits OnePair on this 8s7s2d flop, it will have an OverPair on the flop, as also indicated by the 32% PocketPairAndNoOverCard stat.
=====

You're right that there's a stat naming inconsistency because the screenshot is old. The "PocketPairAndNoOverCard" stat has been changed to the more natural terminology/meaning "OverPair". Thanks for reading the tutorial carefully and noticing, I'll update the screenshots in the near future.

Yes sorry - that was what I meant

I'm glad though that you understood wgat I was talking about

Thanks for clarifying

Loving the app ! I'm having a little problem using P cruncher on my iPad . When using the "Deal to flop" feature to look at stats, I'm having to constantly relaunch the app because the second two rows of info in the stats box have no percentage results, just dotted lines? Should I re download the app? Will I get charged again?
Thanks

Or is it because I don't have a hand selected!?

You guessed it right, in the iPad version tap on a player to select the player and then the Stats view will show stats for that player. Currently you must have a board card selected, which means show stats for the winning hand, and those extra two columns of stats (draws and combination draws) aren't calc'ed for the winning hand.

The reason an app restart "fixed" things for you is that on restart Player1 is selected, not a board card.

Hope this explains it; thanks for good feedback on the app.

Ok now the app/I have a better answer for this. An update V.6.4.1 has gone live (iPhone version so far, updates for other versions to come) with some additional flop stats: TopPair, MiddlePair, BottomPair. Also a couple of others: TwoCardBackdoorFlushDraw, Pair&OpenEndStraightFlushDraw. This is in addition to the already existing couple of dozen flop stats.

Example pic below. Note that to have e.g. TopPair, the player's cards must be used in hitting the board. That is if you have AK and the flop is JJ2, you don't have TopPair (even though you've made OnePair).

Thanks for suggestions/questions like this one; helps keep the app on an improving path.

You da man! Thanks !
However I don't see the apple update yet, prolly be there soon.........

The update went live late last night, but can take up to 24 hours to propagate around to everyone.

This update was for the iPhone version of the app. The updates for the iPad and Mac versions will happen in the coming weeks. Thanks for using the app and for suggestions.

Yes, got the update for my iTouch, thanks again !

Will you release a Windows version?

It's on my long term to-do list, but no plans to start it yet. One reason is there aren't good, high visibility app stores as on iOS, Mac, Android to make app discovery/purchase/delivery easy. Another reason is, I'm just not that big a fan of Windows from a coding/dev perspective : ).

But then again I had said no to Android for a long time and then I did make an Android version.

Hi,
Just started using PockerCruncher 6.4.1 on the an Imac 10.9.1 and Im having trouble importing a hand history from PokerTracker 4.

I copy my HH text from PT4 -
I go to PC and go 'File'-'Import Scenario'

And past the text into the dialogue box, replacing the old default text that was there as instructed.

Hit 'Import'

And I get an Errror message: Import Scenario / Couldnt find any players.
Heres my text as I pasted it in -
Any help would be great, Thanks in advance.

PokerStars Hand #109864475970: Tournament #846607591, $1.44+$0.06 USD Hold'em No Limit - Match Round I, Level III (20/40) - 2014/01/09 15:18:13 ET
Table '846607591 1' 2-max Seat #1 is the button
Seat 1: TheCleaner01 (440 in chips)
Seat 2: oleso88 (560 in chips)
TheCleaner01: posts small blind 20
oleso88: posts big blind 40
*** HOLE CARDS ***
Dealt to TheCleaner01 [6d 9d]
TheCleaner01: raises 40 to 80
oleso88: calls 40
*** FLOP *** [Td 4c 3d]
oleso88: checks
TheCleaner01: bets 80
oleso88: raises 400 to 480 and is all-in
TheCleaner01: calls 280 and is all-in
Uncalled bet (120) returned to oleso88
*** TURN *** [Td 4c 3d] [Qc]
*** RIVER *** [Td 4c 3d Qc] [Ts]
*** SHOW DOWN ***
oleso88: shows [Qs 4h] (two pair, Queens and Tens)
TheCleaner01: shows [6d 9d] (a pair of Tens)
oleso88 collected 880 from pot
TheCleaner01 finished the tournament in 2nd place
oleso88 wins the tournament and receives $2.88 - congratulations!
*** SUMMARY ***
Total pot 880 | Rake 0
Board [Td 4c 3d Qc Ts]
Seat 1: TheCleaner01 (button) (small blind) showed [6d 9d] and lost with a pair of Tens
Seat 2: oleso88 (big blind) showed [Qs 4h] and won (880) with two pair, Queens and Tens

Hello,

>>> Im having trouble importing a hand history from PokerTracker 4.

Thanks for buying the app.
This is as expected currently. The ImportScenario feature only imports scenarios that are in PokerCruncher text syntax. The import feature is meant to allow sharing scenarios with friends (who also have PokerCruncher), or importing PokerCruncher scenarios people have posted on forums, etc. One reason I chose the word "scenario" is because it's different than "hand" e.g. a hand from a hand history program. But sorry for the confusion on this feature, I see now that for a feature called "import" (via text), the app should be clear in the instructions as to what kind of text syntax can be imported.

I see a feature request here - import hands in PokerTracker syntax. One reason I didn't support other syntaxes is that as soon as one non-PokerCruncher syntax is supported, it becomes an open-ended feature and I'll probably have to support many other syntaxes or people won't be fully happy. E.g. PokerStove syntax, hand history programs' syntaxes, online poker websites' syntaxes, etc. I wanted to keep things clean and self contained so decided just to support the app's own syntax.

Is my decision reasonable, or do you think it's time for the app to start supporting other syntaxes? Which one (or two or three) other syntaxes are at the top of the list?
Cringing a little about the open endedness of this feature if I decide to do it : ).

Hey RJ Thanks for the answer.
Understand your approach, maybe just make it clear in the menu that, yes only .PRC formats are allowed.
Yes, it would make it quicker and easier to analyse a situation by copy paste text from PT4 and HEM, and I understand you reluctance to open up to an open ended system, but as a developer of a great tool like yourself, I think you owe it to your growing future market, current customers and to yourself to make the best tool to your abilities and to push your limits.
Only can get better.

Again thanks for the prompt reply.
TC.

>>> I think you owe it to your growing future market, current customers and to yourself to make the best tool to your abilities and to push your limits.

Yes it's my goal to make the best tool that I can. I've been improving all the versions of this program for 5+ years now and it's gotten significantly better; this thread is one documentation of the improvement. I hope my reputation on this doesn't rest solely on if I implement your import-syntaxes feature suggestion or not!

In product design 'more' isn't always better. If this app supports say several other programs' hand syntaxes, then a dependency / link is created on those other programs in a small way. E.g. if those other programs change their hand syntax, or add some new field or new punctuation to their syntax, I have to be sure that PokerCruncher doesn't barf and still parses their hand text correctly, which would probably mean code changes to PokerCruncher to keep it in sync with those other programs.

I think your feature would be great to have in the app. But what I'm saying is that it can't be taken too lightly; let me chew on it for a while.

Thanks for ideas and feedback. Always good when users and developers of an app are discussing and weighing feature ideas.