hello scylla, is it possible to round the statistics to the nearest tenth?
for exemple :

for two pair write 1.5, and no 1.48

thank you for your software, I tested pio, simple postflop, gto wizard, and I much prefer gto+

It's a bit tricky to decide where to round values, and different people may have different opinions.
A value like 1.475845 can be rounded in several different ways.
To me personally, 1.48 seems to be the optimal balance between accuracy, and keeping the visual size of the number down.
I believe that, as a rule of thumb, we aim for 3 numbers per value (I'd need to check the code).
But I can see if we can perhaps add customization here.

-- replayer suggestion --

When using the replayer (to play against a database), the suggested bet sizes are the ones that have been calculated. As you (scylla) have mentionned in this thread, multiple bet sizes on turn/river do not really impact the overall EV for flop play that much. So usually, when running database solves, I solve for multiple flop bet sizes, but limit the sizes on turn/river as it saves (a lot) of time for solving. When I need to dive deeper into a turn/river spot, I just open a new window (with the "up arrow" in the turn panel) and just run a solve for that spot with multiple turn/river bet sizings. That last part goes really fast.

However, when I want to use solved database with the replayer for practive, the solves with "simple" turn/river bet sizes become a bit useless as on turn and river, the different bet sizes can make a big EV difference.

My suggestion: add an option in the replayer to have different turn/bet sizes than the one in the solve and calculate them on the fly during the replay. It would make database solves with multiple flop bet sizes instantly useable for advanced turn/river replay functionality.

One could even add an option in the turn/river PANEL during tree analysis to do the same (calculate a different tree with multiple bet sizes on the fly), but I'm not sure how to have that work in the interface...

Hi,

Could you consider adding EV in terms of the percentage of the pot to the viewer? Both for range and each hand when hovering over it. It would make it a lot easier to see how close thresholds are and how good you're doing on certain boards (e.g. is a +1EV bluff OTR very mandatory (yes, if it's in a SRP. More close if it's in a 4BP)).

Example:

Actually, all bet sizes perform almost exactly the same (even bet sizes that don't make sense perform surprisingly well, provided you're playing perfectly).
You can verify this for yourself by building the same tree, but for different bet sizes.
After that, compare the overall EV for each tree.
It should be nearly the same, regardless of the bet size (unless the spot is non-zero-sum, in which case many different solutions are possible within any given dEV).
To get the overall EV, look for OOP's EV below the table in his very first decision.
See the screenshot below.

The most important factor in EV performance is the quality of play; not the sizing of the bets.
When playing perfectly, basically any bet size will work.
Whereas when even using pinpoint accurate bet sizing, even the slightest mistake in quality of play can lead to a huge drop in EV.

That being said, we can of course consider adding automated customization when looking at subtrees.

Ok, I can see if we can add it as a mouseover feature, or perhaps a toggle.

Yeah, I realized that after I wrote it. My request was more to easily being able to replay turn/river situations (small bet, pot size, overbet, all in) and seeing what the solver prefers with a given hand without having to pre-calculate every hand, but rather that specific hand on-the-fly.


That would be awesome and a great feature!

Hello,
see attached image please.
IP is supposed to raise 61% of the pot at the flop but actually the simulation shows a raise of 11.5 while the pot is 11.2.
Is there anything I might have missed?

The starting pot was 8.3.
The bet was 2.9, which makes a total of 11.2
When you call, the pot will be 11.2 + 2.9 = 14.1
If you want to raise 61% pot, it will be a 8.6 raise.
8.6 raise + 2.9 for your call = 11.5 bet total

Small annoyance (bug?):

When using the UP arrow in the turn panel, a new GTO+ window opens with the current state -> good!
On the "Run solver" panel, the Target dEV shows a target dEV of 0.
On the "Run solver" panel, the number of threads shows the latest used value.



Expected:
The target dEV is the latest used value, just as is the case with the number of threads.

As this is not the case, each time a solve needs to be executed, the dEV must be filled (either manually or by clicking one of the presets), which feels a bit meh

This choice is intentional, because exported trees will either be turn or river trees.
We reasonably assume that users want to solve to a dEV that's as low as possible, and on the turn/river, solving to (almost) zero will often be the default.

Hi Scylla.

I'm wanting to purchase some preflop ranges from either Range Converter or Monker Solver. Is there any easy way to import these ranges into Flopzilla/GTO+? Or do you know which ranges are easiest to convert? I'm hesitant to purchase preflop ranges from either source if I have to import them one at a time. That seems daunting.

Many thanks!
Sasquatch

Hello scylla!
Add ability to make a certain bet only if i make c-bet on the flop and if i make c-bets on the flop and turn too. For example, i have two sizing of bets 75% and 150% of the pot. I want to have ability to bet on the turn using sizing 150% only if i bet on the flop. And have ability to bet 150% of the pot on the river only if i made a c-bet on the flop and turn.

You can achieve this by editing the tree.
Create your tree as usual.
After it has been created, on the top right, click the "edit tree" icon:

Click "Import Tree" in the center of the screen (or bottom right if you already edited a tree before).
Navigate to the proper section on the flop and click the arrow to go to the action on the turn.

On the turn, click the action panel:

In the popup that appears, remove the 75% sizing by clicking the X in front of the action and accept the changes.

Your tree should now look like this:


Repeat for the river (and/or XR on flop/turn).

As a final step, click "Accept Changes" in the bottom right of the program.

If there is a better way, I'm sure scylla will jump in too

Pio format should be easiest to import.
For this, store the ranges to a subdirectory /pio in GTO+'s directory.
Then, start GTO+ and go to "Settings->Import preflop ranges from newdefs2.txt or newdefs3.txt".
Should you need further assistance, then please contact support.

How do you add a check action using the tree editor?

Enter 0 for bet size.

Hello scylla,

When editing trees, I found a bit of an inconsistency in the way things are presented.
Example:
The following simple flop tree (based on 66% default size)



When I hovering over the action after the initial 4.5 bet, I get the following popup:



When clicking the action, I get the following popup.



In the last window, it says “RAISE 9.7”, even though in all previous windows it says “RAISE 14”. I find this a bit confusing
(And yes, I know the “RAISE 9.7” is excluding the CALL that needs to be made )

My suggestions to improve this are the following:
1) Add the amount to call to the edit decision window. This could be included in the information line on top (pot=15.1, stack = 93, to call = 4.3). I think it would be useful regardless of the other suggestions.
2) Change the wording on the buttons from “Raise 9.7” to “Bet 9.7”
3) OR Change the amounts displayed to include the calling amount so from “Raise 9.7” to “Raise 14”. At least it would be consistent with the terminology used in the other windows. In this case, when adding an action, the user would also enter the total amount (and not the bet amount).
4) OR (ideal suggestion): make an (toggle button) option to display/enter the amounts with or without the bet amounts



I would personally go for option 4). If that is not possible option 3) and last resort option 2).
Hope you like my suggestions.
K.

The reason for the current choice is because it's intuïtively easier to see that raising 9.7 in a pot of 15.1 amounts to 64%.
It's a balancing act in how much detail to show, although admittedly there's probably some room for improvement here.

Ooohh, now I see! In the mouseover, the the pot is 10.8, but in the "edit tree" the pot is 15.1 (which it would be if you call). Makes total sense (not really)

At least now I have a better idea on what amounts to put in, thank you!

K.

Also, in the "build decision tree" window, it displays "bet" vs "raise", and there the amounts are including the initial call...

results in


So in some windows, it's including the amount to call, and other windows it is not - hence my suggestions for improvements (and things to think about for you)

Have a great start of the week!
K.

I believe that the editor is the only exception, for the reasons that I stated previously.

But it is inconsistent. It is the same story as here:

Considering the IP player plays twice at the same time - calling first then raising his call - is definitely not the way people think about it and is disturbing.

I do not manage to use the Flopzilla<->GTO+ communication for ranges. I allowed communication in both ways, letting the default port number, but GTO+ side the "Export to FlopzillaPro" button remains non clickage.

That's just how % of pot is calculated.
It's not something that we have control over.