Problem with PAHUD v1.19.10 beta on Absolute Poker

[Freddy_James]

The beta version is making each table pop up whenever a hand goes to showdown or the hand finishes, kinda annoying when you are playing 10 tables at a time and you time out with AA because 3 other tables pop up that you wernt involved in.

Any way this can be stopped in the options? or is a patch needed?

Using Win XP, and it's definately not AP's problem (for once) as when I logged off PAHUD the problem stopped.

[kraada]

Could you please enable logging (Tutorial: How to Create a Log File) and play on as few tables as possible to reproduce this problem,then attach the PAHud.log file to a support ticket? That way we'll have the data we need to figure out what is causing this issue and get it resolved.

[Freddy_James]

Any word if this is fixed yet? Or if not when it will be fixed?

I upgraded to PT3 because of this problem, but I'm having more problems with that than it is worth.

[WhiteRider]

What is your ticket number?

What problems are you having with PT3?
Have you reported them in the PT3 forum or via our Support system?

[Freddy_James]

ticket_id=45415

Was told this problem had no timeframe on when it would be fixed. So I upgraded to PT3 as was told I could transfer all my old HH's and aleiviate any problems.However, it didn't transfer any tournament summaries which is annoying but manageable, but it crashes every time I am in the middle of a session with a "runtime" error freezing 10 games up for 2-3 minutes - that IS a problem!. Also it slows my computer to a virtual standstill when running. No problems with memory / diskspace (P2.6ghz / 250GB) and when I close PT3 the games run smoothly again.

Opened a thread in PT3 technical, and they've asked me to use beta 24, which I have and has the same problem with slowing the computer down, timing me out of hands etc...

Cost of PT2/PAHUD? - >$100
Money I profited from it as a result? - $1000's
Asking me to upgrade to PT3 at an additional cost, only for it to cause huge problems and lose me money? - PRICELESS!

I'm currently NOT running PT3 when playing, as IT IS NOT FIT FOR THE PURPOSE THAT IT WAS INTENDED, (I'm sure I heard that was important when selling something?). And I won't be using it until these features are fixed.

[WhiteRider]

Have you created a ticket on our Support system to submit log files showing your PT3 crash?
These crashes are pretty rare now and we can't reproduce them ourselves so the only way we can investigate and get them fixed is with some help from the people who still have problems.

[Freddy_James]

So I have to run PT3 in the background, enabling logging, let it slow my system down whilst 10 tabling causing frustration and timed out hands, wait for the inevitable crash, which locks me out of games for 2-3 minutes losing me more money?

No thankyou.

I'd rather have this PAHUD/PT2 problem sorted out and bin PT3, which is way more trouble than it is worth. It may have cost $100, but has probably cost me 5 times that already in games and hands timing out as a result. I doubt very much I will ever see a refund, so I won't even make the effort in that respect.

So, when will the original PAHUD problem be fixed?

[kraada]

What version of PT3 are you running? If you're still running Build 3, the most recent release, Beta 24, fixes a huge chunk of slowdown and crashing errors since the Build 3 release. If we could reproduce any of these slowdowns or crashes we'd have fixed them by now.

I don't have a timeframe on any new PAHUD releases at this point.

[Freddy_James]

Is there any timeframe when this will be fixed?

PT3 just slows my computer to an almost standstill so I wont be using it again, PAHUD used to work fine but this table pop-up problem basically now means I have two huds which are both more trouble than they are worth.

Come on pokertracker, I reported this problem, a MAJOR problem, coming up to two months ago and you still havn't sorted it out, or even said that you have any intention of doing so.

Sigh...

[WhiteRider]

The issue is in our bug tracker but I don't know when it will be addressed, sorry.