I think without tracking software this becomes a rather hard task. Ideally you would use tracking software to see how you perform historically in certain spots. Someone else's stats would not necessarily be as helpful here. Of course, with tracking software you could just check your performance with your range in preflop spots. That being said, I can consider a feature for later versions that figures out this information by running a large number of random flops through the solver and providing a custom list as output. It would be interesting to see what that would lead to.

Ok, I have made this change and expect to post an update later today with smallish fixes. I'll post here when it's up.

Thank you very much!

I'm doing a tree starting on the flop, in this case the turn action starts with the SB instead of BB, I think it is a bug?

Also, it seems only one bet size is allowed per decision using the equilibrium solver, can you confirm? Any plans on adding multiple bet sizes in the future?

This is typically the result of:
1) Entering a tree
2) Changing bet/stack sizes so that the tree no longer makes sense
3) Possibly making some more edits and then changing bet/stack sizes again

The problem with changing bets/stacks after a tree has been created is that often, players are suddenly all-in. Or they're not all-in anymore. Or that a raise is to X is no longer possible because the amount to call already exceeds X. There's all sorts of issues that can occur when changing the situation in a tree retroactively. The software tries to compensate, but in some cases it's simply not possible to do so. It's not that it fails, or that it's a bug, the software was simply asked to do something that can not be done.

We have tried to find ways to compensate for impossible values being entered, but in the end it turned out that there's hundreds of possible ways to do so. A solution here would have been to not allow editing bets/stacks after the tree has started, but due to the open-ended nature of the software we decided to keep those options in and leave it up to the responsibility of the user to not make changes in bets/stacks that would cause conflicts.

That being said, ideally you should just enter stacks when starting the tree and not edit them after the fact. As for bet sizes, if you want to edit them, then just don't edit them so that they conflict with the tree as it's already been entered.

Finally, it's probably better to use the wizard to create your tree instead of entering it by hand.
It's a lot faster, and will ensure that everything is there that should be there.

At the moment we offer single bet sizes.
As for plans, generally speaking, if new features are added, then those will be made public when they are released.
There's no prior anouncements.

Ok, I have posted the update.

Thanks a lot! Now it works great.

Hey scylla currently trying to figure out how to use the equilibrium solver (the ying yang button), just had a few questions (also i watched all the videos/read through the manual still super confused)...


-Does the equilibrium solver in CREV work the same as PIO like the equilibrium solver is range vs. range/nash calc's right like it does all the MDF stuff for you?

-What do i put in for dEV or deviation, actually i'm sort of confused on what this means as what it does so yeah sort of ambiguous to me?

Do you think your programing technique of using such a small amount of memory can one day be applied to writing an advanced pre flop solver?

Yes, it's exactly the same thing.
And the results appear to be the same as well (I haven't seen a difference yet).

A reasonable value would be "0.5%", meaning 0.5% of the pot. dEV is the maximum amount either player will be able to improve on the GTO strategy that was found, even if that player were to play optimally.

Generally speaking, if new features are added, then those will be made public when they are released.
There's no prior anouncements.

locked only fold
analyze tree ranges> "accept changes"> and unlock raise and bet (locked only fold)
on 3.2.9 it work fine

Hi LJ,

When editing actions with the analysis tool the entire selection needs to be locked, given that any edit involves changes to all of the actions. It was actually a small oversight in earlier versions to allow partial locking for edited equilibrium ranges.

Cheers,

Scylla

Hi. This might have been addressed already, sorry if so.

I don't want the card matrix to be shaded according to frequency. That makes it very hard to compare the EV of different lines.

For example, with 100% weight:



With 50%:



With 1%:



Can I turn this off somehow? I just think it makes things very hard to see and compare, don't see any upside to it given how I use the software.

Thanks!

Thanks.

You answer this about 2 months ago, do you had look at this a bit? Do you think it's possible?

From what I can tell, it would be really complex to do this. Ideally, if you want to fix villain's strategy in some way, then you should just enter that part of the strategy and lock it.

Cheers,

Scylla

If you want to compare the EV for different lines, then the easiest way to do this would be with the analysis tool (press SPACE to bring up the analysis tool) and press F3 for EV mode. I don't really see the problem with the screenshots you've posted though. Can you perhaps elaborate a bit? Do you mean that the numbers in it are hard to read on your screen? Because I don't have any such problem on any of my monitors/laptops.

The number of threads seems to be capped at 32, any way to increase this?

That cap is there to prevent inexperienced users from entering a number like, for example, 1000, and then running into issues which are then hard to pin down for support. You can override the cap by entering overrideXX, where XX is the desired number of threads. So, for example, you can enter override64 for 64 threads.

Great, thanks.

How do I put weights on individual hands in the postflop condition editor text input?

Is there a release for any Linux/Unix platform?

The text input does not include weights at the moment.
I can look into it for later versions, but right now it's not there.