Quote:
Originally Posted by PJs Ronin
First. I was unaware you were using a 3rd party for the graphing functions. I have asked many questions about graphs over the past couple of years and had this tit-bit of knowledge been available earlier I probably would have shut up long ago. One of the feature requests that has been around since Jesus was in grade school is a function to combine all cash/tourney/HE/OH winnings/losses into a single BR graph.
With some exceptions, software is almost always written using third party code to create common features; the visual components of the graphs are just a small example of that. Even companies such as Adobe use third party code to create some components of their UI, it’s a common practice.
Although we have combined Omaha and Holdem data into the same reports in PT4, we do not intend to combine Cash Games and Tournaments in the same way. Can it be done in theory? Probably… but it is too complicated to do this to allocate the resources necessary. Keep in mind that cash game and tournament stats are separate entities, they may have similar names but the data does not co-mingle due to the differences in the way processing must occur. This is why you need to create a separate HUD profile for Cash and Tournament games, the non-technical way to explain it is that the stats used are not fully compatible with one another, which require us to use separate tables in the database for cash games and tournaments. If we combined cash games tournaments structurally within the database schema the processing required to accomplish basic task might crush a high volume player's user's computer. Someday far in the future perhaps, but right now our current dual-path strategy is best.
Quote:
Originally Posted by PJs Ronin
Second. Making changes to PT elements 'on the fly' (like suddenly discovering 6_bet_on_thursdays is a great stat and you need it in your HUD) is like pulling teeth. My computer is not bleeding edge, but it ain't bad and changing parts of a HUD while still playing just about locks my system. After pressing the 'OK' button in the HUD profiler PT3 pretty much becomes comatose for 30-40 seconds. Same deal when starting 'auto import'... same deal when changing filters. All of these things are pretty well instantaneous in HEM (spew)... in fact I cannot find one activity in HEM that grinds the program to a halt. I find many in PT.
Contrary to common belief, the owners of HEM and PT get along, we are friendly. They have a good application as well, both applications have their own sets of advantages and disadvantages - of course we prefer our application over theirs and we hope you do too. The most basic example PT3 & PT4 are both coded in C++ for cross platform compatibility while HEM is coded using Microsoft .NET technologies which is not convenient for porting platform independent code; as such HEM and PT3-4 rarely use the same APIs or methods of accomplishing the same goal while programing our respective applications. Another example is that HEM forgoes the customization options that PT3's engine was built upon, in exchange they gain some speed in the rendering of reports through .NET technologies while losing the ability to add some stats to their HUD or adding custom stats. We in turn are willing to sacrifice a second here or there for a more powerful product that allows the user the greatest flexability. Both products make tradeoffs in various areas, but as they say "the grass is always greener on the other side." We regularly help users switch to PT3 after being long time HEM users, these tend to be people who are willing to forgo a little report rendering speed in exchange for more raw power… we could achieve the same report rendering speed as HEM if we created an application with less features, but I don’t think our users would like that at all ;-)
With that said, I think you will be pleasantly surprised at some of the speed optimizations included in the PT4 code. We are not done developing therefore we cannot give specifics, but many areas have improved load timing because when it is possible we have switched to loading the GUI in stages which saves processing resources.
Quote:
Originally Posted by ServerBTest002
I don't know what's are your plans but there are plenty of things you can do about EV....
Another one is EV per street, I know it can lead to wrong outcomes but used in the right way should be useful.
Btw best of luck with PT4, I'm looking to switch from HM since their support isn't able to fix bugs :P
Take a look at video #1, I think you will be happy to see some of the stats you asked for in default report when using the advanced toggle switch.
Quote:
Originally Posted by PJs Ronin
This is an accidental error that we made in the past, and it is one we will strive hard to not do again in the future. Please accept my apology; we should not have discussed something that was still in the idea stage before we were in development. We have learned from that experience, on the bright side it made us better as you will soon discover when you try PT4. In the future we will try our best to not create expectation for a feature that was under consideration but not yet developed.
In the software business, when an application is developed (or updated) the designers often have to intentionally remove proposed features in order to make shipping dates. If we included every idea that has been proposed then PokerTracker would have been vaporware, it’s a precarious balancing act that must be done on a daily basis to determine what the priorities are when adding new features. Most software (use Photoshop for example) does not have a moving development target, they create the application then come out with patches or hot fixes to solve design and programing errors as they are discovered - with the rare but possible feature upgrade. PokerTracker is a different animal entirely; we constantly have to update PokerTracker to assure that we can continue to track data from a wide range of third party companies which do not always communicate their plans to us directly. We may come into work on a Monday morning only to discover that a hand history format change had occurred over the weekend that we did not know about, forcing us to drop everything to address the change. In other scenarios we may have a feature planned because we think it would be great for the users - but due to feedback we change our priorities to instead focus on functionality that would positively impact the play of a greater number of users. Bankroll management is an example of such a feature. We have implemented some of the supplementary concepts from the bankroll management module spec ideas into PT3 since that post was made, but the core functionality we envisioned was postponed to instead work on adding new features which our users were telling they needed immediately which were complicated to develop - for example multicurrency. This doesn't diminish the value of the features we intended to include but never got around to adding, it only means that there were other features that were higher priority based on feedback from users. There are hundreds of thousands of PokerTracker users, our job is to do our best to adjust development priorities to meet the needs of this vast user base, it is not easy - but we try our hardest… and we really do listen.
Now back to your original question - I cannot answer with specifics because we cannot discuss any feature until it has been included in a video or press release, but I can say this functionality is on our radar - and it is something we are discussing… it has not been ignored.
Quote:
Originally Posted by cgets
few ideas
1. reverse hud - lets say you are new at the table and after 10 hands you are 60/50, it does not tell much about you because of small sample size. But there is a reg, and you have 200 hands on him, so he probably has 200 hands on you. So it will be useful to see how the reg sees you, from that 200 hands you play together. For example by double right clicking on his hud your hud could change color and show only the information he can see so you will know, tak you are not 50/60 but 18/15 for him.
2. positionally aware stats - instead of classic VPIP, PFR 3bet... there will be special type of these states which would show numbers according to actual position of villian. So if villian will be on CO his VPIP would show his CO VPIP instead of total VPIP, if he will be on BU it will show his BU VPIP and so on. This might save some place on hud and also save time because we will not have to look at popups so often. Yes, this will need about 5 to 10 times bigger sample size but when we have a lot of hands on somebody why not see positionaly related stats right away on hud instead of total stat. Obv. when smaller sample size, it will show total stat and lets say it will be underlined to distinguish.
We love the idea of the reverse HUD, it is technologically possible but it is not feasible without interrupting you're playing experience. Even modern desktop computers may have some trouble handling the processing speed required to complete this type of very complex SQL queries, PokerTracker takes avoids taking any risks where we may accidently add a feature which would interfere with your game. I'm afraid that although it really is a great idea, it is just not feasible until the average computer advances past what is currently the highest end of our users - once technology catches up then we can revisit this great idea.
Your positionally aware stats idea is also good, but once the player starts multitabling his HUD would grind his computer to a halt, it would be too processor intensive to switch the stats on the player HUD on the fly. As it is, we already have some users who only refresh their HUD every X number of hands to lower the processing hit required to render the HUD. We go out of our way to assure that PokerTracker augments while not interfering with the playing experience; I fear that too many of our users would find such a feature to be detrimental rather than helpful.
Please keep these ideas coming…. Even when they are not feasible, it helps us to see what your real needs are, and points out possible flaws in the current player "workflow" that we may be able to solve. Keep it up!
PS: I think you are already aware of this, position-specific stats exist in the HUD popups, and more have been added for PT4
Quote:
Originally Posted by kollane
My idea: feature when i play, then i cant open PT to see my graph. hope its possible
Although we see the value of hiding data for tilt control and to temper results oriented thinking, we also see the downside of such features. The best bet is to just hide your PokerTracker window and remove any win rate stats from the HERO by altering your HUD profile - a task that is much easier to accomplish in PT4.
Quote:
Originally Posted by Messenjupp
Some further features that should not take all that much work:
1. More number of hands to mark while playing. ATM its only five...10 would be better IMO...or at least give people an option somewhere to choose how many hands they wanna see to mark them.
2. Mark hands at rush too (not possible ATM as far as I know).
3. Make stats at least kinda semi useful for anonymous tables at microgaming network in a way that the HUD only shows stats for a session...and if a player leaves the table (this should show in the HH, right) stats on the HUD should go back to zero again...not sure if thats possible though. problem with those annonymous tables is that players are only recognized by a tracker as player 1, player 2, .... so if you already played some days and start a new session at those tables you will get some stats on your opponents that are not accurate of course...so why not tell the HUD to NOT show any previous stats for those tables and start from the beginning and also restart HUD stats when a player leaves...if that would be possibe we can at least use HUD stats to some degree.
Have you ever used the Show Hand History feature in the PT3 HUD? This opens a window which allows you to browse through the hands while played at the table. This window has some very special features, such as -
• You can mark
any hand for review that was played at the table
• You can review the street by street equities after the hand is complete (this is why I leave open this window while playing at each table, I more the window to my second monitor for convenience)
• You can export the hand to 2+2's forum format, text, or Microsoft Word RTF for further review
I think this would address your needs. In addition, I think you will like our new Marked Hands for Review features in PT4, it is vastly different from PT3. Unfortunately we cannot mark RUSH hands for review using this method as the Hand History Viewer cannot be displayed when playing RUSH tables, this is because the hand histories are not populated in the order they are played.
I have contacted Microgaming to ask about your request, if this is something they will permit without breaking their EULA /TOS then it is an idea we can consider for further development after PT4 leaves beta.
Quote:
Originally Posted by PJs Ronin
PT3 is doing a great job at tagging the different tournies/SnGs that are available. For tourney (specifically SnG) players in PT4, will PT4 source HUD data from SnG filters. ie, if I play 45 man SnG will the HUD data be sourced from my 45 man SnG bank so that when I go to 90 man SnGs I will not (unless I choose so) see data for the same villains from the 45 man pool? Similarly, turbo data will only appear in turbo tournies/SnGs etc.
We are looking into this, we know this is something users want and need. No promises… but I can say it has been considered. I am going to contact you via PM, I'd like to chat with you on the phone about your idea to help us flesh it out as best as we can.
PS: Sorry for the tldr post, lost to discuss though. Expect a new Feature Preview Video this week - we need more feedback!
, Kraada confirmed that many EV features will be available...