[pat82]

The reason the source is down is because the tool was sold, and I am not sure if the site that bought my software want to supply the source code. So that is the reason it is down for now. I will post more about this later.

Currently I have made my own engine for reading Poker Tracker databases, so RBCalc now reads both PT files aswell as the pure logfiles.
I have also implemented the graph engine for both logfiles and PTdatabases, and you can draw the winnings aswell as the rakeback graph ontop of the win-graph.
The logfile engine is also a bit optimized for even better speed, the function that reads the PT database is verry fast aswell and reads about 100 000 hands in around 5 minutes on my stationary PC.

I have some small stuff to finish up that I will complete during this day, and I will release more info where to get the tool later tonight after I have talked to my employer.

[ QUOTE ]
The bad news, I ran some tests today and this calculator does not come up with the correct rakeback stats atleast at PartyPoker. So if you're numbers don't equal your affiliates numbers then you know why. The good news, On every date this program underestimated rakeback stats so you'll be getting more back then you expect.

[/ QUOTE ]

Example. 4 players sitting at a table. One of them sits out, the log will display "xxxx is sitting out". When I first made the tool I tought it would say this for all players sitting out in every hand, BUT the client only writes this to the log ONCE when the player actually sits out. After that, in the next hand it will look like 4 players are still sitting at the table, but in fact one of them is sitting out. I did not realizie this when I coded the txt-log engine, so that is the reason why RBCalc dispays a bit less rake then what you actually get. Since it will devide the rake by 4 players in that example, instead of 3.

// pat