Post by kozkon on Feb 5, 2010 19:36:45 GMT
First off if your getting a popup saying tesseract error, your def is probably set up correctly.
In Alpha 7.0 we started using Tesseract to read the chip amount and in 7.1 we used it to read the raise amount. Its a 5 step process that happens very quickly.
Step 1 - Looks in your data/chips or data/raise folder to see if it already read the amount. If it has it simply reads from that .txt file. If not it goes to step 2.
Step 2 - Takes a screenshot of the raise box or the chips amount (top left of the game screen)
Step 3 - Resizes the screenshot to make it easier for Tesseract to try to read.
Step 4 - Tesseract reads the shot and outputs a .txt file.
Step 5 - It cleans up the reading (takes out $ and ,) and outputs another .txt file then deletes files it doesn't need.
If your bot folds on call_upto's when he should be calling, chances are its not reading the raise box correctly. You need to go to your data/raise folder and open up a bunch of .txt files and look for errors. You should see numbers without spaces. Spaces are evil and will mess up the bot. So assuming you see spaces Tesseract failed in reading the true amount. We have a fix for this!
Different PC's, different resolutions, video cards ect. means not all computers will read the same. So I added a Resize option in your deadeyefred.ini that tells the bot what to resize the screenshot to in step 3.
[Resize]
chips =3
raise =4
If your call_uptos (data/raise) numbers are wrong try raise =5 then after a few call_uptos look again at the .txt files to see how the numbers are. If still messed up try 6 and so on.
Same for the chip amount. If your data/chips .txt numbers are wrong try chips =4 then check and redo until its reading correct.
Call_once and raises use the same principle as call_upto so if your having issues do the same as above.
In Alpha 7.0 we started using Tesseract to read the chip amount and in 7.1 we used it to read the raise amount. Its a 5 step process that happens very quickly.
Step 1 - Looks in your data/chips or data/raise folder to see if it already read the amount. If it has it simply reads from that .txt file. If not it goes to step 2.
Step 2 - Takes a screenshot of the raise box or the chips amount (top left of the game screen)
Step 3 - Resizes the screenshot to make it easier for Tesseract to try to read.
Step 4 - Tesseract reads the shot and outputs a .txt file.
Step 5 - It cleans up the reading (takes out $ and ,) and outputs another .txt file then deletes files it doesn't need.
If your bot folds on call_upto's when he should be calling, chances are its not reading the raise box correctly. You need to go to your data/raise folder and open up a bunch of .txt files and look for errors. You should see numbers without spaces. Spaces are evil and will mess up the bot. So assuming you see spaces Tesseract failed in reading the true amount. We have a fix for this!
Different PC's, different resolutions, video cards ect. means not all computers will read the same. So I added a Resize option in your deadeyefred.ini that tells the bot what to resize the screenshot to in step 3.
[Resize]
chips =3
raise =4
If your call_uptos (data/raise) numbers are wrong try raise =5 then after a few call_uptos look again at the .txt files to see how the numbers are. If still messed up try 6 and so on.
Same for the chip amount. If your data/chips .txt numbers are wrong try chips =4 then check and redo until its reading correct.
Call_once and raises use the same principle as call_upto so if your having issues do the same as above.