Hello all,
Today we are updating the solver and the viewer. You can read about details on our
blog.
The biggest change is that it's now possible to build trees with multiple bet sizes. Amount of bet sizes is for now limited to 10 per decision node. Games from turn/river should be very manageable with as many bet sizes as you wish. Here are some examples of flop spots which are solvable:
0)up to 4GB of RAM:
-almost every sensible turn/river game with 2-8 bet sizes, those are small and fast to solve;
1)up to 8GB of RAM:
-100bb single raised pot without flop donkbet and 2nd river sizing added (on all rivers)
-100bb 3 bet pot with 2 sizes everywhere (say 40% and 67%)
-25bb tree with 2 cbet sizes and 2 river sizes everywhere
-CAP tree with all-in added everywhere
2)up to 16GB of RAM:
-100bb single raised pot with 2 river sizings (every river)
-100bb single raised pot with one flop sizing but 2 turn and river sizings (no flop donk bet)
-as above but with donkbet but only one sizing if there already was a raise
-25bb tree with 2 bet sizes everywhere
-CAP tree with 3 bet sizes everywhere but without flop lead OOP
-limit holdem with cap 4 (standard) without OOP flop leas
3)up to 32GB RAM:
-full 100bb tree with 2 bet sizes everywhere (for example 40% and 70%)
-full CAP tree with 3 bet sizes everywhere
-full limit Holdem spot with CAP 4
How it looks like:
1)setup (for CAP with 2 bet sizes everywhere)
2)browsing:
3)Toy river game:
The schedule for updates:
-edge customers have their download and notifying email already delivered
-pro users can expect it later today
-basic users can expect the update tomorrow
-free version will be updated later this week; multiple bet sizes (maybe a bit limited) are expected to make it to there as well
Schedule for near future:
-add some missing basic functionality of the solver/viewer (including setting/locking strategies, range analysis, expanding chosen nodes etc.)
-optimize speed/memory so all above mentioned settings go down at least one category down in memory requirements (and hopefully one generation of CPUs as well but that's a bit more problematic)
Stay tuned!
Last edited by punter11235; 04-05-2015 at 09:16 AM.