We do not currently support Ignition so if your HUD is not working you'll need to contact the author of the hand converter you are using about that. With regards to the hands if you want to see hands older than a day you need to move from the 'Play Poker' section to the 'View Stats' section in Poker...

Please compress the hand history files from that session and attach them to a Support Ticket so we can investigate that for you. By default PokerTracker 4 moves your processed hand histories to your \PokerTracker 4\Processed folder which you can access via the "File -> Open User Data Folder&quo...

Please follow this guide to get PostgreSQL installed and if it does not install successfully go to: C:\Users\SOME_NAME\AppData\Local\Temp In this folder there should be a file called "install-postgresql.log", "initdb.log" or something with "bitrock", "postgresql&qu...

It will 'work' but only hands where you contribute to the pot will import meaning that some stats will be wrong and others will be skewed - see this thread for more information.

LeakTracker is 'legal' and has been approved by their poker room manager.

That's working for me so please attach your audit file to a Support Ticket and we can take a look at that for you.

That method is unchanged as you can see in this PokerTracker 4 guide. If you cannot remember the password used or made a typo when installing PostgreSQL then all you can do is use that method to override the password requirement or reinstall PostgreSQL again.

Cash game hands where you contribute to the pot will be imported using PokerTracker v4.14.23 (the current version is v4.14.25) however hands where you do not contribute to the pot are not provided by Microgaming so none of those will import.

Tagging is for hands only at this time however you could use that system to filter for unreviewed tournaments. To do that go to 'View Stats -> Statistics', select the 'Overview' report and 'By Tournament' tab. When you go into an individual tournament to review the hands you can then select all the ...

No problem and thanks for the update. As I mentioned in step 4 that file can be the cause of the connection issue and we typically see the 'memory segment' error in older PostgreSQL versions such as v8.3 and v8.4 which are no longer supported by PostgreSQL. If you are using an older PostgreSQL I'd r...