HUD stats stuck on dim, wtf

I moved the slider to make it a little more transparent, now its too dim to even see the numbers and i cant change it back??

Using beta 12 - Lag and missing stats seem improved.

I am having a problem with crashing that I haven't had before. If I finish a set and start a new set PT3 locks up and I have to restart. Sometimes I get an error message that says there is problem with the HUD and to restart. I have a log file do I need to do a ticket with both the PT and HUD log?

Does it keep freezing and crashing for anyone else? the new build is pretty much unusable for me

I don't understand whats going on here. They have a perfectly working PAHUD model. How hard is it to plug in a few extra stats into it?

+1.

I know that these guys have put in a ton of effort, but this thing is killing my PC. It works fine until I turn on the HUD - then it all goes to hell in a hand basket. Beta 12 and Build 2 are both problematic on my machine.

I opened a support ticket and was asked to defrag my hard drive. I responded that I defrag my hard drive on a regular basis, and just did so last week. I will wait and see if PT3 support can help me find/fix the problem...but the HUD lag/freeze/etc. renders much of the software's functionality useless.

Decided to try out PT3 (been using PT2), shortly after I start auto-import my PC reboots itself. I don't see any error messages because it happens too fast. Tried it twice, same result twice. Playing on Stars, have WinXP. Nothing else running. Guess this trial is over...

Had to create a folder outside the C:\Program\ path. Even if I choose a different folder under C:\Program\, the path in PT3 still says C:\Program Files\. But creating a new folder directly under C: for processed files did the trick. This seems to be a problem for those who run Swedish Vista only though. Got a support email from a fellow countryman who runs PT3 on Swedish XP and he doesn't have the problem.

I'm confused. PT3 is BETA again?
I'm quite sure I get something wrong. Could someone be so kind to explain me?
If I'm a new customer, which version should I get, the new BETA12 or the BUILD2?

A lot of people had a problem with the HUD build 2, and a lot of people didn't. So they have released a new beta to see if it works better for the people who were having problem with build 2.

Therefore as I understand it the advice was install build 2, if it works ok, fine. If not, install beta 12 and see if it improves the situation.

Personally build 2 worked ok with party, but not with ipoker, and suffered a lot of lagging. Gave Beta 12 a whirl and massive improvement, such that I am using it as my everyday HUD.

So it's rather a matter of choice? Both will be updated? Or will I face problems in the future if I chose the BETA12?

No, there will be a move from build 2 -> build 3 shortly. Again from my understanding (as I have nothing to do with PT3), there has been a big rewrite of the HUD.

Beta 12 is a test for this new and improved HUD code, and if beta 12 goes fine for people, there will be a "build 3" that will be basically beta 12 + more bug fixes and tweaks.

From my experience and what I have seen on the forums beta 12 is a massive improvement over build 2, so I would expect that a build 3 won't be far away.

As stated previously build 2 works fine for a lot of people, but at the same time it doesn't for another large group. I think the reason for this was that the guys at PT3 didn't want to find they released as "build 3" and find that the HUD was broken for even more people.

OK, thank you for clearing this up for me!
As I found out this is explained quite in detail on the PT-forum...

I don't claim to understand the ins and outs of the technical difficulty here. Josh made the statement in a thread on the alpha board, so I presume he knows what he's doing

Good deal, I'll check them out too

Are you using the manual import's Import From Folder function? Manually importing is much, much faster than auto-importing (30x faster last I personally ran a speed comparison).

Configure --> HUD --> (cash or tournament) will get you the HUD configuration window even if you can't see the HUD at all. If it is more transparent you can see through it easier. You want to make it less transparent.

Yes please, that way we have the logs and we have them next to a report of what issue caused them. Please quote the error message in full and attach the log files to a support ticket. We do appreciate it.

Several people seem to have problems with Beta 12; if you do not have many issues with Build 2, you should consider reverting (or staying) with Build 2 until another release comes out. Hopefully this won't be too far off.

The database is built entirely differently, there would be a whole lot more effort required than simply plugging in a few extra stats. The PT3 HUD will also end up being vastly more configurable in the end, and I think this flexibility is worth the wait.

We have seen people who defrag their hard drives come back with a large reduction in CPU usage. It's not a panacea, but it is something to try; just leave the computer defragging overnight. If it drops CPU usage from 100% to 60% things should suddenly get a lot more usable. (This sort of result most likely occurred for the users it did because they had large databases. Apparently PostgreSQL's files getting fragmented slows things down.)

There are C:\Program Files\PokerTracker 3\PokerTracker.log and PokerTrackerHUD.log files. If you could attach those to a support ticket it will help us figure out exactly what is going on.

Good to know, thanks.

Build 2 is the latest stable build. Beta 12 is supposed to fix known issues in Build 2 (there were also quite a few alphas in between Build 2 and Beta 12). The software cycle works like this: Start programming until something is good enough to release --> alpha testing --> beta testing --> stable release. Then when there are new features to add, or fixes to make, release another alpha build so that you can do some testing and not release a patch to everybody that is very broken. Then after the alpha testing gets it good enough, it goes to beta testing, and once it's stable enough, release the next stable version. Then this repeats. So what happened here was there were significant issues with HUD Lag, Replayer crashes, and other things in Build 2. These were fixed over several alpha releases, some of these fixes created more problems and needed fixing themselves. It got to a point where it was stable enough to release a beta. But not stable enough where we felt comfortable releasing the next build. So we have Beta 12. We will continue to have beta releases in between stable releases throughout the lifetime of the software. If you do not feel you need any of the fixes in the latest beta and want to stay with a stable release you are always welcome to do so.


See my above explanation of the life cycle. You won't experience any problems updating to Beta 12 other than software issues still hidden in Beta 12 that need fixing (and we are aware of a few . . . and we are working to fix them ASAP). Once Beta 12 has become stable enough, it will become Build 3. We don't expect Beta 13 to come about before Build 3 but it is possible depending on how many issues there are with Build 12 in the end and how complicated the fixes with them are.

The only problem with this is I don't think Build 2 was stable, the build that everyone paid money for. Now it looks like we'll have to recreate our database once the next "stable" build comes out. This was released commercially way too soon.

I am in the process of doing the following:

• Disk defrag
• database cluster
• database vaccuum/analyze
• hard drive cleanup/compression

but as I said, I do all of the above on a regular basis. If it works, great...if not then what?

At that point, please follow the instructions listed in this forum post. The more data we collect on these issues the easier it is to figure out exactly what is causing them. Once we understand what is causing them and can reproduce the errors, we can fix them so that you won't experience them further.

Can someone please point me to a place where I can find quality HUD layouts. Thanks.

Unfortunately the only way to share layouts at the moment is to swap Layouts.pt3 files. We do eventually hope to have layouts in our repository, but we don't as of yet. I'd recommend trying to find somebody to swap with . . . I don't know anybody with a standing offer out there yet.

Originally Posted by Stosh
I am currently re-importing all my datamined hands into a new database because I dl'd the latest beta. It is 3mill+ hands. Its been importing in manual mode for 3hrs 45mins and I only have 79,000 imported. It says 155:38:00 for time remaining on import. Why is it going so slow? This re-import stuff is a big pain in my ass. Can I make it go faster somehow?

Kraada
Are you using the manual import's Import From Folder function? Manually importing is much, much faster than auto-importing (30x faster last I personally ran a speed comparison).

... Yes, read my original question again. It says I'm using the Manual Import function. It's been importing over 12 hours now, and its still very slow. This is very frustrating.

Can we see player's PF squeeze % somehow?

I got sick of the slow import, so I closed PT3. Here is a pic of how slow the process was going...

A large number of duplicates slow down a manual import, especially if you have logging enabled. If you haven't already, try disabling the logging, then shutdown and restart prior to the import.

welcome to my world dude
While it's not that bad, I never get over 15hands/sec

I see the image you posted and wonder if you tried the manual import while not auto importing? I would guess if your actively mining away while doing doing a manual import, you might see some poor results depending on how many tables you are mining.