PokerTracker

Hi

For the last 2 weeks or so I've experianced problems with importing hands into PT3 and I finally figured out when and why it happens. The PT3 log doesn't give any error messages and everything appears to work except no hands are imported and PT freezes when I try to stop an import.

This is the case for both manual and auto import, and for some time I thought it was broken hand histories that caused the problem. but now I know what it is.

the problem occurs as soon as I try to import a hand history that allready has at least one hand in the database. So if something goes wrong while I import hands, or a file isn't moved away from the HH dir. I'm no longer able to import hands until I move the hand history out of the way.

To repeat the problem I selected a file from the processed folder and tried to import it, the log file ends with the following lines.

2008/12/27 05:23:47.808: [- Main -][WindowStatsTab] Refreshing active player: false
2008/12/27 05:26:28.014: [00004816][ImportManual::ImportManualFeeder::Entry] Beginning thread.
2008/12/27 05:26:28.024: [00004816][ImportManual] Message: Import beginning
2008/12/27 05:26:28.115: [00004816][HandHistoryDatabaseImport::DatabaseVariables] Getting connections
2008/12/27 05:26:28.156: [00000580][HandHistoryDatabaseImport::DatabaseVariables::Entry] Beginning thread.
2008/12/27 05:26:28.165: [00004816][ImportManual] Message: Import file: C:\Program Files\PokerTracker 3\Processed\HH20081225 Valborg - $0.50-$1 - Pot Limit Hold'em.txt

Finally seems like I solved this myself. I guess I used a different installation file to install postgres.

I just tried PT3 again and got the same bug.
I'm running postgres 8.3.6 with the latest ODBC driver. I tried both PT3 version (beta and stable).
Postgres is running on Linux.

Any idea how to fix this?

Can you explain exactly what your problem is?
Is it freezing when you import a file that has already been imported (so would report a duplicate)?
Does it work otherwise?

Please enable logging, reproduce the problem and submit your PokerTracker.log file to the Support system , and link to this thread in the reference field of the ticket so that we can investigate.

Hi,

thanks for your fast answer.

Ok my problem is that I import 1 HH file. (I think it already got imported by PT2 a while ago but PT2 should change thefile itself.)
If I now try to import the same file again PT3 does nothing anymore. It doesn't hang up or so it just stops working. I can click on "Pause" and it pauses. However "Stop" doesn't work.
Closing PT3 isn't possible because it's importing.
Somehow the same happens with importing a tourney (without dublicates It think).

I will try it now again and report both logs to you. (Well the log stops at the same points but maybe you can see more than me.)

Without any dublicate files it's importing so fast that I want to switch to PT3.

One question (it's higly offtopic and I haven't used the search yet): Is it possible to see the stats at the table before seating? Would be nice for tableselecting. With PAH it's working (PP).

EDIT: Well I got the answer to that. Will that be changed? PAH is able to do it and PT3 is developed with the PAH developer isn't he?

EDIT2: viewtopic.php?f=19&t=13980&hilit=hud Any updates on that?

Someone will get back to you via your ticket when we get the logs.

There are plans to show the HUD before you start playing, but currently the HUD is tied to the import routine and I don't know when this will be changed.

There is, however, a free handgrabber for Party (FreePHG) which will write hand histories for observed hands and if you add the folder they are being written to to your Party Configuration then you will be able to see the HUD before you join.

Alright thank you.

I could fix the problem with the PT3 support.
The problem was a wrong language for postgres. It has to be english.

My guess:
The dublicate hand error postgres reports can't be read/parsed by PT3 and so it continues trying to import the hand while postgres is reporting the errror again. (Endless loop.)
Could be fixed on PT3 side as well with reacting to other language reports as well but that is of course a lot more work while it can be solved easily with the english postgres version.