4b/f stat
Posted: Tue Jun 05, 2012 7:56 am
Hi,
i allready had the problem in this thread, and send an support ticket with this conversation. But still got the same problem, that my custom stat doesn´t work.
I have the latest version of PT4 and of cause allways updated the database.
Can someone help me?
i allready had the problem in this thread, and send an support ticket with this conversation. But still got the same problem, that my custom stat doesn´t work.
I have the latest version of PT4 and of cause allways updated the database.
Can someone help me?
Message left on Apr 18, 2012 1:39PM
The fix is related to importing hands, so the update will not fix an existing database - you will need to re-import your hands. Since this will affect a number of hands throughout your database it will probably be best to create a new database to import into.
(Note: re-importing into the same database will not help because existing hands will be rejected as duplicates.)
WhiteRider [PokerTracker Support]
Message left on Apr 16, 2012 11:55AM
pokertracker.comHello,the problem is still the same... the 4b/f stat doesn´t work Can u help me in this case?Thanks in advance!
mannue [mannue@web.de]
Message left on Mar 9, 2012 1:23AM
(This is an Automated Message)
The issue reported in this support ticket has been marked as resolved by the PokerTracker development team. Please download and install the newly released version of PokerTracker 4 which should resolve the issue:
PokerTracker 4 - Download
If you continue to experience the same issue that was reported, please replicate the issue with the new version. Then follow the link at the top of this email back to the PokerTracker website to reply and attach your updated log file. Our development team will then further investigate the issue.
Best regards,
PokerTracker Support
PokerTracker Support [g.pernelt@orange.fr]
Message left on Feb 19, 2012 5:48PM
Sorry for the delay getting back to you - we've had a lot of support requests with the expansion of the PT4 Beta program.
Thanks for the examples - it seems that one of the database fields used by this stat is being set incorrectly, but the stat expressions themselves are fine.
I have reported this to the development team to be fixed.
Thanks for bringing this to our attention.