is pt3 slower at importing hands than pt2? i exported my hands from my pt2 db and its taking forever to put em into the pt3 db....

PT3 should be much faster. Orentha was having some severe slowdowns which caused him to be getting a 5h/sec speed, but I've always gotten 60-80h/sec myself.

If you are getting < 20h/sec or so, something is not right. Please submit a support ticket to our support system including the hand histories you are having problems importing and we will try and get to the bottom of it.

I know a big bet is twice a big blind, it's just annoying to have to look at my stats that way. Will there be a quick fix for this anytime soon, like PT2 had?

I just bought PT3 and converted my old PT2 database, but the conversion ate up a huge chunk of my hard drive (like 8+ GB), so I want to go and delete the old PT2 db, but I can't find it anywhere. Does anyone know where on your hard drive it's typically stored? If it makes any difference, it was a PostGRE database, and not a mdb one.

ok I think you have to open up PGadmin to do this. It's typically located in your start menu under the postgresql x.x submenu.

You still have PT2 installed? If so, go to File\Maintain db names and remove the database from PT2 (remember the filename listed on the right.) Then go to Utilities\PostgreSQL database functions, select your database in the list and delete it from there.

thx, totally can't believe I didn't think of this myself

What people who are having problems fail to realize is that for most people, there are zero issues with PT3. Yes, there are major problems, but they affect a small percentage of users (a very vocal percentage, but small nonetheless).

These issues will be resolved. The next beta should resolve even more Hud issues and should contain an improved cluster that for some of our alpha testers has improved query speeds by 10x or more.

These issues are taking longer than we hoped to resolve, but we are working diligently and improvements are being made.

LOL?

Is it possible to combine databases yet. I've got the old db which is everything before the 60 day trial beta. Now I've got only the hands since I've plaued the 60 day trial and I want it altogether. help!

Database > Database Management > Export

Then on the other database -> Import

This is close to true for me. I'm still running the initial release version, so I have the HUD focus steal bug, which is annoying. PT3 crashes occasionally, but mostly it runs pretty smoothly. One thing that really annoys me though is that a CPU-intensive query will lock up my ipoker client while the query is processed. I don't know why this happens or why it would be necessary.

Actually I'm really pissed When I play I have to restart PT3 everytime I open a new table cause PT3 doesn't realize to display stats on the new table also... and small percentage of people...
Now I get this error also ... damn what is this?


all in all I think I got the same issues irentha has .... hey buddy

I don't know if this is the right place to ask, but let's say I have a lot of hands on a shortstacker who either makes a standard raise when it's folded to him, or he goes straight all-in. Is there a way to get the percentage of standard raise vs all-in raise when it's folded to him?

While I understand that you are working hard at making PT3 a marketable product, and I have no reason to believe that you aren't serious about fixing the outstanding problems, I really hope that this is a level. The HUD flat out does not work for me in either Build 2 or Beta 12. I'm willing to be patient but I really hope that you don't think that there are "zero" issues with your product.

After you do this you are definitely going to need to run a file system defrag on your PC. In XP, Start->All Programs->Accessories->System Tools->Disk Defragmenter. Otherwise PT3 queries will likely run slowly.

There will likely be a fix eventually, but it is not that high on our priority list (no offense).

A small integer is a binary integer with a precision of 15 bits. The range of small integers is -32768 to +32767.

I don't know how the number got so far out of range, but I guess you can purge that database now.

But before you do that Orentha please go to pg_admin, connect to your database and do a SELECT id_limit, limit_name FROM holdem_limit. It would be helpfull to know if there are any duplicate entries in there.

Seems like a stupid question, PT.com says ongame hud isn't ready, is this still the fact? Or is the ongame hud working yet?

The documentation is still accurate. Our current focus is on improving stability and responsiveness of the program. We have made significant strides in this regard, and once we are satisfied that all outstanding issues have been resolved we are going to return to adding new features to PokerTracker 3. We hope this will not take too much longer.

Reread my original post. I've highlighted the part I think you need to pay most attention to.

I'll reiterate. Yes, there are problems. I'm not saying it works for 100% of users. However, those major problems are only problems for a very small percentage of users, and the number of users who can't use it at all is even smaller.

I received this the other day and had to restart PT3. It went away after that.

Crashing with some frequency is a major problem and everyone has that. It's bad enough that the program was released in this state without you belittling the issues people are having with it.

The only reason there isn't more and better competition is that most poker players who are also programmers would prefer to be playing poker than writing a next generation tracker and HUD despite probably getting a better hourly writing a PT killer.

Well, the HUD on Stars worked better for me 2 months ago, I along with many others started to complain about the disappearing stats back then. Now, with Beta 12 the HUD actually crashes on occasion and I have to restart PT, not a fun time when your multi-tabling but it is Beta. Unfortunately relying on the pt logs to find these problems is not working that well. I mean, the log is not telling you things like the HUD erases stats on the screen and then replaces them 5 seconds later, why stats are erased before the HUD is ready to redisplay just makes me laugh now. So, don't think that everyone that is having issues can even be bothered to continue with the Beta testing process a month into commercial release.

Don't get me wrong, I really want you to fix up the problems but even basic funtionality is missing from this generation of trakers; things like hand deletions, tourney deletions are pretty basic (I've got tourney results with $50000 buyins from testing, I know I can delete the crap and make a new database and import again but really should not have to).

Then of course, importing tourney results is much better but a 'simple' way to enter ones results would be nice too. Of course, not skewing a players stats when they sit out of a tourney would be nice also along with the autorating system becoming functional again, but these things seem way to far off with the problems ahead of the things like these.

A couple of things... first Kraada said you have at least 100 support tickets so that makes it seem like there are more than a few people who are having problems. Second, I have had 4 or 5 fairly major issues but have not submitted a support ticket. I'm sure there are many more people who are having problems but just haven't mentioned it. Last and most important I don't care if this works for other people I need it to work for me. It does me absolutely no good if it works for Jimmy down the street but crashes 3 or 4 times a day on me or won't display HUD stats half the time.