Originally Posted by Toast91185
There is no error message that comes up and it doesn't interfere with my play in any way, slow down the program etc... It just seems to fade in and out (mostly out), for what appears like no reason. I know that is not much help. I just started a session identical stakes, and for some reason one of the tables shows my stats and the other two don't.
Could you please take a few screenshots so we can see what you are seeing? I think that will be the best way for us to figure out what is going on here.
Please submit the screenshots to our support system
and either link to your post in this thread or copy it and paste it in the description and we'll look into it from there.
Originally Posted by voxx
I'm getting a similar problem I think.
I edited the autorate rules to the same as I used in PT2 and ran them while playing today.
As you can see AgentNo9 is displaying the bomb icon which according to my rules means they are Ultra Aggressor, but hovering the mouse over the icon gives a description of Bad weak Tight which is the warning triangle icon.
I still import to PT2 as well and I only have 55 hands on this player on both PT2 and PT3. On PT2 he also shows as a bomb icon.
Any idea where things are going wrong?
There's a known issue in Beta 18 where the mouseover tooltip incorrectly displays the name of the item with priority one higher. This will be resolved in the next release.
Originally Posted by maplestar
i did 12 table multitabling on pokerstars last night and tried to test new beta 18. Unfortunately, HUD was still not stable and crushed a few times in a 4 hour session.Some tables didnt even show any stats unless i restarted PT3 over again and again. Guys, its just painful to use PT3 when multitabling on stars.
my PC is xp with 1G memory.
Could you please enable logging (check Configure --> Options --> Logging Enabled then restart PT3) and reproduce one of these crashes and submit the C:\Program Files\PokerTracker 3\PokerTracker.log and C:\Program Files\PokerTracker 3\PokerTrackerHud.log files to our support system
? Once we have the logs from the crash we will be able to figure out what caused it and rectify it for a future release.