So, does anyone know how to determine the edge of a roulette wheel using formula
[(Ball Drop x Skill Factor)+(1-Ball Drop)x(Random Factor)]x bounce factor x 36 ÷ sector length -1
Like what data number to put in the above formula to determine the expected edge i would get out of a Real wheel in a real casino. I want to quantify as much data as possible is becasue modern wheels does not have the high edge back in the old days anymore due to ivorine ball being used, wheel being leveled regularly and bounce of the ball has a wide range.
To give some info, I do have the roulette analyzer using data such as rotor speed, barometer, drop to final number, diamond smack, diamond smack position. I also seperete data such as dealer, cleaniness of the wheel, etc.
Or should i just find a good wheel to play which the edge is so big that a human error can be ignored when
Collecting data (slightly off rotor speed, slightly off drop and final)
Around 60% roulette computer accurancy when predicting the dimaond.
±3 pockets when clocking rotor speed using MyRulet
Given there exist some very old wheel but it is rare, it might be better off to spend time finding a good wheel than spending time to sharpern my skills which is not gurantees to be successful.
I once created an Excel file that was able to perform a similar task. The file took input data regarding ball jumps and the accuracy of predictions. It then multiplied each corresponding pair of values together and generated a chart based on the results. I couldn’t find it but it can be created relatively easily.
I think more than one of us has made some sort of file or even program, that was relatively easy to beat on inputs.
However, in reality, things are a bit different and it is not so easy to win
Don’t want to upset the readers - it is still possible to win and not so weakly. However, this requires knowledge and skills and the main thing is not to try to beat someone you can not.
It is better to spend some time looking for a weaker opponent, but for that, you need to know how to recognize him
Yes an easy wheel would have the following characteristic and i would appreciate if someone could confirm this
A good wheel should have a short bounce and tight range of bounce, lets say 13pockets to 23 pockets 70percent of the time
A good bounce meaning the ball is likely to be a big and heavy ball.
A good wheel should have a dimaond such that when the ball hit the diamond, the dimaond cover the whole ball instead of the ball only hit the tip of the diamond.
Whether it is a heavily tilted wheel is although important but the above is more important as modern rc like the myrulet computer should be able to predict a 3diamond game 60 to 70 percent accurate dimaond.
Well, not really - everything you list is desirable, of course, but not always necessary.
It really depends on the method of play.
RC - does not predict, but only makes a calculation and gives the result as an offset from some point.
This is about the same thing that a visual ballistics player does.
That is really in any method we have a certain point and we have a real result.
And here begins the most exciting thing - whether the player is able to detect the correlation between his measurements and the final result.
I talked to many players who also use VB methods, also who use RC help and I got the impression that to find the correlation between the measurements and the final number, as well as to collect a good database - for them very hard work and may not even be feasible …
Certainly, analyzing the data is the key. This can be achived by measuring rotor speed, drop number, final number, air pressure, dealer, dimond hit and diamond hit postiion. I also agree with you that vb players could have the same effect of an rc and from prediction to bet time is acutally faster. However, the vb method i am current using is based on a single dominant dimaond, i am actively looking for a vb system which can define a 3 dominant dimaond wheel.
Analzing is hard to someone but to me it might not be. I have the help of a software developed by laurance scott which could allow me to make bets based on the drop to final bounce distance under a given rotor speed. I would also use the inbuilt barometer app function to measure the barometer and observe marks and scratches of the wheel whether the casino have tampered with. Such that i have an idea of under which rotor speed, dealer, level of tilt of the wheel, ball used to make my decision of betting how many numbers away from the point where the ball exit the ball track.
I do not see here big difference … theoretically, a method that works on a single diamond must the same work on three diamonds only the player must have three times more data and do slightly different calculations.
Essence always is the same - to find correlations - relationships between what you know and what will be.
If these three diamonds are such they go one after the previous so that the ball can hit 3DD then to the next 6DD when are made 0.25 rotations more and to the next 9DD when are made 0.5 rotations more. Measuring ball speed usually will not help in such cases and need to look for some compensations where the hit to the next diamond has say shorter scattering or something that kind…
But still, one diamond must have a bigger % of hits…
Of course, the distribution of diamonds can be in other order say 9DD then 3DD but when are made 0.5 rotations more or 6DD when are made 0.75 rotations more, that is absoluttely other variant
The method of working on a single diamond is just that i assume the ball would hit that diamond. I measure the rotor speed then use a card such that for a certain rotor speed, i would bet on lets say the ball have 5 revolutions to go and exactly at the dd12 diamond, the 3oclock number is the drop number
I don’t know what software you’re talking about. However, I have been in contact with Laurens and even discussed some programmes with him…but I trust more the programmes that I have created myself
Generally speaking, often it is not about programmes but about the player’s abilities - programmes do mostly only calculations, but it is up to the player to decide what to use and how to use what programs calculated.
And this is where mistakes are mostly made…
Kind of hard to answer correctly, as the answer will include something like - experience… but from some small amount I know if are worth collecting more data.
And really talk is not if the wheel is playable or not - all wheels are playable the main question is how big an edge is possible to have…
Yes i can think of 2 ways which hitting the wrong diamond would not matter
Scatter overlap, meaning the scatter of might be 18 pockets and 25 pockets, there are 2 bell curve with 2 meam if you plot the graph.
Compensation rotar speed, if the ball miss dd3 and hit dd12, such that ball is anticlocwise, the clockwise moving of the wheel would have covered 3 times the distance of the ball from dd3 to dd12 so that the drop number would meet the ball again. This is likely to be a 2 second rotor. This goes the same if the ball miss dd12 and hit dd3, the rotor speed just need to be slow such that the drop number meets again. (6 seconds rotor speed)
However, since the RC could predict the correct diamond with 70percent accuracy. However, sometimes the ball speed could go wild becasue clocking the ball could only see 2D motion but there might be a rotational force within the ball or the ball for instance or the ball has some hand gels stick to it. If you only wait for a good conditions, my vb method cannot currenly predict as accurately of an RC.
I have thought of a method to do that but need to develope. The logic is that i can measure the rotor speed pretty accurately by counting 2 seconds. Then i would count the 2 seconds again as the ball is at dd12, if the ball is at a 3 oclock postion, it might be hitting dd12, if the ball however is slightly quicker and is at the 4 oclock postion, it might hit dd3. However, i have yet to test whether human reaction error is enough to define a diamond because the boundary might be 0.5 pockets, 1 pockets or 2 pockets and that for a earlier revolution, it is probably easier to define