Here's what I think:
two tables need action -> first table gets moved to grid, but actual click gets sent to the table underneath causing misclick
one table needs action -> first table gets moved to grid, actual click gets sent to the next table underneath. BUT, since the next table doesn't require action, the click gets sent there but no misclick happens since no buttons are visible.
I'm glad to see that the Action Delay is helping the problem. Please continue to experiment with that (and higher delays) and report back the results. In the meantime, I'm working on a big update which should be released soon. I will do some work on the Left Click Detection and try to make it more efficient, and we'll see if I can fix the problem.
Whats happening is that the poker client cannot keep up fast enough with SaT's table moving. I think that the client is not registering the mouse click fast enough, and SaT is moving the table right out from under it. So thats why the delay is needed, and why it was added to the application a long time ago. Probably if you played 24 tables, you would find that you would need even higher delay, since pokerstars would be really struggling to process all the information for all its tables.
No ideas off the top of my head. A problem like that is hard to diagnose since it happens randomly. It could be a number of reasons, maybe not related to SaT. You could try increasing the Engine Delay to 1000 or 1500, that might reduce the load on the whole system.
two tables need action -> first table gets moved to grid, but actual click gets sent to the table underneath causing misclick
one table needs action -> first table gets moved to grid, actual click gets sent to the next table underneath. BUT, since the next table doesn't require action, the click gets sent there but no misclick happens since no buttons are visible.
Quote:I increased the action delay to 200ms and still had the issue occasionally (about 6-7 times in 3 hours with 2 misclicks), and then tried 300ms. I think it still happened once with that setting in 3 or 4 hours of play.
So its does seem to help, but I am not sure how high I have to go to be sure that I wont have the issue.
I'm glad to see that the Action Delay is helping the problem. Please continue to experiment with that (and higher delays) and report back the results. In the meantime, I'm working on a big update which should be released soon. I will do some work on the Left Click Detection and try to make it more efficient, and we'll see if I can fix the problem.
Whats happening is that the poker client cannot keep up fast enough with SaT's table moving. I think that the client is not registering the mouse click fast enough, and SaT is moving the table right out from under it. So thats why the delay is needed, and why it was added to the application a long time ago. Probably if you played 24 tables, you would find that you would need even higher delay, since pokerstars would be really struggling to process all the information for all its tables.
Quote:I am also having another issue where SaT seems to stop working every now and then and I have to restart the program which can be pretty annoying if I am in 15 games. Any ideas on why this might be happening?
No ideas off the top of my head. A problem like that is hard to diagnose since it happens randomly. It could be a number of reasons, maybe not related to SaT. You could try increasing the Engine Delay to 1000 or 1500, that might reduce the load on the whole system.
