In PioSOLVER defaults are good.
On the server:
-switch off energy saving settings
-turn off all "online scans", "online file shields" and all other things which scan your files for viruses without prompting. Firewalls etc. are fine
-go to task manager, run the solver and see if the CPU usage is in 80%+ territory

Look into:
Tools->Configuration->Notification (at the bottom)

You can choose a system beep or a custom action. If you put a youtube link there for example it will open once the calculation is finished.

I have one question : How do you use PioSolver to determine the optimal betsizing for your range ? In the settings you are asked to enter your betsizings (like oop bets flop 50%, 75% of the pot etc...).
What I would like to know is which one is superior (has the most ev for our whole range- not just hand by hand) ?

Example : BTN vs BB on QJx, Is a bet size of 50% or 70% the most EV+ for my range ?

I think I've just answered it in the Skype group but here it goes again:
-this is in general impossible to do without re-running trees with different sizings and comparing the EV
-if you were to choose one bet size it can still have worse EV than 2 different sizes
-usually the EV differences between flop sizes is miniscule so while it's a fun exercise to run some trees with 35%-50%-75%-100% bet sizes and see what those differences are it's not where your edge is going to come from (although it's useful to run with various sizes to see how defending range changes and against what sizes your opponents are likely to make the biggest mistakes)

If you run it on several flops you will likely start developing a feeling for what the solver likes, in general it likes way smaller sizings than what used to be popular 1-2 years ago.

What is the difference between piosolver pro and edge?

-edge version comes with the preflop solver
-edge version supports unlimited number of cores (well, 128 threads at the moment), pro supports up to 12 (enough for every home CPU)
-edge version comes with optimized compiles for modern CPUs which are about 15% faster as of today

Both pro and edge versoin come with 2 activations (you can use them on 2 machines).

Hey there,

I have another problem when I try to run a script. So I set it up, put in the parameters etc., click generate, it generates the script, but when I click run, nothing really happens. It just stays like in the screenshot here: https://gyazo.com/c3dca7c848517f4ed3cb8a2aca264ff3
I'm running PioSolver.exe as admin already, didn't help.


Thanks for any advice!

The basic version doesn't support scripts, that's the only functional difference between it and the pro version (the other being 2 activations and supporting more threads).

I some how missed this post, this is exactly what I was referring too. Thank you!

Noticed that, when scripting, if you just run one script, you don't need to create the destination folder, but when you run a script that runs multiple scripts, you have to create the destination folders beforehand, else it will fail to dump the calculated trees and gives an error (can't find folder or something like that). It would be nice if this were fixed.

Also when running scripts within a script, the weights get discounted when doing multifile aggregation reports afterwards

This is not a bug but a design decision which I admit might be annoying at first.
I am adding this to to-do but it's more likely that script combining capabilities are added to the viewer than that the solver starts creating folders (it's OS specific call and I try as much as possible to limit OS specific code in the solver itself).

Multifile aggregation reports only makes sense on the saves created from the same config. Once the betting structure is different they won't work.
If you want to do aggregation only form one of them, then put the script used to create those trees in the same folder as the saves and try again. It should see the weights now.

I see. When you run only one script, it automatically creates a duplicate script in the destination folder. Might be nice if it did this when running scripts within a script as well.

I find myself wanting to specify different raise sizes for IP player vs an OOP bet and donk (because donks will generally be much much smaller than a bet, so the appropriate raise size will also change). The only way to do this right now is to use the add extra lines function, but then I have to do it for every single flop line that ends in a call, which is quite tedious. Would be nice if IP had 2 boxes for raise sizes - one for bets and one for donks.

ooooooh oooooh you've got me excited now

If you use multiple betsizes you don't need to specify a line separately for all of them, adding:

check, bet, call, bet, raise 3x
will add raise of the size of 3x in lines containing all bet sizes on the flop.

So that would be one line and another to remove an old betsize from that.
If you are interested in changing the raise size in other lines (donk after being 3bet) then maybe "use only one raise when there was a raise before" checkbox is appropiate as the stacks are already close to allin there so there shouldn't be much need to use varying raise sizes there (but again, you can just type the lines).

I hope that helps

So if I understand this correctly, just writing bet (or raise also, I assume) with no specification of size means any betting line, and therefore "check, bet, call" means after any bet is called on the flop?

Yes, although removing bet/raises is a bit tricky when all-in is added as a separate action. If you run into any problems there, let us know.

You can try those things without investing much time by building the tree and browsing it without solving. This way you can see how changing various options influence the tree as building/rebuilding should be pretty fast.

hi punter, i have pio pro and im curently using a rented Xeon E5-1650v3 Cores/threads: 6c/12t. Should i change it to Xeon 2x E5-2630v3 Cores/threads: 16c/32t? I mean the price jump is like +30%, but I understand that pro version uses only up to 12 cores, so will the solving be at least 30% faster?

It should be around 30% faster - yes.

Hi,
I had some scripts running. My problem is that the Solver stopped at Exploitable for~0,9.
What are the right accuracy settings that the solver stopped at ~0,2.

Currently the settings are at 0.02, but this does not seem to affect the script.

Thx

If I buy Piosolver Pro or Piosolver Edge can I request a refund for it up to a week?

When you are generating a script there is a field where you input accuracy in % of the pot.
Notice that the solver's output is in chips so it's going to be a different number (for example 0.2 chips in a pot of 70 is 0.28% of the pot).

Our policy is to grant refunds for one week with no questions and for 2 weeks if we the product wasn't used (or just registered very late and the refund was requested shortly after that) or there is some kind of other very good reason . That is as long as the license terms weren't broken.
Refunds are a bit of a pain from accounting/taxes point of view in our country though so they are not a system to try a software and see if you like it (for that there is a free version). I would appreciate if you don't use them for the purpose. I consider it abuse.

Hi:
¿Why when i try to put in hotness dont appear nothing? http://prntscr.com/d4cma6 ¿In what part of the three should appears the hotness?

Thanks

Hotness will not appear if you have a small save and you are browsing a street which is not in the save. The reason for that is that hotness requires EVs for all cards and therefore requires recalculation of the whole tree (which is very time consuming). It will work as long as the whole tree is in memory or if you for example on flop+turn saves as long as you are not on the river.

Hello, I was trying to find out if I would be able to do some work in PIO. But I think I missunderstand how PIO works. I will ask question connected to preflop tab, basing on example. Sping&Go, blinds 20/10, BvB action, 500 effective stack. SB raises to 40, BB 3bets to 100, SB is all-in for 500, BB? If we dont change SB shoving range compared to opening range, it shows that BB has to call very wide. Should we change SB range while analyzing BB calling range against SB shove? How PIO take folding combos into the account during calculations? For example, when SB wants to calculate shoving range against BB's 3bet? I am using free version of PIO, maybe I am not able see all options.