This data is available in the engine, and it's possible for us to display it. However, the problem is that when moving beyond the first decision, this data is not particularly useful. The reason for this is that each data point will have been measured under different circumstances (different frequency and range from player 1). So in other words, in each scenario IP will not only be facing a different turn/river, but also a completely different range from OOP. It's possible for us to ignore this, and plot the data anyhow, but there really is no meaning to the resulting table/graph. So, we can consider adding it for later releases, but at the very least for now, it has been left out for this reason.

This would only work if both the range and flop were exactly the same between the trees. We can consider it for later releases, but the problem here is that it will be a feature that will only work under very specific circumstances.

If I understand you correctly, then this is already available.
In "Aggregate" mode, click on the tree icon.

We have set a limitation of 16 threads to protect inexperienced users who may enter a very large value and then run into issues that are hard to track down. It's however possible to enter a higher value with the code XXoverride. So, for example, to get 32 threads, enter the code 32override.

Ok, can you send a savefile to support please?

Yes, in order to do this, just create a database of all 1755 flops.
You can use the "Add X random flops" button for this.
Please note that the program may freeze for a few seconds while randomly drawing large numbers of flops.



For more information on database mode, please watch the second video here: www.gtoplus.com/videos

Sent.

Thx for help.

But still I can't get turn and river data. For example, OOP cbet - IP call, turn card comes, OOP cbet again then what is IP's calling freq for each turn card?

For now we can get OOP's turn cbet freq for each turn card, but still can't get IP's calling freq in database mode. It takes too much time for doing it manually.

The data for each turn and river cards are very useful for mass data analyisis. People around my poker community also want that function. Some one who enjoys GTO+ very much, had to buy another solver for that function. I think if that function is available, GTO+ would be more powerful tool.

Thanks. 1 other question. I have my Z: drive mapped to a local network share (192.168.1.x) and for some reason, GTO+ doesn't allow me to save anything there. In fact, the Z: doesn't show up at all. It shows fine in Windows Explorer. Is there something I need to enable for this?

Hi Scylla,
Just got CardrunnersEV. Magnificent piece of software! Just playing around and need to query something with you.. How do I send a screenshot..?Can't copy/paste. Can't attach.. Must be missing something obvious!

Cheers

Dave

This data is available in the engine, and it's possible for us to display it. The whole problem however is that the deeper you go down a tree, the less useful aggregate data becomes. When you're as deep as the turn, adding the data from hundreds of trees, and averaging over 49 different turn runouts for each individual tree, any analysis becomes really debatable. I'm happy to consider it for future releases, however, for the moment we have left it out for this reason.

No, whatever the issue is here will be related to the operating system.
It's not internal to the software.

In the past I myself always used PhotoBucket for posting online pics, and as far as I can tell they are still available. There are many alternatives though. Other than that, if you're having trouble posting screenshots, then it's of course always also an option to just mail support and add it as an attachment.

What's the best way to export (weighted) ranges from GTO+ and import them to Flopzilla? Is an import to Eqilab also possible?

Thanks.

All calculations in GTO+ are done internally. We have decided to not have to rely on manually exporting to external software for this, but instead offer a point+click system that performs almost any calculation instantly. Manually exporting to external software is a rather bulky process, with a lot of internal calc data missing.

Then it would be really nice to be able to visualize the weighted preflop ranges in some acceptable way. Sharing weighted ranges in form of a jpeg with others is impossible with the current visualization format.

I need to manually build the ranges in other software for this purposes. Would be really nice if this could be handled in a future release. Maybe a good starting point for the development would be the visualization of weighted ranges in piosolver.

Yes, I understand that, but it would be nice if we could analyse each turn (or river) for each decision point (betting frequency, size, EQ and EV) and if there was a possibility to export this data. It doesn't matter if this data has to be calculated on the fly, but then I would at least have all turn cards in one chart. ATM I have to do this for each turn card separately and it costs a LOT of time.

OK. As it happens I worked out what was going wrong, and no further questions.. Having worked in IT for many years, I do think it is a fantastic piece of software..!

Where should i send the save file? I can only see a box on the contact area on the site, no where to attach anything. Is there an email or?

Even so i believe the problem lies in the building of the tree. If i pick smaller flop and turn sizes it auto tries to get in the rest on the river as shown in the attached pic. Do i change this by just bringing down effective stacks to the amount i want to bet combined?

https://imgur.com/slJ7bZF

I'm using the trial on the Td9d6h flop. I'm having trouble understanding if the amount of threads is just what the program uses because of my computer or if it's preset. It was at 4 threads, I changed it to 8 threads and solved a really simple flop that was 0.8 GB and it took 4.5 minutes. Can I bump it up to 16 threads? Just want to make sure it won't fry my computer

Trying to see if my computer is good enough.

Ok, I will consider some other approaches for later releases.

This information is already available for individual trees when looking at a turn/river report. Do you mean that you'd also like it in an aggregate report, for all trees in a database combined?

Oh, I see.
Try support @ gtoplus.com

It's probably easiest if you send a savefile with instructions as to where you feel the bet sizing should be different.

If your computer's processor has 2 cores, then the settings will be defaulted at 4 threads. And if it has 4 cores it will default at 8 threads. So it's always 2x the number of cores. Typically you would expect that for one thread per core CPU usage would be 100%, but as it turns out, optimal performance will be around 2x the number of cores. Beyond the optimal value the performance will no longer increase, but will in fact (slowly) decrease.

From what I can tell, your computer's processor will most likely have two cores. The recommended number of cores for GTO+ is 4. You should however still get decent solving performance on most systems out of 2.

Your CPU can handle thousands of threads, so there really shouldn't be a problem there. There will however be no further increase in performance once CPU usage has reached 100%. The performance will in fact drop a tiny bit due to the CPU having to manage more heavy-performance threads.

I mean a possibility would be great where you can for example suppose that next street the OOP player checks and you could analyse different turn cards in that spot for the IP player, or even against a donk bet. So a database with different turn cards and different bet/check frequencies would be great to have.

Excellent job on the latest update! You have no idea how helpful that flop sorting feature is to me. Whenever I review my hands, I would solve flops and save them individually and not do an aggregate report since I was able to create my own order this way. But now I don't even have to worry about that. Now I feel like I wasted a lot of time doing so many flops this way instead of just combining them into a single database, lol. Thank you and keep up the good work!