Hi Scylla,

Is there a way to save, export and re-use a custom edited tree?

Ok, I will consider it for future releases.

For this:
1) Load your tree
2) Make any changes to the board/rake/cap/etc as you see fit
3) Go to "Build tree"
4) Select the "Rebuild" tab
5) Click on "Rebuild with current settings"

I have an odd result. I edited a tree manually. OOP always checks and IP has four possible bet sizes. I carefully edited every branch of the remainder of the tree to be "reasonable" but not too large. The resulting tree requires 5.5GB RAM.

I assigned a flop of [Jh Tc 8c] and used {BTN open, BB flats} ranges for 100bb.

I ran the solver to a 0.5% dEV.

Every single XhXh has a lower Equity (by 1%-2%) and EV of the corresponding combo of XdXd and XcXc. This is not possible, correct (unless I had assigned some weird suit-based preflop ranges)?

EDIT: I also just noticed that every flush draw combo has a slightly lower Equity and EV than XdXd and XcXc combos as well (with the exceptions of 76s, 75s, and 74s). And why are AdQd and AcQc showing somewhat different strategies? (This also persists over all hand combos)

Disregard my last post. I had changed the board texture and did not realize that to rebuild with an edited tree I needed to enter the edit mode and "Accept Changes" again.

Why in "build tree" in "ip settings" i cant use for set bet for expample 33p or 66c, and this is only for oop? I know i can delate or add in edit tree, but it is harder and longer? Why you dont allow me to do in build tree?

Hi Scylla,

Can you remind me the combination when editing a tree to remove a call/fold option when there isn't the red X? I cannot seem to find it in the search. Thank you.

CTRL+Click on where the red X should be. (I think it only works to remove the call option though, not fold)

Ok that is correct cannot force remove fold this way. Thanks (:

We currently only offer the ability to distinguish between probe and cbets for OOP, but I can consider expanding this for future releases.

hello I cant figure how to make gto+ play against the solution allow me to drill a specific spot lets say facing xr on flop as pfr srp ip
I want to do it so the flop changes each time but I can only figure out for the specific tree within a database which only allows for one flop

pls help thank you

Hi Scylla,

I have a query/request regarding the hand classification buckets in GTO+. Are there any plans in the near future to increase the number of these or would it be too great a task from a resource/development standpoint to be viable?

On a given flop for example, PP's between the 2nd and 3rd cards are often strategically different from 3rd pair which again is strategically different from PP's below the board. I'm curious to understand the reasoning behind the merging of all of these into a single hand class (Weak Pair). They are segregated in not only competitor products but also your own Flopzilla (which predates GTO+). I also think that it would be cool if other backdoor draws were also bucketed seperately (e.g. BDSD&BDFD, BDSD and 1 card BDFD).

I understand that we can export the range output to FlopzillaPro (awesome feature btw ) to regain some additional granularity within the Weak Pair class however without doing multiple exports and manually comparing outputs (can be quite tedious), we don't really gain a sight of how the solution is playing each class from a strategic/frequency standpoint (e.g. how often third pair is betting vs checking and the frequencies of the combos taking said action).

Hope you can help

Is there a way to convert weighted ranges from Power Equilab so they can be easily entered into GTO+



100: KK+, AKs, 80: AKo, 35: A4s, KQo, 60: AQs, K5s, 10: JJ, ATs, KJs+, QTs, T8s+, 86s, 53s+, 70: QQ, 20: AJs, K9s, QJs, J8s, 75s, 40: Q9s, 15: J9s, 50: Q8s, 30: A7s-A5s, A3s-A2s, K7s-K6s, 76s, 25: 87s, 64s+

Right click the range and select "Copy with weights in square brackets".

wow awesome. thank you

Drilling a specific spot does not work versus the database, given that each spot in each tree is not the same spot.
We can consider expanding the feature, although it's not entirely straightforward.
In some cases, if "Basic" storage is used, recalculation would be required between each hand, which would cause a slowdown when every new hand is loaded.

We can consider adding more stats, however, we do need to keep in mind that, with every stat/button/feature/etc that is added, the interface becomes more complex to use. Adding a single feature may seem inconsequential, but doing so with some regularity for several years will add up.

Ok, I'll see if we can add a way to recognize this type of input.

I am very sad to hear this - certainly there has to be a practical method of making this happen - I wouldnt mind the recalcs anyway bc the goal of doing the study is to murder my brain cells with deep thought about every new texture/rng etc you know?

I can consider it for future releases, although a disadvantage of this feature would be that it may not work entirely smoothly in case of drilling turn or river lines.

yes please!!!

Would it be possible (perhaps easier?) to do this with bet sizes selected by the solver? So for instance the player would only choose, say, facing turn probe, but not the exact size, and then the solver would pick one of the bet options available (weighted by the frequency). Would this circumvent the issue of every tree not being the same? I would prefer this implementation either way.

Is it possible when manually editing trees to change bet sizes without previous node locking being erased?

That's not where the problem is.
Basically, certain spots will load less smoothly than others.

If the line is on the turn/river, then the tree can be exported to a different window.
In this new window it can be edited however you see fit, without affecting the original tree.