Hi,
Thanks for the email inviting me to beta test PokerTracker 3.
Here are some initial observations.
1. Installation. I already had postgresql installed on my machine and downloaded
the version without postgre sql. The installation was smooth and quick. No problems.
My machine, by the way, is an apple macbook, with windows XP Home running under Parallels
emulation.
2. Initial data load. I had 45 files in a PokerStars directory. Many of these files were
for 7 card stud, omaha, and other formats which are not yet supported. A subdirectory
contained an outdated tournament summary file which referenced older tournaments not
in the data files. The 45 data files loaded in about 1 minute 25 seconds, spitting out the apporpriate
error messages for the unsupported file types. After this, PokerTracker processed the outdated
Tournament Summary, and gave the appearance of "hanging". I let it run, and finally the entire
process completed after about 8 minutes. Don't know why this should take so long. Maybe because
there was no data associated with the tournament summaries? In any case, a little bit more user
feedback might be useful to indicate to the user that the process is not hung and should not be aborted.
3. Later, I loaded some ring game data (about 100 hands) from FullTilt. This loaded in less than 15 seconds.
4. Views of the data all look good. In general, the program has a clean, easy to use interface that I like.
5. The data files were not moved to another subdirectory, like they do in PokerTracker2. Is this something that
you plan to add later? Or do you just keep rereading the same old data each time you do a data load?
6. I could not get the Full Tilt ring game data to import automatically. I could only import it in bulk after play
was completed.
So far it looks good. I'll report back when I've had a chance to test later releases.
Regards,
Jonathan
