Re: iWitness v2
This is a problem caused when the order of the tables is updated by Party Poker when iWitness is trying to open tables.
When iWitness strarts to open tables it observes tables in the PartyPoker table list and their positions in the list (line number). It then goes out to open them. Unfortunately the table list is always changing (new tables opening, being sorted etc), and so often after a while the table names and their positions no longer match up. When this happens this error appears in your log:
########################Target didn't match table_name
You will notice that iWitness starts skipping over games that fit the criteria that you set, often accompanied by a repeated error sound.
There is no fix for this problem yet, but there are a few ways to make it much less severe.
1) Turn off safe-mode (Right click on ahk icon at the bottom right hand corner of your screen, go to options and then turn off safe mode).
2) Sort the table list by name. Sometimes the tables are sorted by information which is always changing (H/hr, avg pot etc), thus the order of the tables is always being changed to sort by this statistic. Sorting by name reduces this problem.
3) Use the autofilters. Autofilters decrease the number of tables in the list, and so eliminate the effect of changes made to irrelevant tables. Specifically, apply the 'seats per table', 'DP or no DP', 'jackpot/regular' and the relevant limits to shorten the list to only the games that you want to mine (or as close as you can get). This also has the added bonus that when the skipping does occasionally occur, iWitness does not waste time scrolling through irrelevant tables. Before you start iWitness, apply these filters to the limit that you want to mine, and click that limit in the Party Poker drop down box on the left to select it. Do not use the open seats/full table filter, because as tables fill and unfill they will constantly be added and removed from your list, stuffing up your order.
4. Update your code. The code at the OC site now includes modifications which mean that it only auto refreshes tables that no longer fit the player requirements that you have set. With much quicker autorefreshes now, there is much less chance of the problem occuring.
Hopefully this works for you [img]/images/graemlins/smile.gif[/img]. Perhaps this thread could be edited and stuck somewhere, because this is a very frequent problem.
|