This should be available shortly. Due to our efforts to release v105 before the end of 2017 certain details were not included in it yet. We will release a smallish update v106 shortly, most likely on Sunday, and I'll see if a 3x option can be included in it. I'm not as sure as a 50c option though, due to it being an absolute amount. There's many cases where such a bet may not be applicable to the situation.

Guys, does someone notice that multiple bet sizes option has less EV on turn compared to the single bet size. Yesterday I experimented with K5sQ flop, BUvBB, single raised pot, single bet size was 78% of pot and multiple bet sizes includes this single bet size. Maybe I missed something to point but I wondering has somebody noticed it too? And if my conditions was equal for both cases why algorithm does not choose option with better EV(for BU)?

Most likely those turns are just not reached with the exact same ranges.

Why solver does not choose line as with the single bet all streets or it only takes into consideration one street (not complex) because flop is slightly higher EV but turn is lower and river too(solved only a few rivers)?

example

I solved tree with single flop size and multiple turn and river sizes compared to single all streets size. Now turn and river EV for BU is better for multiple bet sizing.

Our solving algorithm is extensive and does not use abstractions. So all turns and rivers are treated. The reason for the differences is because you're comparing spots that are not the same. If the tree is different (even if the difference is small) then you will get different ranges on the turn/river, and therefore differences in the solutions.

The problem is not in the interface. We can basically produce any interface solution that is needed. The problem is that when you set that, for example, the river bet should be 50, then situations will occur where this is not a practical size. For example, the pot could be 1000 and you would still be betting 50. It's for this reason that it's better to express the bet sizes relative to some property of that particular situation, such as the pot or villain's bet size.

Ok, the ability to enter bet sizes expressed as 3x times villain's bet size has been added for v106. We will probably release a small update this Sunday which will, amongst other things, contains this feature.

When we conduct database analysis, we can check OOP players' chekcing and betting frequencies by clicking 'display result in graph', how about those of the IP player after OOP's decision?

That's not possible, given that there's multiple spots where IP gets to act.



On the other hand, there's only a single decision for OOP to be taken into account. In case where OOP only has one action though (for example if he always checks) then IP's frequencies will be shown.

If I don't get wrong, it implies that an overview of OOP player's check-raise frequencies on different flops for the time being is not available either (maybe unless OOP player always check and IP player always bet?).

Will there be any related feature be considered as a part of future updates?

Thanks!

why is "SB 0.06" different results ?

The 0.06 value is the EV prior to posting the blinds; the pot is $0. The 0.56 value is after SB has already invested his blind of 50 cents, BB has posted his $1 blind and the action is on SB; the pot is 1.5.

At the moment we do already offer a feature where you can see the aggregate frequencies across flops. See the pic below. So it will display the entire flop tree, with the associated aggregate frequencies for every action. There is however currently no feature yet for displaying a breakdown for each individual decision.



One solution that I can think of for this is to display a popup with such a breakdown whenever you mouse over any item in the tree. Or possibly even offer the option to display the data in that decision in the table if so requested by the user. I won't add it yet for the update v106, which is expected to be released tomorrow, but I will keep this option in mind for later releases.

Thank you for the feedback,

Scylla

Hi!

I noted that today the webpage is down, since 12 hours ago...

Hey scylla is there a way to let node lock villain for future streets?

Say we are OTF and expect villain to check back turns a lot OOP is there a way to change the % to be lower for villain OTT (even though there is no run-out set for turn)?

No, it's only possible to remove the "Bet" line entirely. To be fair, if IP checks a very high frequency, then just leaving out the bet should be pretty close. We can look into if perhaps it is possible to manipulate the frequencies of actions, but right at this moment there is no such feature.

Hi Everyone,

The release of v106 has experienced a slight delay, but it should be available by the end of today. It will contain the option to express bets as 2x,3x,etc, changes to the preflop menu so far (negative slider and suit options) and some minor bugfixes and changes. The predef menu will be available in v107.

I've been receiving similar reports for about a month now, and I can not seem to reproduce it. The website is up, both from my own location, as well as just about any proxy. For example, this website lets you check from multiple locations: https://www.geoscreenshot.com. Can you tell me in which country you are located? And if the website works for you through a proxy?

Ok, I'm trying from Spain. I´ve been trying from differents browsers. Today it's still not working.

Using another location I can access, as you said (I tried from "Australia"), but it's a little bit unconfortable.

Ok, can you tell me if perhaps you're getting a message of some kind?

Same message like I have no connection.

"ERR_CONNECTION_TIMED_OUT"

I also connect from Spain and the same thing happens to me.

I discovered that it was a problem with the cache mechanism used by the operator.

Sulución: Restart Router so that the operator grants you another account with another IP

Thanks okay i will play around with it. Would be a nice feature to have AFAIK other solvers don't have this either.