Update Beta 0.3.2 Posted

http://www.pokerobserver.com/downloads.html

This is a minor update, mostly intended to help me resolve some issues a few of you are having.

* Fixed: Save Quick Action Panel context menu does not make Quick Action Panel disappear
* Changed: NaNs converted to "oo" to reflect Infinity
* Added: More detailed logging to help with those having trouble with getting stats on Stars

Observations:

When surfing the net, and playing on Stars, when Observer tries to steal focus oftentimes it shuts down.

When enabling cockpit and my tables are overlapping, the little icons disappear(the ones to make the cockpit come out or whatnot) I just disable and re-enable them to make them show back up, but whenever another table overlaps the icons they always disappear.

I went through and enabled a stat and made it transparent. It usually shows with a black box behind it(Opaque setting) and then if I scroll over the stat and then back off, it is transparent. This happens on a lot of stats(not keeping transparency)

youretoast:

just want to let you know thanks for the product so far that youve made, and although i know there will be some bugs when the final version is released i will look very much forward to purchasing

I don't know whether mine just isn't working or I'm dumb...but I have no ****ing clue how to work this thing. No stats ever show anywhere and I'm about 30% lost trying to figure out the cockpit thingie. Are you going to have like a basic video or whatever shopwing how to set this thing up. I've used PA for awhile and I'm surprised I'm having trouble figuring this thing out but im lost.

If i say had 2million 200NL hands and I open up 8-10 200NL tables and have PT3 and PO running....eventually i should probably see some stats on the tables right?

I will look at the stealing focus thing today. POH shouldn't be stealing focus at all, but I believe PokerStars does, so maybe its having an unexpected impact on POH.

Schawallie, have you by chance tried 0.3.2? I'm not positive, but its possible it may have resolved the Quick Action Panel disappearing problem. I'll look at this issue as well.

The stats you made transparent: were they normal stats or combo stats?

Thanks for the feedback and I'm glad you're enjoying it.


Its really simple to use -- once you get stats! Actually, I will be posting a video pretty soon, but it will mostly be for people new to HUDs because for the most part, I believe POH is pretty intuitive. But its NOT intuitive if you don't see stats (because there's really nothing to configure without the stats).

So the next question is: why aren't you getting stats? POH is obviously recognizing your tables. When you have as many as 2 million hands, it will take a while to pull the stats up initially. The problem right now is that I have not implemented a caching mechanism and unlike HEM, PT3 doesn't compile stats, thus a caching mechnism is necessary for big databases. Can you try a couple things? First, if you don't mind, create a new PT3 database and start importing hands with it while playing 1 table and see if stats show. Alternatively, try playing one table with your big database and waiting up to 10 minutes or so to see if stats show (by the way, once stats show, future queries are much faster).

Finally, if you still have problems, make sure you're using 0.3.2 and enable logging and send me a the pohlog.txt log file from the main POH directory.

For everyone's information, I am holding off on implementing caching until I determine which direction Josh is going to go with it. He's indicated that he might create some sort of caching functionality (which is needed IMHO), but I'm not sure whether, if he does that, it would be accessible by third party programs. Perhaps he might also decide to create a compiled stats table like HEM. We will see.

The biggest problem with POH & large PT3 databases is that even when the stats do show up they update fairly slowly, and when players leave & new players sit down POH shows the stats of the player who left for a long time, making the HUD really confusing and even detrimental if don't pay close attention.

Is Party support coming soon?

I will see what I can do about fixing this precise problem. When a player leaves, his stats should be removed; if he is replaced by a new player, his stats should b replaced. I thought I had that pretty solid, but it might need some work.

I also am going to look into workaround for large db sets; ie. start some testing on employing different filters. One thing I'd like to see those with big DBs try is setting the filter to pull only, say the last month's hands. I'd be curious to see if you get a performance improvement. FYI, I have not spent much time on examining the PT3 indexes, so sorry for my uncertainty on this.

I need a few volunteers to do some real testing. Not having access to anything other than play money tables makes Party support a little difficult. Other things about Party make is super easy. In terms of timing, I'd like to do some testing by the end of this week or over the weekend.

I'm 2-tabling right now and set filters first to 30d, then 7d, not helping at all, still taking half an eternity v 0.3.1

Also the download new version button at the bottom of POH screen apparently does nothing

Thanks for following up. Just so you know how it works, changing the filter during an existing database retrieval won't affect that retrieval, but it should affect future retrievals. So to verify that its not helping, you should change the filter and then restart POH. That way, the filter should be effective upon the first download of the data when you restart. Try that if you didn't already and see if it makes a difference.

The Download button is non-operational in 0.3.1 but should bring you to the download page in 0.3.2.

Using 3.2, The stats are normal, and disappearing didn't stop on 3.2

Also, it is shutting down when u have action, so like Pokerstars pops up and then for some reason POH is shutting down occasionally when Pokerstars steals action from something like Firefox when I'm browsing.

When you say "shutting down", do you mean its locking up or does it actually return an error and close?

Oh yeah, forgot to mention I did that (figured it would work somehow like that), no dice.

OK....I will see what I can do about optimizing the data retrieval. Once I finish, what would be really interesting to know is how much it improves, if at all, for you. To know that, of course, we'll need a baseline, so if you're so inclined, track the length of time it takes to show stats from startup and initial import now; then when I release an optimized version, we can see how much it improved. You can PM me the result if you want. Of course, if you don't want to go through that trouble, no big deal because I'll do my own comparisons.

I run an Emachines T3985 with 1 million byte RAM. It is an older computer, but I never had trouble with PAHUD, PT2. With pokerobserver and PT3, it is causing delays in your PS functions, even with one table. It is difficult to use with 2-3 tables and I had one lock up. I'll retest when this issue is resolved.

How big is your DB JP?

Traditional windows Vista error that says windows has incurred an error with Pokerobserver or whatever that is.

My data base is just over 65K hands for PS which is all the hands that I have in PT3. Once it locked up without returning any visible errors, but usually it just causes delays in your actions while playing at PS or delays in the game play.

when i right click on one of my stats, (hero's) and change it to session, it just disapears and doesnt come back. Happens on both xp and vista, with vista in classic mode with that feature disabled.

I currently have a 2.3 million hand DB and 3GB RAM...The HUD locks up as soon as I get the action buttons on Stars 6-handed NLHE tables.

Scott

I've had this happen. When I exited HUD observer and restarted it, then this worked but the program causes game lags.

JPFisher, It would be worth knowing if you experienced similar lags with AHK HUD (if you ever got it working).

This would enable YoureToast to know if the problem was with the database access of the code or caused by another section, I think.

JP's symptoms are different than the others. And he has a small DB so that is likely not his problem (although I'd be curious to know the answer to your question, dave).

I have lots of code optimizing to do, particularly for Stars. The biggest problems I see, however, are problems associated with big PT3 databases. One thing I'm trying to figure out at the moment is what generally is the cutoff for decent performance. I've had issues with some people at 2 million hands, but not many, other than the JP-type-things just lock up complaints. Clearly, as the DBs get bigger, theres going to be problems until I or Josh creates cache functionality. But really what I'm interested in at the moment is optimizng the code for non-large DBs so that people with regular sized Dbs can use it without fault.

Yes, this is a known bug. If the session stats are 0 on certain stats, the result of the right-click session stat is an emply stat, which may never become visible again. Its a pretty easy fix and should be done in the next release. Also coming will be the ability to switch all of a player's stats to session stats in the context menu.