It's not the case because someone called the first all-in and we do not know his cards. Pretending hands that called the all-in and later folded do not count in the hand at all ends up introducing a bias. I agree it's less obvious in this case but a more obvious case is this: Imagine A goes all in a...

We do not calculate adjusted equity in any situations where a player called an all-in raise and later folded. To do so would introduce a systemic bias against you in these statistics.

Please restart PT4 using the logging enabled link on your Start Menu, reproduce this problem and then report it via our support system with the log file - that will help us figure out what is going on here and get it fixed for you. You can find that file by clicking File --> Show User Data Folder in...

That's odd but trusting your VM's IP should be fine.

(1) If you have the SQL skills to define things as needed in your own schema you are welcome to do so. It's definitely beyond the scope of our support here. (2) There is a maximum of 1600 columns per PostgreSQL query. In effect this means the cache and any queries cannot exceed requesting 1600 colum...

Please restart PT4 using the logging enabled link on your Start Menu, reproduce this problem and then report it via our support system with the log file - that will help us figure out what is going on here and get it fixed for you. You can find that file by clicking File --> Show User Data Folder in...

Did you play a session on or around midnight?

When you look at your sessions without filtering in the Sessions report do they have the right date and time?

Use the "Call PF 2Bet" stat and you can set the position to big blind in the Item Properties area and that should get you what you want.

Please create a support ticket here and let us know what payment method you were attempting to use and we will work with you to get your purchase processed.