Not working with new FTP update

[krumpy]

Tablescan is failing to scan with new FTP update. I get the three errors below:


Error injecting in target: Exception has been thrown by the target of an invocation.
Try resetting your FTP Lobby Widgets to Default! The Player List and Open Table/Join Waitinglist buttons must be visible!
You may also need the Microsoft Visual C++ 2008 SP1 Redistributable Package! Check the download page at www.tablescanturbo.com

[Zandry]

Ok thanks, I'm thinking/hoping it will be an easy fix and I can get an update out tonight.

[horsey21]

Hi im having the same problems with FTP as the poster above

[WhosBad]

same problem here :/

[bubu123]

+1

Pls fix it.

Thx.

[Zandry]

I've got it working again I am just trying to fix one more bug, which is when the "waitlist manager" is open then TST can accidentally end up scanning the waitlist manager instead of the main lobby. It should be ready in an hour or two

[Zandry]

Ok, I released 0.49 to fix FTP support, here are some things to note:

• I developed a method to get the # of players waiting, it works well and does not slow down the scan at all
• It will automatically click "join this table" and click "ok" on the join waitinglist popup(when you use TST to join a waitlist). You can also use the option in Full Tilt's Lobby: "Options > Always Join Individual Waiting List" to get rid of the popups, and that works fine with TST as well
• It works with the "Waiting list Manager" and "Seat Available" dialogs open (just mentioning it because this was actually the hardest thing for me to fix)
• FTP does seem to be running slower right now, this is not due to any changes in TST, you can verify just by clicking on a table that it takes about 1 second for the lobby to load the player list. Please let them know if the player list is loading slow for you because they do seem to care about that in the past when I've contacted them

• FTP seems to crash randomly when you accept a seat from the new "seat available" popup. I have not done enough testing to know if this is caused by TST or if it is just a bug in the new FTP, but I am thinking that it is a bug in FTP, because I have been testing it for the last hour or so with autoscan on a 0 interval and it has only crashed for me maybe 2 times out of 40-50+ tables that i've got the waitlist popup and joined. So be aware of that and please let me know what you find, i'll have to look into it more tomorrow

[BeaucoupFish]

• FTP seems to crash randomly when you accept a seat from the new "seat available" popup. I have not done enough testing to know if this is caused by TST or if it is just a bug in the new FTP, but I am thinking that it is a bug in FTP, because I have been testing it for the last hour or so with autoscan on a 0 interval and it has only crashed for me maybe 2 times out of 40-50+ tables that i've got the waitlist popup and joined. So be aware of that and please let me know what you find, i'll have to look into it more tomorrow

I'm afraid it looks like TST is causing the new FTP client to crash. I have been using the new search feature, but FTP would crash when the "choose seat" dialog was NOT active as well, at seemingly random times. I had FTP crash several times in the matter of a few minutes with TST running. After closing TST, FTP did not crash. I opened TST again, and FTP crashed.

I have had occasional FTP crashes with the old client (when performing a search) but nothing like this.

I do use the Activate Currently Selected Table feature. I did not have Autoscan enabled. Let me know if I can give you any more info.

(I am running on Win7 64bit)

[krumpy]

I'm afraid it looks like TST is causing the new FTP client to crash. I have been using the new search feature, but FTP would crash when the "choose seat" dialog was NOT active as well, at seemingly random times. I had FTP crash several times in the matter of a few minutes with TST running. After closing TST, FTP did not crash. I opened TST again, and FTP crashed.

I have had occasional FTP crashes with the old client (when performing a search) but nothing like this.

I do use the Activate Currently Selected Table feature. I did not have Autoscan enabled. Let me know if I can give you any more info.

(I am running on Win7 64bit)

Having same problem. Crashing a ton when i try to search.

[Zandry]

Does it happen right in the beginning of the scan, before any tables are scanned, or does it happen in the middle?

Also, could you try this solution which was posted in the FTP Answers thread (http://forumserver.twoplustwo.com/28/internet-poker/ftp-answers-7-8-a-824481-post20096148/#post20096148) to help fix crashes:
1. Launch the Full Tilt Poker software
2. Instead of logging in please click on "Observe"
3. Next click on the "Cashier"
4. Enter your login details here and select "Login"
5. Now please close and restart the Full Tilt Poker software

If that doesn't help could you send me a message on AIM/MSN/ICQ/Skype and let me see it on teamviewer:
AIM: ZandryTST
MSN: zandry@tablescanturbo.com
ICQ: 571846001
Skype: ZandryTST

It seems to be working well for almost everyone except a few people!

[yesright]

I am having the same problems as the people above, it crashes the FTP client or brings up an error.

The previous version would only work in the classic view window for me

[Zandry]

Are you guys using the english version of FTP?

Please send me a message and I can look on teamviewer
AIM: ZandryTST
MSN: zandry@tablescanturbo.com
ICQ: 571846001
Skype: ZandryTST

[yesright]

Yes, I am in the US

Now its not crashing but giving me the following 3 errors when i scan

Error injecting in target: Exception has been thrown by the target of an invocation.

Try resetting your FTP Lobby Widgets to Default! The Player List and Open Table/Join Waitinglist buttons must be visible!

You may also need the Microsoft Visual C++ 2008 SP1 Redistributable Package! Check the download page at www.tablescanturbo.com

[yesright]

what lobby will the new version work in?

As I said I could only get 0.48 to work in the classic lobby which the removed in the last update :(

[BeaucoupFish]

Does it happen right in the beginning of the scan, before any tables are scanned, or does it happen in the middle?


For me, it wasn't during a scan (scan seemed to work Ok) - it was when I selected a table) or a different table, which is why I wonder if it is related to having the Activate Selected Table option.

US version.

[yesright]

OK, I found the cause and the fix.

It's the widgets..........

I didn't know what they were until the error came up

For those having the same problem try this..........


(1) Enter the "standard view" lobby from the lobby menu

(2) At the bottom you will see a button "customize", click it

(3) click the "reset to default" button on the bottom right of the pop up.

(4) then click OK below it.

[Zandry]

Ok great that you've got it going again yesright :)

BeaucoupFish, you may be right about what you're saying, I didn't really test that feature I just assumed it would work, I will test it tonight, have you tried turning that feature off yet and see if it has any effect? And did you try that fix i posted on page 1 of this thread? And have you tried playing without TST and it does not crash?

[BeaucoupFish]

Ok great that you've got it going again yesright :)

BeaucoupFish, you may be right about what you're saying, I didn't really test that feature I just assumed it would work, I will test it tonight, have you tried turning that feature off yet and see if it has any effect? And did you try that fix i posted on page 1 of this thread? And have you tried playing without TST and it does not crash?

I logged on using the alternate method, but was still able to cause an FTP crash. I think that fix is mostly for ppl who cannot log on to FTP to begin with? Until today, I have played without using TST, and have not had FTP crash by itself (I do also use HEM).

It actually isn't that easy to duplicate - for a while, FTP was crashing constantly, immediately I clicked on a table: crash, restart, click on a table, rinse and repeat (since I was already seated at tables, and FTP auto-opens these on start-up, maybe that has an affect?).

But now, after trying to replicate the problem again, I couldn't get FTP to crash, and have been playing for a while. Maybe it makes a difference whether you have the option checked when the application starts up, rather than changing it on the fly. I want to get a session done today now its currently working, but can try some stuff later on in you have some ideas.

[Zandry]

Alright thanks, keep me posted.

The current code for TST scanning FTP is basically the same as it was before the update, I can't imagine that any of the little changes I made would be making it crash, especially since it seems to be working very well for almost everybody and these crashes are only happening for a few people :(

So I really think this is happening because of bugs in FTP's new update. I mean obviously using TableScan Turbo is triggering crashes for a few people in some way, but the root of the problem must be in FTP, my theory is that it could be a connection issue but I don't know. Hopefully it will work itself out for others as it seems it may have for you. Otherwise, if you get the crash again do make sure to allow it to send in the crash report, and maybe they will be able to fix whatever is causing it.

Anyone with this problem please feel free to send me a message on AIM/MSN/ICQ/Skype and maybe I could figure out whats happening if I could see it on teamviewer, but I cannot reproduce it over here at the moment

AIM: ZandryTST
MSN: zandry@tablescanturbo.com
ICQ: 571846001
Skype: ZandryTST

[x-badbeat-boy-x]

Zandry: What can I say?
Amazing software. Works great in FT! Never failed me. Greetings from Argentina.

[BeaucoupFish]

I did used to get occasional crashes with the previous release, and after restarting TST it would generally sort itself out. I'll let you know if I can reproduce anything consistently with this version.

[MostlyCarbon]

I had it working last night on both Stars and FTP, today Stars works but not FTP all of a sudden.

I've gone over the settings a bunch (there aren't that many).

Hmm..

Carb

[BeaucoupFish]

I did used to get occasional crashes with the previous release, and after restarting TST it would generally sort itself out. I'll let you know if I can reproduce anything consistently with this version.

I also sent you a Skype message: I can reproduce the crash by right-click selecting Scan table on an individual table after a normal scan has run, I think this might tie in to the earlier thought of having the "Activate Selected Table" option enabled (doesn't it perform a scan after x amounts of time or hands?).

[Zandry]

Thanks BeaucoupFish, I have released another small update v0.50 to fix this issue :)

Anyone else who had crash issues please let me know if this fixes it

[shorn]

Install a new version crashes continues :(

[Zandry]

Install a new version crashes continues :(

Hey shorn, could you go into more detail about what the crashes you're getting are?

1) Does TableScan start to scan, then Full Tilt crashes in the middle of a scan?

2) Or does TableScan not start to scan, and give you some errors? If so what are the errors?

3) Or does TableScan actually crash at the beginning of a scan? And give you a message like "The program needs to close"

[shorn]

Today i test this.

Crash (FTP client`s crash, not table scaner`s) appears when scanning in process and opened new table from wait list. I see buy in menu and in this second FTP client crashed. Next: "The program needs to close" (about FTP client) and window with suggestion to report FTP support about this error.

I learned fix this. If opened take sit window, I must click "cancel scan" in tablescanner and just after this I can open new table and quietly buy in without any crashes.

I will be very thank, if u fix this. :rolleyes:

[Zandry]

Thanks to your post shorn I think I have figured out what is happening :)

I am going to release an update v0.50b tonight. Please check back and download it and let me know if it fixes the issue for you. Before I made the fix, I was getting numerous crashes in the scenario you described, since I made the fix I have opened over 50 tables from the "seat available" popup in a row, without a single crash, so I think I have fixed it :)

[shorn]

I forgot to thank you for such a quick update. Big Thank you for your work!