I'm really liking this visual ballistic

[Steve]

If the rotor speed varies significantly, this will kill basic visual ballistics.

The simplest solution is to segregate data based on rotor speed. ie create a chart for start and end numbers, based on rotor speed ranges. What speed ranges? The earlier you get predictions, the tighter the requirements for rotor speed ranges. You could still break it up into 2000-3000ms, 3000-4000ms etc but then you will need more spins than usual, and it is not suitable for all conditions.

Otherwise you can create a simplistic chart that tells you something like:

1. When initial rotor speed is 2000ms, adjust prediction by +5 pockets
2. When initial rotor speed is 3000ms, adjust prediction by +15 pockets etc..

This may be more practical for you, but you are best to memorize the adjustment chart.

Now you are starting to get into the realms of roulette computer use. A very basic roulette computer will tell you when the ball passes the threshold speed, but it will not consider rotor speeds. This is like my basic roulette computer, which I give for free to my players. Next up is the lite computer which does account for rotor speeds, so it is like a super-skilled vb player, but still it doesnt do anywhere near what is possible to maximize accuracy.

I suggest in your case, give the rotor speed adjustment charts a try. But you need to create them carefully so they properly reflect your rotor's deceleration, and the ball travel time from the ball's reference speed. So if you get a prediction 10 seconds before the ball falls, initial rotor speed is A, and rotor deceleration is B, then you find distance travelled. If 10s is constant, then the adjustments are easy to find.

Also if you are taking your rotor speed estimates right at the start of the spin, then the ball travels an inordinate distance, then you will lose accuracy because the end rotor speed will be different in other spins.

I say it many times, I dont like VB because it is a struggle to do things that a computer does effortlessly.

[MrJ]

"can't get bets on fast enough" >> This is not a knock against AP, it does not matter if it is method play........ It is why I will NOT play ANY type of roulette regarding betting MANY numbers.

Ken

[Steve]

Advantage play is not for all conditions. And besides I dont believe you can beat roulette in ALL conditions. VB is particularly limiting, but bias wheel play is even worse. There are better methods than both of these, but they too have their own set of limitations.

[warrior]

If the rotor speed varies significantly, this will kill basic visual ballistics.

The simplest solution is to segregate data based on rotor speed. ie create a chart for start and end numbers, based on rotor speed ranges. What speed ranges? The earlier you get predictions, the tighter the requirements for rotor speed ranges. You could still break it up into 2000-3000ms, 3000-4000ms etc but then you will need more spins than usual, and it is not suitable for all conditions.

Otherwise you can create a simplistic chart that tells you something like:

1. When initial rotor speed is 2000ms, adjust prediction by +5 pockets
2. When initial rotor speed is 3000ms, adjust prediction by +15 pockets etc..

This may be more practical for you, but you are best to memorize the adjustment chart.

Now you are starting to get into the realms of roulette computer use. A very basic roulette computer will tell you when the ball passes the threshold speed, but it will not consider rotor speeds. This is like my basic roulette computer, which I give for free to my players. Next up is the lite computer which does account for rotor speeds, so it is like a super-skilled vb player, but still it doesnt do anywhere near what is possible to maximize accuracy.

I suggest in your case, give the rotor speed adjustment charts a try. But you need to create them carefully so they properly reflect your rotor's deceleration, and the ball travel time from the ball's reference speed. So if you get a prediction 10 seconds before the ball falls, initial rotor speed is A, and rotor deceleration is B, then you find distance travelled. If 10s is constant, then the adjustments are easy to find.

Also if you are taking your rotor speed estimates right at the start of the spin, then the ball travels an inordinate distance, then you will lose accuracy because the end rotor speed will be different in other spins.

I say it many times, I dont like VB because it is a struggle to do things that a computer does effortlessly.

I will start with that thankyou.

[warrior]

Today I was clocking the rotor at 3000 ms was better results but I think 15 numbers are ok I would allow for scatter it work ok.

[warrior]

90% of ball drop was at the 12 o clock and 3 . 72 spins  not a whole lot but better then nothing.changed casinos they spin the wheel with in 60 seconds I like that. They get into hypnosis state or what ever.

[warrior]

If I were to bet today the number I saw and 2 neighbores on each side out of 72 spins i got 8 hit I don't think that is very good.now if I  bet 15 Numbers I would get 30 hits still not good i don't think.

[Steve]

When evaluating a wheel, first give it a brief look ensuring the ball is at least behaving reasonably predictably. Also the ball having a sudden point of deceleration is a sign of a worn ball track, so favour such wheels.

Then comes the next and very important step of scatter analysis. If you get bad scatter, forget it for VB. The ideal situation is a broad 18 pocket peak that is harder to miss, although yuo dont necessarily need to bet all of it.

If scatter is ok, the rest should be ok provided you get bets in on time. Again if scatter is bad, forget it. Scatter tells you a lot about what is possible with basic methods.

If scatter is good, and you have enough data to know this for sure, and results of vb are bad, then something is wrong with the vb method itself.

If you break down the components, then you will know WHICH part needs work. If you blindly look at results without proper analysis, then you wont know what is possible, and how to fix any problems.

It isnt at all difficult, but its like baking a cake where if you do one simple thing wrong, you can end up with a disaster.

[warrior]

Ok that makes sense .this was my session today
 
Rotor speed around 3 seconds per rev 90% of the session.
 
Prediction #.    Outcome #
    0.                     6
    4.                     26
    13.                   14
    32.                   25
    18.                   20
    3.                     35
   36.                    35
   15.                    34
   3.                      15
   1.                     35
   11.                   15
   5                      32
   0.                     26
   7.                     30
   17.                   30
   14.                   18
   30.                    24
   8.                      0
  6.                      18
  36.                     29
22.                     32
26.                     3
  2.                      3
  4.                      36
  6.                      0
  4.                      7
7.                       32
36.                      14
32.                     16
0.                      36
22.                     14
31.                      32
0.                        0
28.                     35
20.                     5
7.                    30
8.                     27
0.                      0
22.                    0
2.                     19
8.                      4
4.                      18
6.                      23
2.                     9
33.                  14
29.                  9
0.                   10
22.                 13
0.                  24
25.                 15
13.                 10
20.                 33
14.                 15
19.                  18
2.                   9
10.                 24
5.                   3
13.                 14
9.                  19
29.                 16
1.                   35
11.                 22
13.                 35
4.                   31
8.                   6
14.                 9
10.                36
27.                8
20.                8
5.                 14
27.                14
22.                0
6.                 8
25.              16
Rotor speed 3 seconds per rev a few times it when to 2 and once to 5 and 4 .

[Steve]

You should use a format as below as its more universal and can be used in software like link:://roulettephysics.com/jaa/index.php/jump

0,6
4,26
13,14
32,25
18,20
3,35
36,35
15,34
3,15
1,35
11,15
5,32
0,26
7,30
17,30
14,18
30,24
8,0
6,18
36,29
22,32
26,3
2,3
4,36
6,0
4,7
7,32
36,14
32,16
0,36
22,14
31,32
0,0
28,35
20,5
7,30
8,27
0,0
22,0
2,19
8,4
4,18
6,23
2,9
33,14
29,9
0,10
22,13
0,24
25,15
13,10
20,33
14,15
19,18
2,9
10,24
5,3
13,14
9,19
29,16
1,35
11,22
13,35
4,31
8,6
14,9
10,36
27,8
20,8
5,14
27,14
22,0
6,8
25,16

And looking at the data, it is not conclusive. Realistically you would need more data, or to refine the prediction method. If the prediction method is refined, then of course peaks will be clearer.

But again you should always focus solidly on scatter. If that is bad, forget vb.

[warrior]

I'm still practising the other day I was clocking the wheel this old man in His 70 was next to me and I predict The number 30 pops right in ,wish I can do that every spin he looks at me thinks lucky  guess I just nod next number 8 23 pops up looks at me again .The next day he there again I sit clock the wheel a few times he's chit chatting  with me  anyways I start verbalizeing the next numbers all coming within 5 6 pockets  and then the dealer changes  I say to him number 8 pops right in there love the  feeling when you get a direct hit he looks at me with a strange look and says quietly that's a coincidence .I smile and nod. The conditions have to right on for this.

[Steve]

When the conditions are right, beating roulette is quite easy. When the conditions are wrong, you will struggle and go insane. It all starts with wheel selection. It is not at all difficult to find suitable conditions, but this depends on the method you are using.

[mogul397]

That's what I was going to ask.

How can you do that so fast?

[Steve]

Its easy to get early prediction with predictions after ball release. But whether or not it's accurate is a different matter. Same goes for roulette computers.

[denzie]

if u can look on what half of the wheel it falls.....then your rich.  u put your numbers first 5/6  8/9  10/11  13/14  16/17  23/24  27/30  31/34  33/36. if u have the gift of know on what part it falls u do nothing or press cancel bets. u just need a roulette without a dealer but not online also. so if u really can be accurate lets say 1 of 3-4 times minimum.....bingooooo