This data is based on more then 400 spins for each rotor speeds. Then data was simulated to represent 1000 samples.
Data was collected from tilted wheel, only from spins where the ball hits dominant diamond.
One set of spins was where the rotor was 5-6 seconds per rotation and the other one was where the rotor was about 2.5 sec.
The ball used was 20 mm diameter slightly yellow, material probably Teflon.
5 sec. rotor BLUE graph
positions 10,11,12 (marked as “A”) from place where the ball is hitting rotor we have the highest hit rate The ball stops on group of 3 pockets 168 times in 1000 spins. Every pocket in average gets hit every 17.8 spins.
2.5 sec. rotor RED graph
We can see that actual pick point A from previous graph disappears.
It become wider and I marked it as “B”
Pockets around point C have hits every 24.4 spins.
Green line represents average expected hits per pocket.
You can see that pick point B due to faster rotor is shifting to a bit greater distance from impact with rotor. But really it is not worth playing it since it gives us only a small chance.
Most important to notice here is that actual relationship will the ball slightly bounce back and stay around spot where it hits rotor, or will it start bouncing, is changing.
On fast rotor impact with ball is stronger more energy is taken from the ball and more often the ball jumps backwards or stops instantly. That is why we have created new pick point C. It is not so high as A.
But if we want to play fast rotor it looks it is better to play around position where the ball hits rotor.
I was explaining these fey years ago in boys club but here it is again.
Of course this doesn’t have to be valid for all kind of balls but definitely it is good to be aware of it.
Pick point C is created from 2 components.
One is when the ball hits and stops there, the other one when it hits the edge and bounces almost 37 pockets.
thX FOR THE POSTING Forester
reminds me of the convo we had that kept me up to nearly 2 in the morning
point being,I think it would be a great advantage to the player to have this data while hees playing :
any thought on this compadre
your very own
Is this a low fret or are starburst?
Sony HD camera is good for porn??? I didnt realize that before. ;D
you have any Background pornhop HD Sony camera.
I tried to record ball in HD with Sony camera, and this picture is a frame from video.
It is hard to see the ball.
17 mm, ball , color white, light in weight
Leveled wheel data real 358 spins.
Notice, how pick point around 10 on leveled wheel is actually closer to rotor hits then on first graph. It may be because the ball on first graph is jumping down the hill.
Forester, can you put a photo with the ball of 20 and 17 in pockets?
for example 17mm in pocket 10 and 20 mm in poket 5.
Is only to see if the difference is easy to find to the human eye.
i see also that the 17 is telfon and the 20 is ivory
u know of cource that couse they are from deferent matterials is a big factor that they jump diferently
Manuelon, do you see, the balls are exact equal as our casino. And its 4 different sides. So now you know why we lost when whe lost, and why we win when we win xD. We have 2 big balls (yellow and white) and 2 small balls (yellow and white). Good to know.
Please contact with me as fast as you can Manu
Yes Seiko, last time we lost was for this reason ;D. We knew that the kind of ball can bounce/jump different, but we didnt notice it. Is a very usual problem. See you at msn my friend
Can we see the raw data of all 1k spins. I just want to paste it into my own spreadsheet to view.
It holds the water only in theory. Imagine setting the system that way and staying in casino 12 hours to predict 20 spins. Once the player is at the table he is there to play, perhaps he can skip some spins but not sit at the table and wait for his perfect rotor speed. The border in between what will create pick point one or two is never sharp so if the speed is suitable you play or leave.
If you look point A and B on the picture, B is too small since the taken spins are not normal, I deliberately spin al spins so much faster to create big difference to better see what’s happening. But in reality if you play, the point B is only showing how with rotor speed increased the ball jumps a bit more.
The FF adjusts for that change because it’s common but you can easily set it to increase more, simply by adding some extra time after last rotation clocked. Adjusting from point A to point C, by computer would be a suicide. No matter at which rotor speed you set the border you simply will not be able to know if the computer predicting properly. Without knowing what to expect with a ball drop the player would be blind and analyzing it in combination with ball scatter is to slow. I wouldn’t like to play 100 spins too find out something is wrong.
If to remaining time after last ball click you add on sec the deviation from 5.5 sec rotor to 3 sec rotor would be additional
I may have missed something but it seems it may be beneficial to help exploit the advantage
of scatter point more accurately from any graphs made like yours which have taken rotor speed
in to account for ball scatter of a wheel without needing to focus to hard. Also this extra bit of
information maybe helpful to show if something in the game changes during play, eg ball change
or pressure change etc if the spins played should have a more uniform pattern due to parameters
Well if they replace the ball you have to set it again, each ball may have deceleration curve different.
If it isn’t much different for the FFVB2 it wouldn’t be much different except the offset might change.
I don’t believe much in air pressure change. A friend of mine did a big research and nothing changed.
Same as red can come 15 times in a row it can happened to point A or B.
Imagine how the graph would look at 3.5-4 sec rotor. A,B,C would be as added creating an average wider area.
As I took here
from MH video. Understanding that and prediction where the ball drop is never 1 pocket accurate, inaccuracy combined with it only creates one area where the advantage is, you will have it or not.
-15 … x
-10 … S
-9 … S
-6 … x
-4 … x
-3 … Sx
-2 … xxxx
-1 … x
0 … xxx
1 … x
2 … x
3 … x
5 … x
6 … xx
8 … S
9 … xx
10 … x
12 … x
13 … xS
16 … x
17 … xx
Maybe somebody have big database on scatering ball depending to wheel speed? So how long is distance from ball hiting to rotor till stop in diferent wheel speeds ?