Hello Forster
You've written that on Cammegh Connoisseur your reference time is 2s.
What is your target ball speed on that wheel?
Do you know where I can find video spins on Cammegh?

Yes I use 2 sec.
If you are spending time with VB2 the best for you is just watch the wheel few spins.
Start 2 sec lets say when ball is about 15 sec before then it drops read number
Then instantly apply same time again, if the time is ok you should read same number.
It also means somewhere 15 -10 sec before then ball drops you have linearity with that time and no matter where you start vb2 within that time you will be ok.

If for example CW spin.
First number is zero and next reading it is 7 it means that during your time of 2 sec the ball slowed down to much so you should reduce time. Perhaps to ~1.5 s

In usual I have rotor about 4 sec per rotation.
Before then i apply VB2 time I apply same time and observe rotor.
rotor makes 18 pockets and I started VB2 time at 12 o’clock …read result

next spin rotor may make 20 pockets in my 2 sec time. It means 11 pockets per sec also 1 pocket per sec faster.

So I expect ball to drop about 12 pockets from previous spin.
Instead of starting VB2 time for ball at 12 o’clock I move it in ball direction by 12 pockets. (targeted to have prediction when the ball is about 12 sec before then it drops)
Still observe final results (also noticing ball drops to rotor ). If you get consistency in distance in between number you read and final numbers then move your basic starting point from 12 o’clock, by that difference and continue playing for real.

Last night I played Cammegh Connoisseur with small ball, it was very good.
I played only about one hour and won $1400 with $5 units, placing about $100 per spin.
Very strong tilt, but ball jumps are wider. I played this wheel few times and won.
However I am not very confidant in playing it.

I target that the ball hits rotor just after my prediction.
I win if it bounces back and if it makes long jump of about 30 pockets.
With this wheel is a bit tricky, if rotor speed increases then there is less long jumps and ball more of time jumps 12-15 pockets.

I do not know about targeted ball speed I just estimate to have prediction at 10-12 sec before then ball drops.
Nobody have spins for them.

hello
I start to work and study vb2
and this is how I play it:
casino :
dvd bob gordon video tilted wheal small ball (clockwise direction)

first I find referent ball time, in my case is 1.2sec(my referent time is ok when I apply it in same spin from same rerefent point couple times beforre it heapens knee point… it as result gives me zapp on same number) I use timer from ffz(referent time can be 1.4 sec as wheal, I dont now why but it can )

2.i apply vb2 for some time, my referent point is at 12 o clock(where is dd), then i compared my predicted number with place on rotor where ball hit, and find consistency that is in my case if i predict 0 ball hits 5 (180 degrees ). I play 10 spins to find consistency. after that I moved my observation point from 12o clock to 6 o clock(I moved it 180 degrees).

after all that. now I make ball scatter patern. when I make it in may case it was this:
0,+2,+7,+7,+7,+7,+8,+9,+10,+11,+12,+13,+14,+15,+18
-1,-6,-8,-10,-14,-18
I used +10 and when I apply vb2 and get prediction number I ad 10 pokets in ball direction.

4.then I play 9 chip around mu central number who was 10 pokets away from may prediction number(4 from each side).

I play 43 spins (is that a loot or its normal ???)
I won 15spins (36-9=27…2715=405) I won 405 chips
I loose 28 spins (289=252) I loose 252 chips

I won clear 405-252=153 chips

I dont now how to calculate advantage???
I calculated it like this:

43 spins * 9 chips per spin = 387 chips
I won clear 153 chips which is approxsimately 35-38% advantage
is this calculation ok???

please if some vb2 expert can answer me on this post…
is this may play real or I was just lucky… ???
thanks in front…
mr… forester if you can answer me I would be weary grateful
Is this what I do properly or not
I still learning vb2 I just find out for all this(forum,myrulet,and you) just two months ago…

1. first I find referent ball time, in my case is 1.2sec(my referent time is ok when I apply it in same spin from same rerefrence point couple times beforre it heapens knee point... it as result gives me zapp on same number) I use timer from ffz(referent time can be 1.4 sec as wheal, I dont now why but it can )

The time is not so critical 1.2 is good as 1.4
When you have more precised time you can be more rotations wrong or have bigger rotor speed changes. 1.2s is better.

"when I apply it in same spin from same rerefrence point couple times beforre it heapens knee point"

Same reference point, same spin but in different times!

" I used +10 and when I apply vb2 and get prediction number I ad 10 pokets in ball direction."

Instead you can just shift reference point by 10 pockets in ball direction.

I didn’t see you make any adjustments for rotor speed changes.
It is important!

I play 43 spins (is that a loot or its normal ?)
I won 15spins (36-9=27.....27*15=405) I won 405 chips
I loose 28 spins (28*9=252) I loose 252 chips

I won clear 405-252=153 chips

I do it this way
Won form them
15x36 =540
Gave to them 43x9=387
Profit 153
Advantage
153/540=28.3%
28.3-(-2.7)= 31% change from negative -2.7% casinos advantage

I did not make rotor speed adjustmens, because I dont now how to do it…
should I use my referent time for it

example: for 1.2 sec rotor make 10 pokets
next spin for 1.2 sec rotor make 11 pokets.
1 pokets diference for 1.2 sec
that means that if I apply referent time 10 sec before spin ends ball will hit rotor 10 pokets after my predicted number…???

or should I do counting for rotor speed individual??
do I make rotor speed adjustmens every spin.
I think I should…

You have to make rotor check, also avoid fast rotor because for faster rotor and reference time needs to increase.

If you look around in VB2 section you will find explanation how to do it.
But basically yes your explanation is ok.
Using ffz’s timer is better.
In usual in casino you will find out that you ref time needs to be 1.5-2 sec.
It makes it better for checking rotor .
I apply 1.8s and each difference in rotor speed I multiply by 6.

So you do same as you did but this time check rotor let’s say rotor makes 9 pockets apply time form one ref point. Read result compare to drop.
Next spin check rotor, rotor makes 10 pockets.
Shift your ref point by 0 pockets and apply the time.
Read result compare to drop.
Basically if you start rotor at one diamond and if speeds are reasonable it ends up around some other point as in this example 9 pockets distanced diamond.
You compare spins to that diamond.
Rotor come 1 pocket short you deduct 10 , 2 pockets extra you add 20
Perhaps base doesn’t have to be 10 exactly, if it is 9 or 8 it doesn’t matter much as long rotor doesn’t change speed much. If you add 20 instead of 18 it sis til close.
You will see how important it is to make rotor adjustments since rotor will always deviate few pockets.

In next version of FFZ to timer I will add that after zap of set time it repeats it.
In your case it would be;
1.2 sec zap then again after 1.2s zap
So we can have 2.4 sec to clock rotor which it better than 1.2s.
The difference would be multiplied by 5.

thank you weary much
you cleared me everything wot makes me problems to understand vb2.
I now understand how and why is it work. now just need a lot practicing first on dvd then in casino…
practicing is a key of success…

ım thinking about rotor adjustment for different rotor speeds in vb2 and ı have a question.ı wonder ıf one of you give any solution.

assume we apply ref time 2 sec.rotor speed is 9 p/s.we red same number.so ref time is ok.second spin we apply same ref time but now rotor speed is 10 p/s.according to written stuff about vb2 we have to add 10 pockets in ball direction.my question is what if we read same number in this second spin?(that means rotor is 1p/s faster in spite of this we read same number so ACC increased !!! and compensate the equation(T=1000/rotor speed*ACC)
because if we apply 2 sec ref time and in the first spin we read same number (while rotor is 9 p/s) in the second spin while rotor is 10 p/s we shouldnt read same numbers!!! because we apply 2 sec again and we read ref number twice lets say in 5 sec.so the number we red must be changed by 5 pockets.if we read same number do we have to think that in this spin ACC changed and compensate the equation?

ım thinking about rotor adjustment for different rotor speeds in vb2 and ı have a question.ı wonder ıf one of you give any solution.

assume we apply ref time 2 sec.rotor speed is 9 p/s.we red same number.so ref time is ok.second spin we apply same ref time but now rotor speed is 10 p/s.according to written stuff about vb2 we have to add 10 pockets in ball direction.my question is what if we read same number in this second spin?(that means rotor is 1p/s faster in spite of this we read same number so ACC increased !!! and compensate the equation(T=1000/rotor speed*ACC)
because if we apply 2 sec ref time and in the first spin we read same number (while rotor is 9 p/s) in the second spin while rotor is 10 p/s we shouldnt read same numbers!!! because we apply 2 sec again and we read ref number twice lets say in 5 sec.so the number we red must be changed by 5 pockets.if we read same number do we have to think that in this spin ACC changed and compensate the equation?

regards[/quote]l would sudjest you apply bigger time interval to identify rotor speed changes. Pokets per second is just for explanation purposes. In real play use angles. 37 pokets= 360. More or less 10 per poket change.

ACC increased !!! and compensate the equation(T=1000/rotor speed*ACC)

my question was about ACC that can change between spins and make hard to apply the true ref time

You know how to deshifrate ACC ?

If yes then you easy come to minde that formula which you write is to simplificated and really it must be other and ACC in that new formula not exsist.
Forester done somewhere better description of all that, not be lazy try to find.

And after simply think what must be T that we will see always the same number ? Here you can come to one very strange decission to which i come many years back…