I have started playing around with the "Odds & Outs" software (v 1.00.10d)
and I believe it is counting the backdoor straight outs incorrectly.

Example

You: 45
Opp: 3A

Board: K93

I believe we have 3 fours + 3 fives, a backdoor flush draw with spades (1 out), and a backdoor straight draw (345). Since there are no gaps in the backdoor straight draw we can count it as 1.5 out.

That gives us 8.5 outs. If we multiply it by 4, we get 34% equity. Pokerstove actually gives ~ 30%, but it's close enough.

However your software says that I have 11.5 outs and 46%~49%.
The answer shows 6 immediate outs (no surprise here) and 5.5 backdoor outs:
26, 2A, 67, and

So basically it counted 1.5 out for every possible runner-runner straight combination, which in this case seems to be a huge overestimation.

Thanks for the feedback. Yes, it's not doing that exactly, but there was a bug in it. IT was already corrected a while ago, and there will be a new update soon. I'll post it in here when it's ready ago.

Long awaited. (Probably kinda overdue.) Looking forward though. Thanks.

do you mean me too ?
i think i got some good ideas there like putting the option to do just flush draws, or straight draws or overcards on the flop.
(of course as i said the flop would be random flush draws, aka flush draw plus pair,, flush draw with overcards,,).

I also like the idea of doing odds and outs with specific groups of hands or just 40 hands with pocket 5s then 40 with 67 suited for example.

i do think you should put in the option to hide the villian hole cards for outs, like you did for the flop trainer and have one villian there.

it also helps me to know if some of these things are possible, or like have to be in a v. 2 of it,

It's been two months and no update or fix for this. Can you please explain?

It's fixed already, we've had other things that have been going in, and we had to transition in a new developer onto APD. There's going to be a release this week though, and I'll post it in here when it's ready.

can i use this equity calculator on a live session? ive been told i cant use it on most sites given their terms and conditions

I honestly don't know the T&C's of every site out there, but the general consensus on most sites is that you can use tools like calculators, as long as they aren't telling you what to do (bet,raise,etc..). So it should be fine, but if you have any doubt, just contact their support and they will tell you.

New version out earlier this week. V1.00.02e

Feature highlights:
- New simple and advanced modes in Odds and Outs Trainer.
- Equity calculator check added in Odds and Outs. You can 1 click to check the actual equity you have when converting your outs.
- Various minor bug fixes.

Updated, now it won't run.

Ace Poker Drills has encountered a problem and needs to close. We are sorry for the inconvenience.

If you were in the middle of something, the information you were working on might be lost.


That is what I get when I try to run it after the update. It worked fine before.

Running on XP fully updated. Even tried to reboot the machine, and still have the issue.


Just tried to reinstall. Runs, but once I update, I get the same error message.

It's likely a .net issue. Can you try and update your .net and run APD again:

http://www.microsoft.com/download/en....aspx?id=17851

I'm getting this error:



whenever I try to play any hand in the Equity Calculator.

I start up EC, click 'Load from database', click the 'retrieve sessions' button, double click one of the sessions and get the hands from that session listed.

But when I double click one of the hands (or pretty much anything else there - one of the play hand controls (preflop, flop turn river buttons or play/back/forward), 'copy hand history to clipboard', 'show stats' or 'show opponents cards' I get the error above.

Updated to the latest version today.

Any ideas?

Same error still

I'm also not getting any stats (hide stats is off) or chipstacks in the Equity Trainer.

Having the developer look into it today, and will let you know. I may need a log file, but let me see what he says.

Thanks

They are working and testing a new build, and there should be one out tomorrow. I'll post an update in here when it's up.

Apparently had to add in a few other fixes, but a new update is out. You can just click check for new updates if it doesn't auto-prompt you on load.

Thanks, but it's still not working for me. It's now a different problem in the Equity Calculator though - when I select a hand that has been loaded from the DB, this popup pops up:



Click 'close' and it pops back up again a number of times - this could just be coincidental for the few hand histories I checked, but it seems to pop up once for each action in the hand history (forgotten debugging message perhaps? ).

Also, still not getting any stats or chipstacks in the Equity Trainer (these could be missing elsewhere also, but I'm not sure where they are all supposed to be).

Ok, thanks. A new developer updated the .net framework, and that's what set off these set of issues. So having the original developer go back over it and straighten it out. I'll let you know as soon as he's done an update.

Any updates on this?

There has been an update. Have you tried it, and are you still having issues? The developer is working on another one right now as well. I don't have an ETA though. Let me know what's going on, and I will pass the information on.

This is still the same issue as my previous post:

I'm getting 'No update found' when I run the update checker from the program
so I think I'm still on the most recent version.

I need to figure out equities, but am quite skeptical of this program, probably gonna do it by pen/paper/stove instead. I mean what if I think villain has suited connectors in a spot 30%? Or I think he's getting tricky flatting a normal raise hoping to get squeezed with premiums 10%? And how does preflop ever work? Going by some static ranges? Not exactly teaching to adapt if I'm not wrong. How is preflop calculated anyway?

Ok, thanks. We will have this fixed next update. I thought it was in the last oen by mistake.