That error you posted is inconsequential. Note that preferably you should quit fpdb before checking the error file.

But nice that you seem have it working now, freerolls are one of the newest features
Can you try the things that failed again? Try bulk importing the histories first, you can check in the fpdb-log file whether it really imported the hands. If it did try playing another one of that game.

Bulk import worked great as well. Seems to be working now, at least for my current needs, thanks!

I was playing a razz freeroll on fulltilt and had the typical hud freeze complete with the mangled HH, but the strange thing was that I was running the exe version 0.20.903

so with the new .exe installer using the latest snapshot .903 do I still need to add extra files from somewhere to get things working smooth with vista?

I saw stuff about vista in the wiki, but I haven't done any of that yet.

So far it seems to be doing fairly well getting stud8 hands but it does tend to crash a lot, esp when using the hud.

I'm not sure if the crashes and errors are vista related, or just the newest snapshot being buggy, this is my first time using FPDB.

If you are using the .exe version, you should just need to set "run as administrator", and don't have to do anything extra.

The extra downloads on the Wiki are only needed if you want to run the "source code" version (which allows you to rapidly make changes to the software).


0.20.903 is built from the developers latest code, with lots of new features and bugfixes, but will contain some new bugs which need ironing out.

The 0.20.1 download is "stable", and most players, I think, are finding this version to be reliable.

The database structure is different between these versions, so if you switch versions, hands will need to be re-imported.


We appreciate feedback with any issues you can find. The project is very active, and a new snapshot should be available soon.

Thanks DangermaN, I'm going to have a good go at re-creating this; I can re-create the hud freezes, especially on the sourcecode version, but haven't been able to get the exe to lockup and have never had the HH's mangled so far.

Does this happen with one table open?
Do you have any other processes reading the HH's during play?
Are you XPhome SP3?
What import interval are you using (std 10 seconds)?

regards steve/gimick~

Probably best to take this to email gimick

Hi Dangerman, have pm'd my email address.

Steve~

A couple other things I have noticed here. These are low priority and I suspect tied to Windows 7 and the DWM, but worth mentioning.

Often when a HUD stat window is redrawn for a new player joining the table, that players stat window is always on top of other windows. So, imagine I have the HUD running, and open Firefox and place the browser over the poker window. I'll see a HUD stat window on top of the browser window. Doesn't happen all the time. I haven't been able to consistently reproduce this as a cause, but so far it appears that if I am covering the poker (PokerStars in this case) window with the other app screen or I can even have the app not covering but simply having focus when the HUD redraw occurs, then the new stats become foremost.

Popups (tooltips) on hovering. These things popup and won't go away until you put the cursor over them again. Not too bad except that quite often, just hovering over a random part of the PS window will make a tip pop up for a player that the cursor is no where near. <--that is the main issue to report. Seems like the HUD is not getting the correct coords of the mouse and firing the pop up. Again, Win 7 and the DWM is pretty screwy when you start hooking the screen. I have several apps that have had to be adjusted for this.

I am going to change all the exes to run in compatibility mode for XP and see if this helps. If there are any dlls that could benefit from this, tell me and I'll try them out too.

COKE_MAN,

I get the same problem on Full Tilt, the delay on tooltips is almost nil, and they act weird. I don't get those on any other site that we support (I don't have a Stars account, so I haven't tried that). I ---think--- it might be something to do with custom window classes that the more advanced sites might use. I've used fpdb on every other site we support, I think, and have not had it there.

I very rarely get a single hud stat window appearing on top of other windows, but it goes back down when that table window is focused and then goes back below. I've never really looked into it because it's really rare. It happened to me in XP as well as in 7, and I've had it also happen on lots of other apps as well. I think it's a Windows problem, personally.

I'm running Vista and I occasionally will have HUD stats appear over another open window also. Regaining focus with one click and the stats disappear. Maybe 2 or 3 times in three hours of play... on Stars. I'm still running the last version (not exe).

Dog

Stop the presses on the hosed hands. I've found the reason that I get corrupted histories, and yet after restarting the hud, hands are still importable.

I've got games in progress right now, but expect details later tonight or tomorrow.

.903 has quite a few bugs. It is the first pass at a range of new features, and a couple of things that are now fixed.

I'm not sure about the mucked card display for stud at the moment, so removing "stud_mucked" might make the hud a bit more stable for the moment.

In Vista 'run as admin' is essential as far as i'm aware.

I think Steffen is panning on putting out a .904 release within the week.

Sorrow

I'm sure we are going to strike a few issues with Windows 7 and its window manager given that we are using a cross platform toolkit.

I think that the new stat window forcing focus is common to all platforms at the moment. I think the mucked card display steals focus the first time it attaches to a window too.

I dont think we've had anyone that understands why the focus is being grabbed on the initial 'hooking' of the clinet window. Any light that could be shed here would be appreciated.
I dont think that is us - the mouseover events are part of the underlying toolkit, we just respond.
I will be curious about the results.

Sorrow

Any hints?

any idea why i can't view positsonal stats as it doesn't say "(todo)" or anything like that?
when i click just nothing happens

New problem for me

Whenever I try to start the HUD now, when it creates the player stat windows (VPIP, PFR, etc.), it only creates like one or two that I can see and theyre off in the lower right of my screen (The FPDB menu box pops up around there too). They also don't overlay the table window; when I click on the table window, it is brought to the front and the stats go behind it.

Positional stats was broken between 0.20.x and 0.20.90x - we know about it and are working to fix it.

Sorrow

Is Python 2.7 cool?

That's rather odd. Am I right in assuming you didn't edit the config file yet? Try deleting or renaming it, you can find it in the folder above the logs.
I'm sure it is, but nobody I know of has yet actually tried it. Windows users who want to run source on py2.7 should note that some of our dependencies are not yet available as installers for py2.7.

Such as pyGTK? I just got to that

If I just installed Python 2.7 & imported the tarball into a new PyDev project in Eclipse, what are the next steps for resolving these dependency issues?

You might have to install the dependencies from source, how that's done depends on the individual package. I know python has a "easy_install.py" (might be part of the setuptools package) script, you could try using that, but I don't know if or how well that works in Windows.

The bottom line on the HH corruption is the editor I use to view text files, when I view certain HH files from FT, they consistently flake out, but when I load those as binary instead of text, I can see no corruption and no reason why the editor would consistently fail at that same point every time the file is opened.

I spent some time exploring code pages and trying various ones thinking perhaps a code page was tripping up my editor as well as FPDB, but I did not find anything conclusive.

Just tried fpdb with py27 and happy to report that everything seems to work

A lot of software has problems with non-ASCII, FTP goes further and uses wide characters - the best thing to do about this would probably be to submit a bug report to the makers of your editor.