Hello Moby,
Can you use this system straight away when you find a biased wheel or do you have to video spins first to get acc?
Of course you can do it without looking video spins.
With calculation and knowing ACC is explained only a theory why the system will work.
VB2 is the easiest system to apply.
What is ACC?
VB2 firstly was published for users of FFA roulette computer.
ACC is what we call ball deceleration, FFA can measure it and it can say ACC value to the player.
For example if we targeting ball speed of 1000ms and next rotation is 1200 ms then ACC would be 200 (1200-1000).
Some wheel/ball combination may have it 140 some 200 some 300 or it can be anything in between. The FFA tells us ACC per rotation not per second, so good pracitse is to set the system to have prediction when the ball is about one sec then what FFA tells us matches ACC value per second.
On a single spin the ball deceleration per rotation increases but per second it is reasonably constant until the ball slows down to 1.2 sec or slower.
VB2 takes advantage of linear part, and we should not use it when the ball is slower then 1.2 s.
Example
Lets look if we use only 1000ms. time and if ACC is 200.
If the ball is 1000ms
We apply 1000ms time when the ball is over DD
After 1000 ms the ball is again at DD and under the ball is number zero.
We read it and that is our reference number (prediction number without offset)
Of course we can not always start in spin when the ball is 1000ms
So what will happen if we started one rotation later?
From previous we know that when we start now we have zero under dominant diamond (DD)
So we are going to apply again 1000ms time and read number under the ball when time elapses.
But now the ball is taking 1200 ms per rotation. (before it was 1000)
So the ball is a bit slower.
In 1000 ms this ball will cross
1000/1200=x/37
X=(1000/1200)x37=0.83x37=30.8 pockets
We can say 31 pocket
Also 1000/1200 is 0.83 that is percentage of rotation that the ball travels
So the ball will stay short by 37 -31 =6 pockets from making full rotation.
If in our example the rotor was traveling 6 pockets per sec. since the rotor is traveling in opposite direction then ball in our reference time of 1000 ms zero will move by 6 pockets and that is exactly how much the ball stayed shorter from making full rotation.
So in this particular case as you can see there is no difference if we started prediction when the ball is 1000 ms or 1200 ms, we read same reference number under the ball (zero).
But what if rotor speed is 12 pockets per sec.
It is logical we would need double our reference time, so it would be 2 sec.
2 sec reference time would make ball slow down 12 pockets so it would match rotor movement.
I assume your main concern is how to find right time to use without much complications.
And that is simple, first you forget about all formulas, in reality you do not need it. It is only an explanation why the system works.
If you have FFA and played that wheel few times at accuracy setting 2 (1000ms ball) you would have idea how the ball decelerates on that wheel. But that also is not needed.
So let’s go back to first example.
6 pockets per sec rotor ACC200 and 1000 ms our reference time.
But what if by mistake we used 2000ms for reference time.
So let’s say after applying 2 sec of reference time the ball is above number zero and it made 3 rotations.
Now we apply again 2 sec. reference time we know that the ball is slowing down 6 pockets per second so with 2 sec reference time it will travel 12 pockets less.
But from first starting point it already slowed down 12 pockets so in total the ball slowed down 24 pockets.
Since new starting point is 2 sec away from previous one the ball in our reference time will make 24 pockets less.
For time of 2 sec rotor moves only 12 pockets.
Once our prediction was zero and next time it will be around number 14 (ball clock way direction CW)
To make this shorter and simple.
All what we need to do to found our reference time is to make few experiments.
Lets say we start with 1.5 sec.
We apply it somewhere during the spin and read our reference number.
(lets say we applied it 15 sec before then ball drops)
Then we wait few sec and apply it again in same spin.
Lets say now the ball is 11 sec before then it drops. (4 sec difference at start)
We read number again.
If 2 numbers are same or close in distance our time is ok. It means that no matter where in spin from 15 to 11 sec we start we will have reasonable predictions.
If second number we read is in front of first number we know that our time is to long (as in previous example)
If first number is 26 and after 4 sec we read number 4 (CW spin), number 4 is 5 pockets distanced after number 26.
We know that our reference time is to short since the ball did not slow down enough to predict again number 26 but passed it.
In such case we would increase reference time.
If same spin repeats and we increased time from 1.5 sec to 2 sec.
Of course first prediction will not be any more 26 but something like 8 (0.5 s extra bal traveling time) but now most likely our second prediction will be 8 as well.
Important is to get consistency, is it 26 or 8 it doesn’t matter, it is our reference number and we observe where from that number the ball realty stops.
If for example the reference number was 8 and the ball with most common jump stops 9 pockets from there, (31)
We can simply move our starting point by 9 pockets in ball direction, so if same spin repeats instead of number 8 we would read number 31.
Reference time for VB2 depends a lot on rotor speed.
So once it is adjusted for particular speed it is not good to play if rotor speed changes a lot. We can allow rotor to change more and make adjustment just for rotor change if we have greater feeling to start in reasonably same time during the spin. Such feeling also allows us to have and reference time more out of perfection.
Somewhere in this thread about VB2 we used one spin and reference time of 2 sec,
Good linearity showed for 10 sec. it means somewhere from 18 -8 sec before then ball drops we could have accurate predictions.
In reality rotor changes a bit, time is not perfect but player with some practice do not need 10 sec gap to estimate ball speed. Reducing it to ~3 sec it helps a lot.
If player just tries to estimate right ball rotation with accuracy of 3 sec. and if the rotor is 10 p/s it means he will deviate 30 pockets in predictions. With VB2 it may be only few pockets, and prediction will never be in wrong bal rotations since any rotations is good and the ball deceleration compensates for misjudgment of right ball rotation.
In usual I use same reference time that I use for ball to observe and rotor changes.
VB2 locks reference number to be same as we always predict in same ball rotation, but for a bit faster rotor we need to add more pockets to prediction.
If my reference time is 2 sec and if in that time the rotor makes 2 pockets more then in previous spin, I know that rotor is going about 1 pocket per sec faster.
If my targeted prediction is 10 sec before then ball drops I know that I need to add extra 10 pockets because of faster rotor.
I hope this helps.