Hi Scylla (or anyone else who might know),

I run Linux as my main OS and currently have Flopzilla running wonderfully under WINE. I want to purchase GTO+ and take advantage of it's integration with Flopzilla.

Do you know if, in order to do that, I would have to install both programs within the same WINE prefix or would it be better to have them both in different prefixes?

I'm unsure how the communication between the two programs works. Do they pass files to each other on the same hard drive or do they communicate via sockets or some other networky protocol?

Thanks!

Neat! Didn't know this existed. Thank you!

Hello there, i'm Working a Lot with the gto+ solver recently and i have a question. How can i Set in the Betting tree that i want to Check my whole Range/bet my whole Range for a specific sizing and call my whole Range without having a c/r Range?

Gesendet von meinem Pixel 5 mit Tapatalk

Can you fix the tool tip where if we hover the bet size in the tree above if it's anything above 100%, it shows the correct percentage instead of just ">100%"

Ok, I'll change that.
I think that this conversion is a protection mechanism, given that in most cases anything above 100% is impossible.

I don't have any experience with Wine, so I don't actually know this.
It seems most likely to me that both programs would need to be installed in the same virtual environment.

It's probably easiest to use the tree editor and remove the unwanted actions.
In this manner, your tree will be smaller and solve faster.

Fair enough, I'll give it a go.

Just to help my troubleshooting if the need arises, how do Flopzilla and GTo+ communicate?

Cheers!

Any way to add percentage(relative to pot) to bet buttons in play against solution?

They should be able to connect to each other, as long as they are on the same computer. Because of this, it may not work if they are on two different virtual environments.

I can consider adding a toggle for this, although this is a bit of a balancing issue between functionality and complexity of the interface.

It would be nice because posflop most players have percentage buttons and if you use multiple sizes in solves adding percentages would help https://gyazo.com/101cf3bc16bb0c5da9a7cf331e864cdb

Is my GTO+ 2nd license transferrable to GTO 6+?

If not, can I purchase a 3rd license for GTO 6+?

Provided that you're not switching back and forth, I can transfer the license for you.
For this, just contact support.

We're currently setting this up.
However, in the meantime, you can just purchase a second license for GTO+.
After that, contact support and we will add it to your GTO6+ account manually.

Hey Scylla!
1. It will be good to add to the simulator the choice of the categories of hands that need to be worked out: no made hands (backdors), OESD \ FD, weak pair, 2Pair, TP, nuts etc.
2. And it would also be good to add to the Drill the current decision option, we made a raise on the flop, but this piece of the tree is played for a raiser, not a color. To work out our turn strategy after our flop raise.
3. And it would be cool to make Drill the current decision for the database, at least for the flop, in order to work out the situation against a continuation bet and against a check-check situation in the database.

Ok, thank you for the feedback.
I will consider it for future releases.

So guys i am creating this subset for BvsB 30BB and i want it to train fast. I have had other big trees where it just takes son long to calculate turn and i do not want to happen.
Problem is Save file would be 19GB big (I have 2TB memory so space is no problem)and maybe if i do it this way the file would not even open when is all done.

Anyone who also may have a very big tree and might give me some advice on what to do?
https://gyazo.com/67f98db2680e250fefeacbdbdcce4e7a

A 19GB savefile is far larger than I would consider to have any more added value from a practical viewpoint. You're probably much better off by creating smaller trees. In particular, it's really not necessary to use overly complex play on the turn/river. Single bet sizes are sufficient here. The quality of the flop play will barely be affected. Your trees will become smaller, solve faster, and require much less RAM and disc space.

I use these tree to review hands that other people play, so i like having 2 sizes in flop and turn and 4 in river. I don't mind having to wait a couple of days in exchange for never having to twitch anything in the subset again. My concern is: Would a 19GB save file even open when is completed, or will it crash or something?

Do you think that having 2 sizes flop. 3 sizes turn. and 4-5 sizes river might be harmful and create worthless trees?

Interpreting a tree with single bet sizes is already a super-human task. I don't think that all the added complexity of adding more bet sizes will lead to better results when translating the data to something that is used in practical play. Please keep in mind that multiple bet sizes will not lead to a significantly higher EV performance. When using only single sizes, your performance will be nearly identical. For that reason I would recommend sticking to single bet sizes on the turn/river. As for a 19GB file, this is far larger than anything we ever had in mind when writing the software. It really seems far simpler to work with smaller trees/savefiles.

Just to give my opinion from my own experience: I had a BvB database of 163 flops which GTO+ estimated would be ~10GB using extensive storage (but when it saved the file, the actual size on the disk was only 5.5GB). I have an SSD, and it took about 20 seconds for the file to open up. Once I had it opened, then there wasn't really any delay while browsing different trees or even on turns/rivers when using the Play vs Solution feature.

You said you have a 2TB disk. I'm assuming that it's HDD, which will take far longer than SSDs to load the database.

Re: your last question - yes, 4-5 sizes on the river are certainly overkill. Keep in mind that the more options you give the solver early on in the tree at different decision points, your tree size will grow exponentially. And couple that with 4-5 sizes on the river, you will have humongous trees that will most definitely not be worth the hassle. Since it's BvB, 2 bet sizes on the flop is fine. Give the solver 3 options on the turn: 33% (as a probe only for SB), 67%, 150% (as a cbet only for SB). Remove all donks. This alone will make your database a lot smaller while barely losing anything in accuracy.

If you want to make the tree even simpler, then just give 1 flop sizing (33%), 2 turn sizings (67% and 150%) and 3 river sizings (67%, 150%, all-in). This will do well enough.

hello, i think im doing something bad, it turns out that I put different bet sizes to gto + and sometimes get the bet sizes and sometimes its only putting one, for example I put% 30,% 50,% 75 on the flop, and when it finishes creating the tree, I get only% 75, its because gto+ wants to choose only one bet size? on that particular board?

Ok, can you send a savefile to support?
I'll have to take a look.

hi Scylla,
In Flopzilla, i cant seem to apply suit selection. any ideas?

https://imgur.com/gWYYsBv

You will need to select hands in the matrix to which you want to apply the selected suits.