I think that HEM has a feature that lets you export the hands back to hand history files, which you can then point Point Sleuth at.

Yes. In the DB tab of Poker Sleuth's Options window, you can find the path to Poker Sleuth's DB. Exit Poker Sleuth and simply copy the file.

Poker Sleuth can't switch automatically. However, you can create different layouts for different parts of the tournament, then switch layouts as needed (right-click on any of the stats).

Thank you for the detailed testing and analysis. I'm working on hunting down and fixing the cause of the slowdown you're experiencing.

I should note that I've been sitting around sixteen tabling 6-max holdem (not rush) with my normal fast play (not fold-every-hand) and had no significant slowdown, so it probably has to do with rapidly changing players. The software is great, expect to see my purchase within the next 20 days.

Has anyone used montecarlo.dll in its own software for calculating the equity?
When I set to one of the players range of hands as a specific hand, such QsTd, the function returns all zeros equity.
However PokerSleuth calculator correctly handles specific hands (such as QsTd).

Which programming language are you using?

If I put QsTd into one of the example programs, it works fine.

I am using C++ Builder. Program code is almost the same as in the example for C or C++.

Montecarlo.lib was converted for Builder by using coff2omf. Perhaps the conversion is not correct.

In the event of an error in C or C++, the equities will all be zero, the return value of compute_equity should be non-zero, and the parse_errors structure should be filled in with information about the error.

If you'd like, you can send the code to me at support@pokersleuth.com, and I'll take a look.

Agthorr thank you for help. My program had bugs. The calculator works fine.

Agthorr do you plan to add support for everleaf or merge?

Maybe someday, but I have no short-term plans for them.

Then your program no longer supports anyone in the US market.

Not sure that it's wise to make your program obsolete for the majority of your customers. Frankly it's a horrible business decision.

You guys are funny - only on this thread because I tried this a long time ago and saw it was pretty much beta functionality (or at least, was lacking some of the core features/stability of HEM and the other majors).

Leave the poor guy alone - as an ex-developer, I know how frustrating it is to put a lot of effort to make a decent piece of software only to get maybe 10 subscribers. Basically, $20k of effort (or more) just to get a couple hundred bucks for your time.

He never stated upfront he'd support those rooms, and did any of you even purchase it? I always LOL when I see freeloaders complaining up the wazoo.

Dude calm down. Personally i was a beta tester so it's no big issue. However sleuth is imo the best hud on the market.So yea it sucks that it's useless now. I'm sure plenty of people did buy the program and it kinda sucks that agthorr has decided to leave them hanging. I have no idea how many people brought sleuth but i bet 1/2 or more was from the US So if i would say his #1 priority as far as this program goes should be adding support for American rooms. AG seems like a decent dude but i think he is wrong to abandon his customers It's also cuts down on potential profits.

We should swap names, I can be grumpy sometimes!

I just thought it seemed obvious he wasn't exactly actively supporting it, that's all. I really liked the +/- feature but saw that a lot of the HUD layout depended on 3rd party programming tools and bailed (not to mention a lot of stats just aren't in there).

TBH I wonder if a lot bought this. If so, then he should be adding that support. At the same time though, I can understand that, with the current confusion, no one's sure if those sites will even remain open for long to the U.S., or perhaps the other sites will come back soon enough and it will be all moot.

Just kind of bugged me first thing in the morning ( morning = grumpy!) to see two people complaining about lack of U.S. support (when it was the sites that really dropped the ball IMHO, by not having more compliance or backup in place earlier).