The choice between horizontal or vertical is one of the first ones I made in designing the program. The reason for horizontal is that most serious poker players have a setup of multiple screens or at least one very large one.

I could .... Mmmm, I need to think about that. I definitely see your point. It's something to consider.

But first, that "darn" video!

hey, the beta i found has expired - is the a current release? this looks v interesting.

thanks

When using the slider to choose a Top% of best hands, it would be often better to use the Sklansky-Chubukov ranking.
A choice as a default between this ranking or the one you use would be great.

You can set your own rankings under the customize range window.
It's the button next to the ?-button.
The ranges are saved in the range.txt file which you can exchange with other users.
When I wrote it I sort of figured that users would probably come up with some better standard ranges than I could and that in time someone would create a good range.txt file.

I am sooooooooooooooooo lazy

You can get 1.0.6 in post 22 of this thread.
I'm releasing 1.0.7 tomorrow.
There's not a lot of changes in it though since I've spent the past week on the video and doing some grinding.
After the video is released I'll continue work on the program.

The 1.06 beta has actually already expired despite it still being March.

-Andy

There will be a full blown instructional video on how to use the program once it gets out of beta.

Get version 1.0.7 here:
http://mediaserver2.stoxpoker.com:80...vbeta1_0_7.msi

Some improvements in the new version, but I've been mainly focussing on the video manual which I'm hoping to complete today.

Bugfixes:
When copying an action from for instance flop to river the riveraction still thought that it was at the flop. This lead to some very minor problems.
Preflop conditions added by doubleclicing in the quickselect menu did not work until they were edited.
Program crashed when copying a preflop condition to a postflop fase when starting the tree after the flop.
Some crashes when rightclicing popups.

Improvements
When program can not continue because no preflop range has been given an errormessage will be displayed explaining the nature of the problem.
F9 will now not only toggle relative percentages to absolute but also display EV in absolute amount of money.

Cheers!

Scylla

how the hell do i make it stop pre-flop again, i.e. calculate pre-flop only???
i did it fine in earlier version, this is tilting the crap out of me

demonstration:

By having a go to showdown situation preflop, meaning that all players except one have either folded or have gone all in.

ah ok

What I'm trying to do is calculate a following situation:

this shows our EV for the whole hand from the beginning, but what I'd like to do is calculate our EV to the red line only, to find out what our EV is when he calls AA-TT, AK pre-flop without going all-in. Is this possible, and how do I make it stop at the red line? Sorry, I kind of suck with this thing still and I probably don't fully comprehend the whole EV thing either heh.

Oh, one more thing: often the different streets get pretty crammed, like in above example you can't fully see button's range pre-flop. could you make the separators between different streets "draggable", so you could expand or shrink the width of different streets? And perhaps make them auto-size by default? I think this would be pretty important if your plan was for people to post stoxEV calculations in hand threads - PITA to explain particular player's range separately

Some kind of "export to jpg" function would be pretty cool too for forum purposes, I don't know if that's doable though

First of all, all preflop EVs are calculated in the full knowledge that the flop will be QsJsTs. In order to calculate our EV in this situation on an unknown flop you'd have to define all postflop actions on an unspecified flop (which borders on the impossible since there are so many flops).

In answer to you question, try what happens when you set the rake to 0.
Currently, in the last decision preflop for both players $52.77-41.22=11.55.
The pot is 13.50, the rake taken out of the pot will be $1.95: $13.50-$1.95=$11.55.
If the rake were set to 0 all decisions would add up to the current pot.
This means that when called our EV would be -$41.22.

When you hover over a condition its full name will be displayed.
As you will see with the full name in preflop situations, it's really large and resizing the fields would result in extremely wide trees.

As for exporting to JPG I'm afraid that you're stuck with making screenshots.
It would be a very large amount of work on my part and it would take away from working on the program's analysis capabilities, while using paint to save screenshots is a very viable alternative.

I know I can see the range by hovering, I was talking about posting screenshots where you can't see the whole ranges. I can see the point about too wide trees, but there's plenty of vertical space - perhaps you could set a width and make the overflowing text go on another line? This would be good for posting screenshots. Maybe a possibility of switching between that and the current view? I mean like this (mad editing skillz):



ok, I think I get it now, thanks! hope you get the video tutorial done soon so you don't have to answer all my stupid questions

Ah I see.
The main idea in these sorts of cases is that the savefiles can be exchanged since they are only something like 1kb in zipped form.
The stoxpoker forums allow users to attach small files to their posts, twoplustwo might be willing to offer the same feature if the demand is there.
Good alternative?

Uploading it as we speak.
Will still take a while to convert though.
Also some sound issues of me getting used to the microphone.
I hope it turned out good, after working on it for several days I just can't tell anymore if it's great or terrible.

Just cuz u cant attach a file directly to your post, there is no reason people cant upload their save files to a hosting site like Mediafire, etc, and then just post links to share them.

omg too much trouble
yeah ok sounds reasonable, didn't think of that, dumb me.

FWIW - I havent used this yet... but I am gonna start. So I will prolly start posting some really noob questions.

The video manual should be coming out within days.
Might wanna wait for that.

Ok, here's the new version of the program:

http://mediaserver2.stoxpoker.com:80.../stoxev108.msi

Not too many big changes.

Most noticable change is a new option in the postflop menu.
If there was a flushdraw on the flop you can now determine on both the turn and river if the third flushcard has come.
In case the turn makes a 2x2flush and the river is a backdoor flush, this will NOT be accepted by this condition.
It only refers to a flushdraw from the flop coming in.

Video should be up by wednesday is my best guess, tuesday if we're lucky.
It's been a long ride, but I'll finally have that behind me
I never thought making a video was that hard.

I'm trying to model a very simple preflop scenario in a HU game. SB either openraises or folds, BB either reraises or folds. If BB reraises, SB folds.

What I'm interested in is finding out SB's overall EV in this mini-game. Am I understanding correctly that this number isn't displayed anywhere?

It's the number in the red circle:



Don't forget to add a fold all hands condition to the small blinds actions. Otherwise he will be dealt (in this example) the top 38% of hands 100% of the time and you don't take into account the times he folds.

What the number in the red circle tells us is our EV given that we decided to openraise, since folding is not treated as a loss:

0.38 * 0.807 * 1.5 + 0.38 * 0.193 * -2.5 + 0.62 * 0?? = 0.27664 = 0.28

In reality in a HU game, folding the sb comes at a price, we lose half a big blind. This is what I would like to see, as the current calculation doesn't have (as) much practical use for HU poker.

0.38 * 0.807 * 1 + 0.38 * 0.193 * -3 + 0.62 * -0.5 = -0.22336 = -0.22

This is the number I would like to see in the red circle, or at least somewhere. This number tells us what our average final stack will be (77.7 big blinds) if we play this game 100 times. It won't be 127.7, which is what the current number would seem to imply.

Edit:
62 times, our stack will decrease by 0.5 (-$31)
30.67 times, our stack will increase by 1 ($30.67)
7.33 times, our stack will decrease by 3 (-$22)
End result -$22.33

You will get the win/loss from the sb simply by (expected value - small blind). In your example you will get (0.28 - 0.5) = -0.22.