Thursday, September 15 2011
RC4 build 6 Released
Fixed support for latest iPoker update
Fixed support for latest PokerStars.fr update
Added support for iPoker skin: PowerPoker.it

Upgraded Npgsql API from 1.0 to 2.0.6
Autowaitlist will now ignore the "# on Waitlist" filter conditions, when it comes to leaving waitlists. For example: If you have an autowaitlist filter which includes a condition "# on Waitlist (0-3)", TableScan will no longer leave the waitlist if it goes over 3
New feature: Use non-OCR PokerStars scanning method, in Configure > Advanced Settings > Sites. This feature allows you to scan PokerStars with ClearType on, and it also slightly improves the speed of opening tables and joining waitlists. It is off by default currently to allow for further testing

Fixed an issue where TableScan could take a very long time to scan when the "Give TableScan Highest Priority" option was unchecked on slower computers. This issue was caused by the old npgsql api version
Fixed an issue where TableScan would get bb/100 wrong when using Holdem Manager 2
Fixed a bug where the option "Dont allow AutoWaitlist to join or leave waitlists that I have manually joined or left" did not work with PermaScan
Fixed a bug where the option "Don't allow AutoWaitlist to join waitlists at tables where I have recently been unseated" did not work at all after RC4 b3
Fixed a bug where TableScan could skip some tables with 10 players on PokerStars
Fixed a bug where TableScan "list filters" would not filter Fast or Deep tables on PokerStars if the "Table Limit" table requirement was used
Fixed a bug where TableScan would not scan CAP NL tables on PokerStars if the "CAP NL" scan filter was used
Fixed a bug where TableScan would not get hands from PT3 when scanning 888 Poker
Fixed a bug with PartyPoker note importing that caused TableScan to try to import partypoker notes files as Pokerstars notes

I'd like to make a special note to anyone reading this about the upgrade of the Npgsql API, which is what TableScan uses to connect to your database. Apparently, the old version was causing a serious issue that TableScan has always had, where on slower computers it would not finish a scan with the option "Give Tablescan threads Highest priority" turned off. So, I would highly recommend that anyone who has had lag issues should try turning that option off in this new version.









2008-2015 Zandry, LLC. All rights reserved. | Privacy Policy | License Agreement | Affiliates