Programming roulette computer

Hi guys, I m new to this forum and had been reading about roulette and roulette physics, on how to use various techniques like visual ballistics , wheel bias, dealer signature etc. to obtain advantage in roulette. I am a computer science student and can develop some programs of my own using .net and java, currently i am working on developing a roulette computer program, so far I have estimated that I can determine the wheel position when the ball leaves the rim (before hitting one of the deflectors/diamonds) but I am unable to determine the (chaotic) path the ball travels after hitting the deflectors??? :frowning:

Could anyone of you provide any kind of source code material that roulette computers use or any kind of java code snippet that is used in roulette computer programs… so i can get an approximate idea about the program???

Thanks…

Hi themechanic and welcome!

I believe that no one can determine with certainty where the ball will stop after hitting the diamonds.

It can depends on ball speed, hit point (top, middle or bottom of the diamond), rotor speed…

There is no accurate way to calculate: usually we do an average of the scatter of previous spin, to try to predict where the ball will stop.

About technical info and source code for roulette computer I think only Forester could hep you, but I don’t really know if he wants…

You may try some other forums, we do not deal here with Java, FF devices are programmed in assembly which is 100s time faster and more accurate in time measurements. I personally have no interest in developing Java applications. Hardly that anyone will help you’ it is a matter of playing roulette for years and experiencing what is required and what is not. There are many useful posts at the forums or you can get books form Laurance Scott where he nicely explains the theory.

Hi rremoroulette thanks for ur response

It can depends on ball speed, hit point (top, middle or bottom of the diamond), rotor speed...

Thanks for providing this information. Yesterday while going through the forum I found this http://rouletteplace.com/index.php?topic=273.msg2704#msg2704 from forester. However the links to myrulet.com forums seem to be missing. I wonder what information it was!! ::slight_smile:

There is no accurate way to calculate: usually we do an average of the scatter of previous spin, to try to predict where the ball will stop.

I do agree with this. Its almost impossible to predict one single pocket where the ball will land but I am very curious to know how Eudaemons http://en.wikipedia.org/wiki/Eudaemons were able to achieve freaking 44% advantage :o over the house. I do want to read that “Eudaemonic Pie” about their work… btw have you read this book?? Does it contain only the story or does it contain some information on their experiments as well??

You may try some other forums, we do not deal here with Java, FF devices are programmed in assembly which is 100s time faster and more accurate in time measurements. I personally have no interest in developing Java applications. Hardly that anyone will help you’ it is a matter of playing roulette for years and experiencing what is required and what is not. There are many useful posts at the forums or you can get books form Laurance Scott where he nicely explains the theory.[/quote]

Hello forester thanks for ur response
I found a very interesting topic http://rouletteplace.com/index.php?topic=1481.0 I have not went through the entire posts but seem very interesting to me by looking at all the pictures :D. Yes I apologize for posting about Java and all that, but it drew my attention towards these roulette computers and their programs when I watched some videos at http://jafcoroulette.com/index.html. Also about the Eudaemons obtaining like 44% advantage (as mentioned in my above post) these are damn good predictions in-spite of the scatter the ball encounters after hitting one of the deflectors!!! Although watever might be those FF devices (i have personally not seen one before) as far as I can recall these microchip devices are all coded with conditional and logical coding methods which won’t be difficult to interpret if we get its source code. Simple example would be “IF” it rains today “THEN” i am not going to school :stuck_out_tongue:
So I was wondering even a little piece of informatino to deal with the logic after scatter could help me out… :smiley:

Anyway s I forgot to mention before but I am not working on constructing a roulette computer to hide in my shoes or something like that, rather I am working on just a software of my own that would help me to win at “Online Live Casino” (especially Live roulette)

Oh yes and about that book “Professional Roulette Predictions” dude can I get it a ebook copy for free anywhere??? ::slight_smile:

  1. You cannot find Laurences books for free, you have to buy it online.The second edition is more about analyzing where the first book gets you into the game play and understanding how and why the techniques work.

  2. The Eudaemonic Pie is more of a story book and it was a long time ago, today technology is improved.
    The the computer is dead accurate - when used correctly. You still have to know how…

  3. For online live roulette - you cant use a computer because they call NMB before the ball is spun in most cases and where its not your predictions wont be accurate because of the internet latency and strength also the video tends to pause and slice while you watch so you wont be able to map the ball precisely

  4. There is no possible way you can calculate or find out how the ball will scatter on a wheel in advance or use it on every wheel, on some its predictable on some its not of course on different wheel speeds etc. There are too many factors that are involved like someone told you before you have to observe many spins and see if theres a predictable pattern in the scatter most of the time.

The key isnt in knowing or finding a system,technique thats 100% proof and that will work every time on every wheel which it wont and doesnt exist . Its about knowing how to find and beat the conditions on a specific wheel.

!!! ITS NOT EASY !!!

Ill suggest you as a first step to first make lap timer with accuracy better then 1 ms and triggered with an external clocking switch
and a stable vibrating metronome with adjustable time.

Thanks to all for taking active interest in my query.

@forester
wow, from what I read I assume that the device will be a little bit difficult to find ::slight_smile: ::slight_smile: ::slight_smile:

@bagun

The key isnt in knowing or finding a system,technique thats 100% proof and that will work every time on every wheel which it wont and doesnt exist . Its about knowing how to find and beat the conditions on a specific wheel.

Thanks for highlighting this out along with ur views mentioned in above four points. Yes, I agree in online live roulette NMB is called before the ball is spun and I also agree with the video latency u mentioned about. Keeping in mind “Its about knowing how to find and beat the conditions on a specific wheel.” I would like to share a little program that I made, a slight similar thing is mentioned in a video here genuinewinner.com/vb.html. This is very basic approach and I am really interested in improving it with help of experts here…

Starting first as you can see in following figure I have divided the roulette wheel in 4 Quadrants as Q1,Q2,Q3 and Q4.

Q1: 22-0 (10 pockets)
Q2: 32-34 (9 pockets)
Q3: 6-10 (9 pockets)
Q4: 5-9 (9 pockets)

The objective of the program is to find the forbidden quadrant among the above mentioned four for every spin (using separate databases for each anticlockwise (AW) and clockwise (CLW) spin)

Method:
Taking note of every spin consistently, software records the reference pocket (the pocket where the ball is before spin) and destination pocket (the pocket where the ball is after spin), calculates distance i.e. number of pockets between reference and destination in clockwise direction and saves the distance value to database respectively.

For example: If the history of wheel is as below starting at 0 as occurrence of rotar’s AW spin… further 19 as rotar’s CLW spin etc…
0,19,6,27,8,5,12,16,25
the software reflects values as Q1:1,Q2:1,Q3:1,Q4:0 for next rotar’s CW spin…

Working:
Since initially the ball is at 0 and the rotar is moving AW we take 0 as reference number for next rotar’s CLW spin. Spin… the ball stops at 19, so calculating distance we get number 19 is three pockets away from 0 so the CLW database gets its first value as “3”. Now pocket 19 will be reference pocket for next AW spin. Spin… ball stops at 6. Number 6 is seven pockets away from 19 so the AW database gets its first value as “7” and so counts the respective values on and on and on for several hundreds of consecutive spins and keeps track of all the distance values for AW and CLW spins separately.

Now say we have successfully recorded 100 spins (50 CLW + 50 AW) , and the ball is in pocket 21 (see figure below) and the next would be rotar’s AW spin…now lets say we have 15 records of distance value as “7” (yellow), 5 records for value “19”(green),15 records for value “28”(violet) and 15 records for value “35”(gray) in our AW database then, the software will show
Q1: 15
Q2: 15
Q3: 15
Q4: 5

So the quadrant with lowest value is forbidden. and bets are placed on number in Q1,Q2,Q3.
If betting unit is $1 then,
15+15+15 = 45 times I will win $8 ~ $360
and 5 times I will loose $28 ~ $140
i.e. $220 gain for every $1400 bet
i.e. $15.71 for every $100 bet ~ 15.7% advantage for this particular spin based on previous history.

Now, advantage for each spin may differ from spin to spin , CLW to AW etc… however if we consider to bet against “perfect” roulette wheel and so bet on Q1,Q2 and Q3 its certain that we win 75.68% and loose 24.32% of our bets so next thing I calculated is cumulative winning percentage (means how many times i really won applying the above quadrant method) so any value you get above 75.68% is reducing house advantage actually.

So for example say I am getting 3% advantage for next rotar’s CLW spin but I observed that the cumulative winning percentage for clockwise rotar spins is below 75.68% then I won’t bet.

Its about knowing how to find and beat the conditions on a specific wheel.

So I will wait for the spin with advantage along with cumulative winning > 75.68

I know there is lot of scope here for improvement here, member’s opinions, views, any ideas, suggestions regarding this method is highly appreciated.

Thanks

For that you do not need database you could simply mark on each of your 4 areas when you get such distanced hit. If more data is required some people use XL sheets to track real dealer signature and bias.

Your explanation is only theoretical since dividing wheel on 4 parts will not create you an uneven distribution where on some parts you’ll have an edge. Dividing it in to 4 fixed parts makes things worst since 9 and 22 which are next to each other are in different groups.

Link for video you provided has nothing to do with what you explaining so I am puzzled why you linked it then talked about something else. We do not promote scam here (you can read about genuinewinner scam all over the net).

Thanks for the reply forester

regarding that video…uummm maybe I was thinking to post something else and mixed it up…forget the vid :stuck_out_tongue: wat’s explained in rest of the post is more important

btw u said the explanation is only theoretical, maybe I was thinking rather than dividing wheel into 4 quadrants ,what if we deal with each pocket individually , so 37 quadrants total. If we do it the same way we can identify individual pockets with less hits, so that way we can avoid the worst as u mentioned 9 and 22 are next to each other but in different groups.

Still I don’t think this technique is enough to overcome house advantage in long run in true sense. Could you suggest any idea to improve accuracy of prediction here!

Understanding roulette wheel and exploiting possibilities.

http://rouletteplace.com/index.php/topic,1481

Here you can read about all steps.

Yes, if you use single numbers you should get better result.
Let’s say each number gets 5 hits but 22 and 9 get 10 hits.
In your case it would be 2 areas to play wanting you to cover 18 pockets, with single numbers it would be only 2 pockets making advantage higher. So your areas shouldn’t be defined by you; but by group of numbers that is getting the most hits.

Currently working on updating my initial program to track the hits with respect to initial reference pocket and the destination pocket separately for ACW and CW spins and defining forbidden zone instead of using self defined quadrants as mentioned in previous post… 8)

However I just noticed some threads here regarding wheel bias… I think including this method as well in above program would give slightly more accurate oriented outcomes in defining forbidden zones however I am not entirely clear about the concept of wheel bias… ::slight_smile:

Is wheel bias all about just keeping track of numbers which get more hits… ?
Or Is it about taking note of dominant diamonds and then estimating the forbidden zone considering the position of rotar when the ball hit the DD etc. ???

I did made a program to record hits for numbers at one of the online live roulette wheels, its results after 3502 spins were as below:

Number Hits


13 120
24 108
32 108
34 106
10 105
28 104
22 103
6 102
2 101
3 101
29 101
26 101
16 100
18 99
7 98
8 97
11 97
23 95
9 94
12 93
30 93
20 92
0 92
1 92
36 92
4 91
21 91
31 91
14 86
35 86
27 85
25 85
17 82
5 82
15 80
19 79
33 70

As you can see in 3502 spins, ball has landed in pocket numbered 13 about 120 times and so on…
The only mistake I made and quite a silly one, I mixed up the CLW and AW spins together instead of keeping a separate track of them. Now the new program I make I will keep separate track the same way

Now that the program will calculate hits based on the ref. and destination pocket method along with keeping track of maximum hitting numbers, still in addition I just want to know is there anything else that I can keep track of to know the wheel bias in better way. In short Is there any another method to find wheel bias then just keeping track of numbers with maximum hits… ? ::slight_smile:

Number Hits ---------- ---------------- 13 120 24 108 32 108 34 106 10 105 28 104 22 103 6 102 2 101 3 101 29 101 26 101 16 100 18 99 7 98 8 97 11 97 23 95 9 94 12 93 30 93 20 92 0 92 1 92 36 92 4 91 21 91 31 91 14 86 35 86 27 85 25 85 17 82 5 82 15 80 19 79 33 70

To find the maximum optimized advantage possible in above data. I have created a function which I myself call the optimizer()
Now its says to bet on first 15 numbers here i.e. (13,24,32,34,10,28,22,6,2,3,26,29,16,18,7) only.

As you can notice if u bet only first 10 numbers the approximate advantage is 8.76% while if u bet 9 or 11 numbers its < 8.76%
So the function calculates the best top numbers to bet on… this one’s good too isn’t it? :smiley:

Now its says to bet on first 15 numbers here i.e. (13,24,32,34,10,28,22,6,2,3,26,29,16,18,7) only.

Oops a little bit modification "first 10 numbers only i.e. (13,24,32,34,10,28,22,6,2,3) only. :smiley:

Google, “roulette bias wheel”, you’ll find information and many sites selling software as you want to make. Most bias players i know use XL.

Or a calculator!

I have one simple question regarding VB

Consider a wheel with 4 vertical diamonds. Let 12 o clock and 3 o clock be the DD’s for ACW ball rotation. So as we continue to play using VB , do we need to keep separate records of scatter for these DD’s ???

It’s probably better if you do.

You can take data of about 100 spins for each diamond then same amount for different rotor speeds. All together few hundred spins so you will know is it worth doing it.

here you have some examples.
BALL JUMPS SCATTER
http://rouletteplace.com/index.php?board=19.0