10-02-2008, 12:42 AM
10-02-2008, 07:12 AM
Yes, that would be faster.
Since what PT3 version is this hud cache existing?
Since what PT3 version is this hud cache existing?
10-02-2008, 12:45 PM
Mr_Snood Wrote:
Yes, that would be faster.
Since what PT3 version is this hud cache existing?
Since what PT3 version is this hud cache existing?
Sweet!
The cache started in beta 16 I think.
PT3 is now at BUILD 3 stage, and the cache is working great. I hope you can make it work sven 
Edit: this is what their website said
http://www.pokertracker.com/forums/viewt...=15&t=6548
Beta 16 - Wednesday August 27.
Added:
Trial extension: 60 days
Cache to improve Hud performance
Table opening for TableTracker (Full Tilt, Party and PokerStars only)
Database Housekeeping. Replaces the old way of clustering/vacuuming/analyzing
10-12-2008, 12:51 PM
so now that SpadeEye uses the PT3 cache, all we have to do is to update the cache in PT3 for our Party/FTP DBs to achieve the same results as before when we used the PT3 Aggregator?
Say we just imported 100k hands of data on FTP today, and but we forget to update the database cache in PT3. Will a SpadeEye scan show results from those extra imported hands?
Say we just imported 100k hands of data on FTP today, and but we forget to update the database cache in PT3. Will a SpadeEye scan show results from those extra imported hands?
10-12-2008, 04:51 PM
The answer is: "No".
If SpadeEye detects PT3 build 16 (or newer) it will always use the PT3 cache...
I will most likely improve this, to make the answer be "yes".
If SpadeEye detects PT3 build 16 (or newer) it will always use the PT3 cache...
I will most likely improve this, to make the answer be "yes".