-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to set the 'increase bet' button position/Use vJoy to click the 'increase bet' button #6
Comments
Hey, so, actually, and that might surprise you, but the program works just fine. I think so. But I have to admit, that I always knew this could happen, but I was ignoring it since it just happened when I ran the program on another PC, only having hardware that is - old, let's put it that way. The problem there, I thought, was my display, not running on its native resolution (old hardware, old drivers, not working correctly), causing weird scaling issues. And this seems to apply to other configurations, too. I did not know that. So, for this solution, I am assuming, you are not running your display or game under your display's native resolution. Although, 1920x1080 is pretty standard, so I could be wrong. I am assuming this, because I know, this issue can happen, when not using native resolutions and the program works just fine when using those native resolutions. But no guarantee on that one, as mentioned. A theory (may be boring and/or confusing to some readers)So my theory, so far is, that Windows knows the native resolution of your display and scales to that, but telling programs the resolution the display was set to (in the settings, confusing stuff, I guess). But when actually accessing raw pixels (which the program does to find the 'increase bet' button) of the screen, the coordinates used, correspond to the actual (scaled) image sent to the display. It may be also a variation of this. So it seems like the function, which searches for the button in question, searches not on the actual screen of the game, but outside of it (So when your game is 1920 in width it starts at pixel 1930 or so). The solutionFinally, a solution to this problem. As I already ran into this problem, I of course fixed it, so I could use it. And of course I made no efforts, making this anywhere near user-friendly, but here it is: Command-line optionsThe program has command-line options (mentioned on the project's website) and one of these is Actual steps to do thisI would recommend starting the program with
The console output while doing this should look like this:
It works! Or maybe it doesn'tSince I've already experienced this issue, there is the possibility that scaling may still screw up some stuff - or, to rephrase it, this didn't work for me, great stuff. If not, your cursor will probably not hit the 'increase bet' button, so it may be off to the left or right of the button. In this case, you could just repeat the process and move your cursor not over the button, but slightly to the left/right, trial and error. Or you could use the Use it like this: The saga continuesWhen actually hitting the button and playing in windowed mode, moving the window may actually screw up the set position, so this might not work anymore, when you move the game's window, so just keep the window in the same spot every time. This is also caused by windows' scaling not working the way I'd like it to work. But whatever. I would just suggest using full screen mode all the time, it works better than anything else. Final suggestions and commentsSince this issue is more about the documentation not being as accurate as it should be, so I will try adding a wiki or using similar stuff. Checklist for v1.1.1
Some more stuff:
ByeWohoo, you've made it to the end, you didn't die from dehydration, you didn't starve, that's good. |
Hello Markus. Thanks for your answer. I am running the game in screen native resolution 1920x1080 (not windowed), so there should be no scaling. I am not sure if you can trigger xinput strokes directly or if you have to create a virtual device first, but there is a xinput library: Besides this issue, bot seems to not be making right bets, when there is only a 1/1 Horse I always bet max, specially if there is no 2/1 (and usually win 10k), bot bet 100 for the worst, or max for the 2/1 (and lost). Thanks. |
So, XInput seems to be input-only, so no simulating a controller whatsoever. I'd have to look into this, this may be a solution to the whole problem, but probably optional, as this may be a lot of work simulating a controller. Also, this isn't written in python anymore, i've moved to c++ in favour of a far better performance (startup time used to be ~20 seconds, now <1 second), so this makes this even more difficult as there may not be a library out there, fulfilling these requirements. With the betting, I am not exactly sure what you mean, but with the newest version (1.1.0), these rules apply:
Another checkbox for version 1.1.1:
If it does not follow one of these rules, tell me which one and maybe send more debugging info. To do this, start with cmd argument It may have also something to with the scaling problem, the program not cropping the screenshots the right way. Since you are indeed running at your screens native resolution, are there any unusual things, programs, etc. you are running, that may cause these issues? If this has to do with the scaling problem, I am kind of screwed, but having some logs would help. Yeah, that's all. |
Okay, so for the controller thing, I could use vJoy to simulate a controller, but I'd have to look more into that, so this will only be optional for the next version. But thanks for the suggestion. |
…d by #6 Signed-off-by: MarkusJx <28785953+MarkusJx@users.noreply.github.com>
…ation requested by #7 and suggested by #6 Signed-off-by: MarkusJx <28785953+MarkusJx@users.noreply.github.com>
This issue is closed because it has been open 30 days with no activity |
Hello.
I would like to use autobet, but it fails to increase the bet, mouse is placed near the edge instead of over the button:
So it always bets 100 and views the race.
Perhaps you can use XInput to send pad's button strokes instead of moving the mouse. When you use a gamepad's d-pad the cursor will automatically move to the button in that direction.
Steps to reproduce the behavior:
Expected behavior
Autobet bets max when there is a chance of winning
Log files
There is no output.log in my computer.
Thanks in advance.
The text was updated successfully, but these errors were encountered: