Quote:
Originally Posted by iPlayAAonly
Exactly that way, a few times too. It's not working at least for me, don't know about others
Could you please restart PT4, open and attempt to delete the line, then send us the PokerTracker4.log file via our support system? You can find the file by clicking File --> Open User Data Folder - it's the text file called PokerTracker 4 that is there.
Quote:
Originally Posted by iPlayAAonly
That's basically the same thing as 4bet range from HM1/HM2 right? At least it looks exactly like it from your definition
Yes, it is, but it doesn't really define a "range" (a collection of specific hole cards) that a player plays, hence we decided to give it a more appropriate name.
Quote:
Originally Posted by iPlayAAonly
thank you that's going to be really useful to find out what each stats exactly mean, does that mean i would be able to create my own stats "Bet vs missed CBet total IP" & "Bet vs missed CBet total OOP" using that feature? The stats is there for each street but it wont allow me to change IP/OOP on the total one :P
You could create those using custom statistics, but I'll make a note to see what we can do about allowing an In/Out of position for those Total stats.
Quote:
Originally Posted by iPlayAAonly
One of my biggest problems with PT3 was how complicated it was to create a custom HUD and popups coming from HM1 & HM2, but all of this is fixed now, took me only a few minutes to fully understand how it works and there's a huge thing that HM2 doesn't have that you guys have, we can use color ranges in our popups, thats a huge plus for me.
We're glad to hear you're happy with our improvements!
Quote:
Originally Posted by ISmellToast
Got this while playing about 14 SNGs, HUD and import were still working fine.
close and reopening solved the problem.
Unfortunately that error appears to be cut off. If it happens again, please attach the PokerTracker4.log file to a support ticket on our website and we'll look into what is going on here. The log file always has the full error and unfortunately since the errors are so long, the screenshots often do not.