I don't think I understand. In a 3bp sim where the pfr is allowed to b-b-j, there will be an ev loss if we replace the all in river sizing with a block bet and this will be reflected in the nash ev on the flop.

Perhaps I misunderstood your question. However, it's not possible to edit the river and only recalc that river. We can consider it for future releases, but right at this moment this is not available.

This would be tricky, given that if you want to start drilling at the turn, and "Basic" storage is used, the tree would need to be calculated prior to being able to play the hand. Also, each turn/river spot that you would drill would be completely different from the other flops (the previous action is the same, but has different meaning). So this is not entirely straightforward.

Yes but if you have full save which I think many serious players do to be able to play versus the solution instantly it would work great. Why not make it for full saved databases at least?

Ok, I will consider it for future releases.

I don't think this is a great idea. I have solved several databases that are over 1gb, and they take quite awhile to load. If the sizing is similary to pio full saves, then each flop will be over 1gb, some will easily go to 3 or 4gb for a single flop. That is going to be painful to load. I wouldn't mind being able to do it with a single flop.

Each flop is 1GB? What exactly are you talking about, lol? I have a BvB database that I solved and stored using extensive storage, and the whole thing is 5.6GB in size. GTO+ save files even with extensive storage are far smaller than Pio's full saves. A database being over 1GB is really not much, and how long exactly is the loading time? Is it just at the start to load the file or are there delays when browsing or using Play vs Solution feature? Because for BvB database, it takes about 15 seconds to load the database (I have an SSD), but after that, there's really no delay at all, for anything.

extensive storage only saves turns, if you want rivers saved then the size explodes. Do a full save in pio with one flop and you will see what I mean.

I do 1755 flops for my db's, so using extensive storage isn't really an option. There's no delay after the db is loaded. I would guess the db's are loading in 10 to 15 seconds. There isn't any delay other than a few seconds when I use the bot trainer.

I do know what you're talking about. I have tried a full save in Pio and yes, a 50bb BTN vs BB SRP file is 1.26GB. But as far as I know, GTO+ doesn't have an option to save the full tree. And that isn't even a required condition for the feature suggestion that Scylla is commenting on. As long as people use extensive storage for entire databases, having the drill decision over database option should not be a problem. Fully stored turn data is enough. River recalcs take <1s. That kinda wait time is practically nothing.

Ah. Just noticed that you use 1755 flops. Extensive storage obviously not an option then. Isn't it a bit of an overkill though? 163 flops is enough to get very good estimates of overall flop frequencies and EQ/EV. Beyond that, there probably isn't much of an advantage with using 1755 flops. Sure, you will have some specific spots that might not be represented in the 163 subset, but you can just run individual sims for those as and when you need. If you have a system that's capable of running databases on 1755 flops in reasonable time frames, then solving spots individually can't really be a hassle. You'll be able to cut down a lot on solving time overall, and if needed, can solve some more complicated trees instead.

My mistake - I half read the post, I thought you were asking for full saves.

I solve them all on a server. I play spins so it isn't a big deal to crank out a 1755 flop subset, except for bvb limped pots, those take forever.

Could you add the customer filter creation tool from flopzilla pro to gto+?

Ok, I will consider it for future releases.

Its time to upgrade PC, without 32 GB RAM I wouldn't start anything.

What does the number inside the circle that goes up to 100 when I choose a turn card represent?

It's a rough estimate of the progress of the calculation.
The value 100 means that the calculation is complete.
So it's comparable to progress bars in Windows.
When the bar is full, the calculation is done.

Hi Scylla, potential feature suggestion - or rather, expansion of a current feature. When building trees by street there is the option to add or go all in if stack size is less than X% of pot. As far as I can tell, though, there's no way to include BOTH those options. If I want to build a tree that includes an all-in option if a shove is less than 3x pot, but I also want to have the only option be all-in if shove is less than 3/4ths pot, I have to do that manually through the edit tree option.

My request/suggestion would be to split these into two options.

OK. Let's say I stop the calculation when the number is small.
What's the biggest dEV possible?

Ok, I will consider it for future releases.

The default value is 0.5%, which is far beyond what is humanly possible.
However, the same probably applies to even a value as high as 10%.
So which value you'd like to use would be subjective; there's no absolute rules for this.

Hey Scylla,

I think this has been asked previously - but as of now there isn't a way to look at overall frequencies for different lines for an entire database (so on the flop subset we choose). Your reasoning has been that since on each flop both the IP and OOP ranges at different points are completely different, aggregating them together doesn't make much sense. Which I understand. But a feature like this is very helpful to look at overall tendencies of the environment that you play in. Like, say that you know how much BB is supposed to defend overall vs BB turn cbet and river cbet, and you also have a big enough database of hands from your pool. You'll be able to make a lot of good exploitative adjustments from just having this data.

Maybe you could add it as an additional option that users have to choose specific lines for and then create the aggregate reports instead of these being pre-calculated when you solve a database since there are way too many lines to choose from and doing it for all of them could take time. The users can choose for themselves which ones they want to run the aggregations for.

What are your thoughts on this?

Does it have ability to lock strategy/nodelock(lets say: alwaysbet certain types: OESD, FD, pair, overcards) in database mode that way you could create custom strategies over group of flops easier.

As stated before, adding this data together over different trees, and over different turns is rather troublesome. These points are reached with entirely different ranges, and with entirely different frequencies. Also, some lines will have a weight of 100%, whereas others will have a weight of less than 1%. All-in-all, it involves adding data that really isn't suitable for being added.