Either Advanced->Abort Calculation and save which saves current tree being solved no matter the accuracy or just "cancel" in the bottom right. Next time you run the job it will not attempt to solve already solved trees.

The upgrade to pio 2.0 works for all the activation that I have?

It works for 2 (for pro/edge versions).
We will publish separate pricing for additional activations in a few days. You can also contact us about your specific case.

Today we are pushing our first 2.0 bugfix.
As expected there are many bugs we were unable to find in testing or introduced making last minute fixes. Some of the changes:

1)slow tree building when rake/icm were used is fixed
2)Node-locking preflop now works
3)Crashes/nonsense results when browsing small saves on rivers are fixed
4)Some default values (timeout for recalc as well mixing threshold in GTO trainer are improved
5)Double click now opens a flop when selecting out of many in the same folder
6)Windows resizing should now be smoother (ongoing progress on this)
7)Old versions should now be visible in the installer if at least one is installed (otherwise Options->show old version)

To get the update please run the PioUpdater in your Pio installation folder.
You should be getting PioViewer 2.0.1.3 and the engine version 2.0.1

Does anyone have suggestions about content for making sure I am running sims properly? I am new to the software and want to make sure I can trust my results.

So if I want all trees in the script solved to desired accuracy hitting cancel is the only way? Then when I restart it’ll solve the tree it was working on to desired accuracy before moving on.

It's hard for me to recommend specific content. Try joining our Discord and asking there though!

It will start the one it was working on from scratch but skip over other ones.
You can also run PioViewer with the console visible and mark something on the console. It will stop the process (it's a somewhat unfortunate Windows feature which might be useful in this case).

Is there a way to make Piosolver 2.0 not switch to Postflop Tree Building and Calculations when I am looking at Browser and select a different flop from the same folder that the sim is in? It's a bit annoying having to always click it back

Yes there is!
Tools->Configuration->Behavior->Other->"Default action after load tree"

Thank you!

I just saw the new video, about the trainer are the solutions included? Can I upload my own hands? Can I choose the sizing post flop?

You can use your own solutions. There isn't really anything to upload (it uses local files).
As to sizings: it uses sizings in the solution.
We don't have any solutions for the trainer available right now but we may run a server at some point to prepare some spots. It's not for the near future though.

So if in my sim I have 2 sizings when I use the trainer I’ll have 2 sizes?

Yes.

Just purchased v2.0, running Edge v2.0.1.5, but can't get the Viewer to connect to the solver. I've followed every recommended step, rebooted my computer, updated Windows, etc. Failed to connect automatically every time.

Still getting this message when trying to connect to solver after loading the viewer:

When I do run the .exe file, it briefly loads the solver window but without the same basic info appearing (my email address, Piotr's name, etc), and then it disappears.

Any advice?

Hi all!
I have been playing around with the new GTO trainers for a while and got this error message.

"An error has occurred while processing your request.
The program has failed to provide a helpful error message.(NPE)
If you would like to report this bug, then please send pioviewer_error_log.txt to the support."

This happened when I was adding a new pack.
I had no problem until I tried to add 11th pack.
It would be great if someone can help me solve this error.
Below is my error log file.
Thanks in advance!

#Type#NoLimit
#Range0#77:0.125,66:0.25,55:0.625,44:0.75,33:0.875 ,22,ATo:0.25,A9s:0.125,A9o:0.75,A8s:0.5,A8o:0.875, A7s:0.75,A7o:0.875,A6,A5s:0.125,A5o,A4s:0.375,A4o, A3s:0.625,A3o,A2s:0.75,A2o,KJo:0.5,KTo:0.75,K9s:0. 375,K9o:0.75,K8s:0.875,K8o:0.75,K7s:0.875,K7o:0.75 ,K6s:0.5,K6o:0.875,K5:0.875,K4s:0.875,K4o,K3s:0.87 5,K3o,K2,QJo:0.875,QTs:0.125,QTo:0.875,Q9:0.75,Q8s :0.875,Q8o:0.75,Q7:0.875,Q6,Q5s:0.75,Q5o,Q4:0.75,Q 3s:0.875,Q3o:0.125,Q2s,JTs:0.125,JTo,J9s:0.5,J9o:0 .875,J8s:0.625,J8o:0.75,J7s:0.75,J7o:0.875,J6s,J6o :0.875,J5s,J5o:0.125,J4s,J3s,J2s,T9s:0.375,T9o:0.7 5,T8s:0.375,T8o:0.75,T7s:0.5,T7o:0.75,T6:0.625,T5s ,T4s,T3s,T2s,98s:0.125,98o:0.75,97s:0.25,97o:0.75, 96s:0.5,96o:0.875,95s:0.625,94s,93s:0.75,92s,87s:0 .125,87o:0.875,86s:0.125,86o:0.75,85s:0.75,84s:0.7 5,83s,82s:0.875,76s:0.125,76o:0.875,75s:0.375,75o: 0.875,74s:0.75,73s:0.75,72s,65s:0.125,65o:0.875,64 s:0.5,64o:0.125,63s:0.75,62s:0.875,54s:0.125,54o:0 .875,53s:0.875,53o:0.125,52s:0.75,43s:0.875,42s:0. 875,32s:0.875
#Range1#AA,KK,QQ,JJ,TT,99,88,77,66,55,44,33,22,AK, AQ,AJ,AT,A9,A8,A7,A6,A5,A4,A3,A2,KQ,KJ,KT,K9,K8,K7 ,K6,K5,K4,K3,K2,QJ,QT,Q9,Q8,Q7,Q6,Q5,Q4,Q3,Q2s,Q2o :0.375,JT,J9,J8,J7,J6,J5,J4s,J4o:0.875,J3s,J3o:0.1 25,J2s,T9,T8,T7,T6,T5s,T5o:0.625,T4s,T4o:0.125,T3s ,T3o:0.125,T2s,98,97,96,95s,95o:0.875,94s,93s,92s, 87,86,85,84s,84o:0.125,83s,82s,76,75,74s,74o:0.125 ,73s,72s:0.875,65,64s,64o:0.875,63s,62s,54,53s,53o :0.25,52s,43s,42s,32s
#Rake.Enabled#True
#Rake.Fraction#0.045
#Rake.Cap#1.5
#Board#As 3d 2c
#Pot#48
#EffectiveStacks#976
#AllinThreshold#67
#AddAllinOnlyIfLessThanThisTimesThePot#500
#RemovedLines_2#check, check, bet 66, call, bet 29\\0\\0check, check, bet 137, call, bet 29\\0\\0check, check, check, bet 66\\0\\0check, check, check, bet 50, raise 4.5x, call, bet 29\\0\\0check, check, bet 66, raise 4.2x, raise 4.5x\\0\\0check, check, bet 137, raise 2.5x, raise 4.5x\\0\\0check, bet 29, call, check, bet 66, raise 4.5x, call, bet 29\\0\\0check, bet 29, raise 4.2x, call, bet 66, call, bet 29\\0\\0check, bet 29, raise 4.2x, call, bet 137, call, bet 29\\0\\0check, check, check, bet 137, raise 4.5x, call, bet 29\\0\\0check, bet 29, call, check, bet 137, raise 4.5x\\0\\0check, bet 29, call, check, bet 137, raise 3.5x, call, bet 29\\0\\0check, bet 29, raise 4.2x, call, check, bet 66, raise 4.5x\\0\\0check, check, check, bet 137\\0\\0check, check, check, check, check, bet 137\\0\\0check, bet 29, call, check, check, check, bet 137\\0\\0check, bet 29, raise a\\0\\0check, bet 29, raise 4.2x, raise a\\0\\0check, bet 29, call, check, bet 66, raise a\\0\\0check, bet 29, call, check, check, bet 66, raise a\\0\\0check, check, bet 66, raise a\\0\\0check, check, bet 137, raise a\\0\\0check, check, check, bet 50, raise a\\0\\0check, check, check, check, bet 66, raise a\\0\\0check, check, check, check, bet 137, raise a\\0\\0check, check, check, check, check, bet 66, raise a\\0\\0check, bet 29, call, check, check, check, bet 66, raise a\\0\\0
#ExtraLines_2#check, check, bet 66, raise 4.2x\\0\\0check, check, bet 137, raise 2.5x\\0\\0check, check, check, bet 50\\0\\0check, bet 29, call, check, bet 137, raise 3.5x\\0\\0\\0\\0
#FlopConfig.RaiseSize#4.2x a
#FlopConfig.AddAllin#True
#TurnConfig.BetSize#66 137
#TurnConfig.RaiseSize#4.5x a
#TurnConfig.AddAllin#True
#RiverConfig.BetSize#66 137
#RiverConfig.RaiseSize#4.5x a
#RiverConfig.AddAllin#True
#FlopConfigIP.BetSize#29
#FlopConfigIP.RaiseSize#a
#FlopConfigIP.AddAllin#True
#TurnConfigIP.BetSize#66 137
#TurnConfigIP.RaiseSize#a
#TurnConfigIP.AddAllin#True
#RiverConfigIP.BetSize#66 137
#RiverConfigIP.RaiseSize#4.5x a
#RiverConfigIP.AddAllin#True
Currently selected node: r:0

If your CPU is old (older than Ivy Bridge generation of Intel CPUs) then please copy PioSOLVER-edge-oldCPU.exe from CustomBuilds folder to the main one and try connecting to that (by going to Solver->Connect

If it's not that please email support@piosolver.com with your license key and a screenshot with all the files visible in your Pio installation folder.

Please email support@piosolver.com and attach the following files:
pioviewer_error_log.txt
pioviewer_log.txt

from your Pio installation folder.
This will make solving it much easier for us.

Hi Punter,

I would like to report some weird behavior I found with pio2.
I was running a script for bvb srp to accuracy of 0.5%.
Most of the boards were saved to desired accuracy (I didn't check all of them) but I noticed that one of the saves was solved only to ~2.5% accuracy.
I decided to manually solve this board and it did reach 0.5% acc but It was showing weird results that don't make any sense and cannot be true.
I then used the exact same tree config to solve it with pio 1.10 and was getting different results.
I can send you the tree config file If you wish to try out yourself but here is screenshots of a river node and ev for a specific hand:

https://gyazo.com/19cdaa20c4ab1009c0010d87396c9495
https://gyazo.com/04e3c6f713991db84d27d98ae75c67a6

Besides that issue I would also like to report about rollback in exploitability while solving.
I saw a few posts above that you replied about this and said it is normal with new alg but I noticed in my case huge jumps f.e desired exploit accuracy was 0.3 chip so I would see it solve down to 0.7 and then jump up to 9 chips and after that it would go back down until it reaches 0.3. Is this still normal? Some trees in my script were done in 5 minutes and others in 15.

Please always include configs. Either pm/email or you can include them here. Just use [ code ] [ /code ] tags so it doesn't take all the screen real estate. Like this:
[ code ]
config here

[ /code ]

without spaces inside tags it will look like this:

This happens with the new ald. The old one (optimized to be about 2x faster in 2.0) is more stable but doesn't behave as well around 0. If you are solving big trees to accuracy like 0.5% the old one might be a better bet.

I Sent you an email with the tree config

Thanks, I will look at the tree.
Can you please point me to what you find to be suspicious about the results?
Everything looks normal to me on the screenshots.

Look at first screenshot using pio2 and look at the EV's of A5o combos facing the river bet, the pot is 175, some combos have 0 EV and some win the entire pot which obviously does not make sense

btw this is only when facing the 75% river bet. vs the other sizes the solution looks correct

The thing is that this is actually correct at very good accuracy.
The thing about those Ad5x combos is that:

1)They are not in range at this point
2)The calling range (after raise to 240 for example) has almost exclusively Ads in it

Look:
https://gyazo.com/32100e1ab87055f38964b14f4b569333

The whole calling range range:
This makes Ad an idea card to raise on this river. You can see using new "Frequencies VS one combo feature:

https://gyazo.com/0df6a1655eb9a91d40ffbc3329f69a17

While against the whole range it looks like this:
https://gyazo.com/8d8953aa0317661ec757aa13196c9cf9

Things like this happen against very infrequent actions (in this case bet75 which is only chosen 1.09% of the time at 0.05% accuracy and most likely even less frequent that that if we run it for longer.
You will see that against a bet size that is chosen with bigger frequency no such anomalies occur.

You can ask if in such case Ad5x hands can't arrive at this point and bluff every time vs a bet75. This doesn't work because:

-betting on the turn with Ad5x has higher EV
-bet75 happens very rarely (around 1% of the time)
-It happens even more rarely against Ad5x (0.44% in my calculation)

How come when I run scripts, half the time the script will run, it will show it solving to accuracy, but it is not placing the solved boards into the "Saves" file? I notice this happens half the time. It just sits running the script for days on end, and no boards appear in the Saves file. Then I start a new script, and the boards will appear in the saves file.