Hi Punter,

pot size is calculated in the following manner:

pot := ((pot + call + hero_bet)* (frac) )+ call

which in youe example would be

pot := ((24 + 18 + 0)* (0.75) )+ 18 = $49.50 - As you expect.


I can't think how it would arrive at a figure of $36 (or was it $34?).

It must have failed to retrieve some value, but I can't think what...

If it failed to pick up the pot size, but did reg the amount to call, that would be (18 * 0.75) + 18 = $31.50 - about as close as I can get missing out variables.

Was the table obscured in any way? Pot size, Call & raise buttons must all ve visible for it to work.

Was this a one-off freak or does it do it every time?


dave.

Then it is certainly the problem of having a negative value in the variable.

You should be able to easily solve this by setting the left monitot to be the "Primary Display". Is there any reason this is not possible?

dave.

Very few, by my estimation. I apologise to those on FT with no working solution.

I have been slightly sidetracked by making StarsPlanner, but new FT code on the way shortly

dave.

Hi,

Yeah it was 32$ ! Ive just checked in HH. I will experiment a bit more and check exact raise amounts but my impression is it often raise incorrect amount (like minraising instead of more when I 2/3 potbet).

EDIT : is it possible that its caused by overlay ? (I play 6tables with some overlay)

Four monitors should not present any problems, providing the "Primary Display" is the top left screen (2x2 setup) or the leftmost screen (4x1 setup).

It is important that the origin of your desktop (as determined by Windows) be the top-left of your setup, as it would be with a single monitor.

This is only an issue on Stars, where Image-Matching is required.

Try it, let me know how you get on

dave.

Hi Oreo,

Glad to hear it is now working for you

It should be super-quick.

If it is taking ~2 seconds per action, my first guess is that you are running with "debug=1" still enabled. Change that back to a zero, save, reload the script.

This introduces approx 2 seconds of delay, so that you can see where it is looking for the pot/ call buttons etc.

Or not?

dave.

Absolutely - The script must be able to actually "see" certain areas of the screen. These are the centre-top "Pot:" indicator, and the bottom-right Fold/Call/Raise buttons & slider.

Stars technique has to use image recognition on the window itself (there is no sensible way to get a realtime HH) - If these areas it is looking are obscured by another table - no images will match, it will assume a zero for that value.

It also checks the area where the cards appear to determine street - but I dont think it actually needs to "see" this (different technique used), and it's not such a big deal if it can't get the street - it just assumes pre-flop.

How do you lay out your tables?

dave.

my primary monitor is bottom left in a 2+2, (square-type) arrangement of 4 dell 2001 fp's.

and i use 1600x1200, so is this 3200x2400 in effect?

in display properties bottom left (monitor 1) shows as 0,0 bottom right (monitor 2) shows as 1600,0 top left (monitor 3) shows as 0,-1200 and top right (monitor 4) shows as 1600,-1200.

i had them configured with the bottom 2 as #'s 1 and 2 because they are on the primary video card and the top 2 are on the second video card.

so with this configuration, would i have to reset top left for primary for the coding to work correctly?



thanks.

Damn so thats the reason. I dont have 2nd monitor yet and I like playing with overlay (I very much prefer it to playing smaller tables ). Isnt it possible to use that "diffrent" technique for reading all the action too ?
Or maybe it doesnt matter if the table is on top. I think in windows all the graphic from the table si somewhere in the memory. I guess it may be too time consuming to do it by mayeb not. I am not a good programmer.


I dont use any software for it because as I said I need to play with quite a big overlay now.

Correct, it will work perfectly if the window is on top (which it usually is, when the action is on you)

The problem is at the moment the current AHK image matching function only operates on the specified an area of the screen, rather than a window.


Just thought of a quick and easy hack to fix it though:

Hows about forcing "always-on-top" for the table, whenever the image searching is in progress?

I'd imagine you would not even notice this, but it would prevent another table popping up and breaking the image match.

What you think?

dave.

Hi 2easy,

With this configuration, the top two would cause errors, due to the negative co-ordinates.

The bottom two would be fine, but I'm presuming you have all these panels for the purposes of putting poker tables on them

Yes, do this and it should work fine. Is there a reason you can't change this? Do the additional VGA cards refuse to act as the Primary?

And it's an easy thing to change back and forth (in display properties) should any other apps require to be run on the primary monitor. DirectX / OpenGL games/apps in full screen mode are the only thing I can think of that want the primary display.

ill give it a try when im able to play a bit later tonight.

yes, there is a dvi and a vga for each card, thus inputs for four monitors.

thanks for the help.

It works, but just wondering if there is any other alternative

Am I the only one who has got this issue?

i don't see a "bet pot" button at all using the hyper-simple theme. if i right click on the "Pot: $xxx.xx" amount, it will input the correct number into the bet window if i'm initiating the action on that street. i also don't get a popup from the system tray like i saw in a few other screenshots. the mouse wheel does work for me though.

is there an updated version, or is it just v.01? and if so, could we maybe start a new thread for this script with a link to the most updated version in the OP?