"Add current tree" will add the tree that is currently active to the database. The input field allows you to enter the name with which it is displayed. An example of this is given in demonstration video 2, where we add the same tree, but with different stack sizes. I believe in the video we use the names "1bet", "2bet", "3bet", "4bet" and "5bet".

"Change all flops to" is when you are using a database where all trees have the same board, but, for example, different bet sizes (like in the example above). With this button you can set a different board for all of the trees in the database. Without this button you would need to build the database all over again.

I also think this could be a useful addition. Although to clarify, the weighting I'm referring to would be applied after the current calculations occur. For example, an Ax Kx Qx flop can be dealt 4 possible ways, but with a weight of 0.5 applied it would only be 2. This weight would also be applied after all blocker/range calculations have been considered. The reason for doing this would be so we can use the flop subsets discussed here to more accurately predict preflop EVs. To clarify further, Pio represents these weights as the total number of possible combos for a flop whilst Simple Postflop uses a multiplier.

I agree with this. Pretty much spot on what I was trying to say.

Thanks for clarifying!

We actually do indeed already weigh by the number of possible combos for a flop. Also, in the future (in one or two months) we will also most likely offer default subsets of flops that adequately represent the entire possible range of flops. We may or may not apply additional weights there as well, depending on if it turns out if additional value can be gained from that. The default subset feature will also allow to manually set the weights of flops, so (very) advanced users should be able to do this if they want to use their own settings. So if I understand you correctly, then what you're looking for should be available shortly.

Amazing, thank you!

Any plans for expanding aggregate tab in database distributions window to include turn/river frequencies?

We can certainly consider this feature for future releases. And at the very least this data is definitely available in the engine. It would require some changes to the interface though. For the moment, we are working on v108, which will offer predefs in the preflop menu. So this will have to be after that.

Scylla

Looking for CREV expert for coaching, PM me for details.

Great, given that CREV is already showing average turn/river frequencies before those cards being dealt. It would be nice to also implement it in GTO+ in some way.

The main challenge would be an interface one, given that we would need to alter the tree view to one where you can navigate to the turn. Also, the aggregate frequency data would need to be stored in the trees after solving. None of it is particularly difficult, but it's just one of those things that takes about one or two weeks of development time. We will deal with all such remaining details after v108.

Hey scylla,

Are there any plans at any stage to add the ability to solve for preflop like with Pio and Simple?

Is it possible to save a game tree?
I want to use the same tree but with different ranges.

For the moment we are focussed on the upcoming update v108, which will offer predefs in the preflop menu. We can look into which other functionality to add after that. A preflop solver is very resource intensive though, so only very few of our users will actually be able to run it. I suspect that most users are better off just using their historic performance from trackers to figure out how hands should be played preflop. With this data you will get strategies that actually match the games that you play. In the end, exploititive play trumps non-exploitable play. Furthermore, with tracker data you will also get reliable historic data on multiway hands, while a preflop solver can not be used for anything other than heads-up. Paradoxically, heads-up is the most read-dependent part of poker, so it's exactly there were you would least need a solver. Should your opponent be of a quality where you would need to resort to non-exploitable play, then that may actually be a game where you're better off leaving the table. It's particularly for postflop play where a solver has most value, given that there, for just about any spot, the historic sample size will be virtually non-existent.

Yes, for that just use the same tree, change the board/ranges, go to "Build tree", click on the tab "Rebuild" and click on "Rebuild with current settings".

Well said. Actually at the moment you need to invest 1000$ for PIO edge and probably same amount to run it on a cloud to solve preflop HU.Or to invest 500$ for Monker(their support is terrible and I am not sure how accurate is this program solving almost everything preflop postflop, multiway,PLO,PLO8 etc.) and some amount for powerful PC and solve whatever u want.CREV + GTO+ r best investment money wise.

Okay, thank you for the very detailed reply scylla, much appreciated as always

What would be really useful would be a training module. Basically you could load up a bunch of precomputed solutions and it would deal you random hands and you'd play the spots and get a score at the end. You could sell it as an addon to the main program.

Something similar to this

https://www.youtube.com/watch?v=yNu3nTkdXbE

Yeah that would be really usefull.

An important advance in game theory has been published. See here

https://deepmind.com/blog/game-theor...i-agent-games/

https://www.nature.com/articles/s41598-018-19194-4

Hi
Anyway I can see all Turn runout report for Player 2 with all betting frequencies(not only EV and Equity) after Player 1 Checks or Bets?
Thanks

This data can not really be added between the different turns. For example, if you're looking at the scenario where player 1 checks, then, player 1 might check 80% of the time when the turn is 2h, and 11% of the time with a completely different range when the turn is As. Summing data that has been obtained under different circumstances is possible, but has no practical meaning. It's only possible to show the overall performance for player 2 for the entirety of all possible scenarios (so for the "Bet" and "Check" line combined).

Getting more familiary with the software now but as someone who only bought it for GTO+ (and never used Cardrunners EV) are there any videos or parts of the Cardrunners EV manual that I should be reading that are relevant to GTO+ ?

The current release videos for GTO+ contain all relevant information, so there's no need to look anywhere else.

Hi Scylla, are there any plans to add the ability to save preflop ranges? I've been enjoying GTO+ very much so far.

Yes, this will be in v108, which is almost finished.