I can't confirm this version will work, but this is my best guess.
https://tabletamer.com/download/Tabl...%201.3.3.0.zip
I will try to add support for bodog now.

Restarted the client and it went back to the new version.

version 1.4.0.1
Bodog Cash Game : sometimes the %effective pot odds is wrong

Does this version include a fix for the automatic bets in WPN or are you still working in it?

I'm still having problems with TT crashing when I have 5 tables up on Ignition. How do I fix this?

Not done yet. I can't say exactly when it will be done. The new software is completely different, and it may take a couple weeks.

I need a crash dump. I will send you instructions on how to create one via PM soon.

Example:
https://gyazo.com/edcb2d3d79893cc8e05c61150f1fa9bb
https://gyazo.com/c68c959865614be6d8e9a8b27f04788f

No doubt, it's best to fix the actual problem. Unfortunatelly, such "fixes" from my experience take weeks, because the bug isn't easy to reproduce and as you said , you don't experience it at Jackpot SNG's. Quick fix specifically for "all-in" hotkey would be VERY HELPFUL, because i am loosing serious money on a daily basis when instead of moving all-in with AJo and 7bb , TT minraises.
Once again the nature of the bug: sometimes simulated betting boxes absent at preflop ( and ONLY at preflop), and in such situations "all-in" hotkey works as just clicking "BET" button at poker client and results in minRaise. If all-in hotkey worked as it should, then the bug would be quite tolerable and not urgent to fix.
Thanks a lot for any solutions !

I will implement it for you. I am not sure it will fix it. I am going to try to release a new version today. It should be in that one. I will let you know.

I'll look into it.

Try the latest version out. I added it. About the controls not showing up, can you do something for me? Turn on Settings/Program/Debugging/Debug, and when the problem happens, highlight the table and press ctrl + shift +f12. Then, send me logs. It would help pinpoint what is going wrong.

Poke,

I have lost the use of my "BetXpercent" buttons post flop on Bovada. They show up correctly but do not function. Multiplier buttons work fine. Any idea how to fix this? It is still occurring after updating to the latest version, 1.4.0.2. Thanks!

Meant to clarify that this is for MTTs only. In cash games, these work fine.

I'll check it out.

The same thing happens on wpn with X bb bet hotkeys. This used to happen the last time jackpots was supported. A long time ago it used to work in jackpots. Itll type the number out in the betbox but it will just make the minimum raise. If you dont have it auto raise itll type it out but if you hit raise it will still be minimum. If I type it out manually it works.

advanced action buttons are same color as fold button so they are causing tables to be urgent when they are not as well(at least I think thats the problem???)

I know about the problem with bet x bb hotkeys. If you hit it a second time, it works.

It sounds like a problem with the advanced action buttons. Are you on Windows 7 or 10? Which room are you playing on?

Win10, Bovada, if yer asking me.

I was asking cdfj.

windows 10 on americas cardroom.

Tried 1.4.0.2 today:
1) This version brought more bugs . Now bodog client buttons ( 1\2 pot, 3\4 pot, pot) just don't work at all. And every betting hotkey POSTFLOP works as minbet ( doesn't enter bet size at all, just clicks BET).
2) I couldn't test whether or not all-in hotkey would work when simulated bet boxes are absent on preflop, because i stoped playing once i noticed postflop betting bugs. However, i pressed ctrl+shift+F12 when simulated bet boxes were absent on preflop and send you the logs ( RockJohnson1983).
For now i will downgrade to a previous version where postflop betting works as it should.
Hope my logs would help. Thank you for improving the program!

Hey poke,

I read above possibly a few weeks for full functionality on WPN. Is that still the expectation?

Tried sending my logs again and keep getting the error message.

Edited: Finally got them sent to you.

Sorry about that. We made some changes to ignition in that version, and I didn't test thoroughly enough. I will most likely have a new version out with it fixed tonight.

I don't want to make promises, but I think its a fair timeline.