This will require two conditions, one for one overcard and one for two overcards:
- Gutshot+Highcard(Kicker: Above top card, second kicker: above topcard)
- Gutshot+Highcard(Kicker: Above top card)

There's other ways to accomplish the same thing here though.
Another method would be to specify "gutshot" and then, under the "holecards" section, select 8 and 9, meaning that the holecards will need to contain at least one 8 or 9.

I downloaded the new beta, but it seems to run in trial mode when I launch it. All previous updates automatically ran in the registered mode after downloading and installing.

New graphics look nice.

EDIT: I just noticed the old desktop icon is still on my desktop and there is a new folder in my program files folder.

The beta is installed in a different directory than the regular version.
In this manner you can try the beta without removing the current alpha.

To register the beta, copy-paste the regkey.dat file into its main directory.
CardRunnersEV.exe will recognize it upon startup and initialize the registered version.

You can find the regkey.dat file in the regular version's main directory.
Or in your registration mail.

Great! Thx a lot.

Haven't really played with 2.8.3 a lot... now that I tried, it's freezing on me when I load tmp-files (about a 50% success rate). Win7, 64bit... any know incompatibilities or something? Doesn't happen with the non-beta.

No, I'm not aware of any incompatibilities.
Could you please mail a tmp file that's not loading for you to support?
I'll see if I can figure out what's going wrong.

If I hover over "all hands" and press alt Q Is it supposed to select X% of hands with the highest EQ?

It seems to be picking X% of random hands for me.

Alt+Q should select the x% of hands with the highest EV.
If you want me to take a look, please mail the savefile to support.


On another subject, you might want to try out the beta.
It offers more filtering options, as well as many more additional features and improvements.
The beta can be downloaded here: http://www.cardrunners-ev-calculator...henewbeta.html

Could you please explain the difference between filtering the top %:
-from the entire decision; and
-from just this condition?

Thanks.

Let's say you have a decision where you decide to bet 40% of the time and check the remaining 60% of the time.

You now compute (with F7), after which you mouse over the "bet" action and press Alt+F for the filter menu.
Let's say you want to filter the top 50% according to equity.

Filter from the entire decision
If you choose this option, then this will result in you betting 50% of the time and you checking the other 50% of hands. Your betting range will be the 50% of the strongest hands that were in your range.

Filter from the condition
If you choose this option, then the strongest 50% of the 40% you were originally betting will be filtered out. The ratio of bet vs check will become 20% vs 80%.


So, in the end, what this comes down to, is when you give the command to filter the top x%, the software needs to know on which range to perform this filter action. The range of the entire decision? Or the range of just the action you're mousing over?

????

I have 2.8.3 installed and I don't see this option. Is it just in the old version?

I have Alt+F for filter for EV or equity, is that the replacement for Alt+Q?

Yes, Alt+F is indeed the replacement for Alt+Q.
v2.7.4 only offers filtering the top/bottom % of hands according to EV.
The beta (v2.8.3) offers a wider array of filters.

Just tried to analysis a 50/100 hand, manually building the tree. Set blinds to 50 and 100 etc, then when I click for first raise I can never enter more than 100, even if I click say pot or if I try and manually set the amount, it always displays in the tree as 100.

I am new to cardrunners EV, so hopefully my questions will not be too basic.

I am using the beta version.

I made a tree for a hu hand such that sb bet and bb called on the flop. I then wanted to use the checkdown future to assign checkdown equity for various parts of bb's range. When I did this on the turn (without specifying what the turn was), it assigned any and all hands that "could" potentially satisfy the condition based on all possible turns, into each of the checkdown groups, rather than use the hand values as they were on the flop.

To get around this, I had the bb raise .01 more rather then call, the sb then raise .01 more rather than call, and then added the bb checkdown groups.

From videos I've seen this hadn't been necessary though, and this seems like a common situation where you want to input checkdown equities as of a certain street, but since the actions on that street are complete, you are on the next street.

Sorry if that is confusing.

Second question is that when using the Maximum exploitative feature to determine optimal strategy for the bb, it gave the bb an "Expl. Range" to call the sb bet (or in my case actually the range to raise by 0.01), but then it also gave an Expl. Range for the BB to checkdown with 150% equity (which I previously had >=tp). It made this checkdown range all hands though, and then as a result it was saying to call the sb bet on the flop with all hands (probably because they were all realizing 150% of their equity). What I wanted to figure out though, is what range the bb should call the sb's flop bet, given the checkdown percentages for the various hand classes that I assigned previously. It seems odd that the optimal strategy the program came up with was to just realize 150% equity with all hands!
My other simpler questions involve the beta:
1. Is there a way to turn off math mode and just use monte carlo mode so that simulations can be run faster?

2. Was the range selector tool (the pokerstove style one) removed in the beta for postflop when editing conditions (in the regular you could still click the grid and bring it up)

*Also note a possible bug in the beta: the tree had bb call, and then the arrow over to the turn with action on the bb. When i double clicked on call and checked the box "change to bet", then double clicked again and entered a "bet size" such that the action changed to raise, it still had the arrow go to the turn with action on the bb, rather than arrow over to the sb while still on the flop*

It sounds like you still need to set stacks.
They're probably still at the standard amount of 100, which would indeed make in impossible to bet/raise more than 100.

If that's doesn't solve your issue, please mail your savefile to support and I'll take a look.

I'll have to get back to you tomorrow on this.
For now though, could you please send me the savefile(s) for your questions?
It's typically a lot easier to answer a hand-specifc question if I can see the hand itself.
Please just mail these savefiles to support.

Cheers,

Scylla

Yeap that was the problem...

I am going through the tutorial learning how to use the program. Just though I'd let you know that the file on this page of the tutorial: http://www.cardrunners-ev-calculator...xperiment.html is not able to be downloaded.

Ok, thanks for letting me know!
I'll see if I can fix it.

hey guys,

I've bought this software 2 days ago and i have to say I realy like it. I watcht 4 videos about it but i have two questions:

1. if i use diffrent weights on hand ranges, the rest of hands will automaticly go to the fold range but how to set up if i want so add it to the minraising range. for example villain openshoves 22-88 75% of th time and minraise 25% of the time. is it than right like that?

http://www.abload.de/image.php?img=crgzykd.jpg

2. how to calqulete pre flop decisions if its non All in, and you dont want to inklude the preflop action in the calculation. i've tried first with setting up first act to openfold on the flop but this messed up everything i guess.

You'll need to change the 75% to 100%.
After 99-22 has been treated as 25% minraise, the remaining 75% will pass on to the next action.
You'll need to push them 100% of the time at that point.

Also, it's probably better if you change the "fold" condition to "all hands".
Then, all hands that did not apply to the actions above it will be folded here.


I asume you mean "... and you dont want to inklude the postflop action in the calculation ..."?
For that, just let the action proceed to the flop and then use a checkdown action.
To add a checkdown action, click on the decision node and select "checkdown".

By checking down, you'll let each player realize his equity of the pot.
If you want a player to make a bit more/less, then increase/decrease the 100% number behind "checkdown" accordingly.


Also, fwiw, you may prefer the current beta over the alpha.
It has many advantages over it.
You can download the beta here: http://www.cardrunners-ev-calculator...henewbeta.html

hi
im pretty confused: i put in a hand where all board- and holecards are known. On the river I bet 216$. If villain calls 100% with the worse hand, his EV is -171$. Am I overlooking something or is there a mistake? how is he not loosing 216$ in EV as well? If the 2nd is true ill send you the file.
thanks

Please send me the file.
It's probably the easiest way, since otherwise I'll have to guess what's going on.

Hey scylla, is there a tutorial available somewhere for the script editor?

I want to know if it is possible to get the unexploitable shoving range for different stack depths, so I would change the stack depth by X bb every loop and save the unexploitable shoving or calling range to a file - is this possible?

I've started with a tutorial, but I got distracted by a holiday, Flopzilla updates, bugfixes, and so on.
What I've got so far can be found by going to the "Videos" button in the beta's startup screen.
I'll continue working on that video series in about a week.

As for your question, it's possible to set up a loop and let the software make unexploitable shoves for each stack size. You can make graphs of the EV performance as a function of the stack sizes. Or save the outcome for each stack size as a quicksave. And there's a couple of other possibilities as well. However, you can't save ranges to file. It would make it too easy for external software to operate CREV and use it as its engine.