Myrulet Visual Prediction System VB2

MyRulet visual prediction -VB2
1

I finally decided to write about the way how I play my roulette visual prediction system.

What you going to read here definitely isn’t as anything else that you could find on the net for free or that you could purchase somewhere else. VB2 roulette system has a very unique approach. Smart system design provides very accurate prediction but in same time if the system is compared to some other visual ballistic systems is very simple to use. If this system is nicely packed to be sold it would have fair price of few thousand dollars.

Main reason why I delayed writing about this system is that there are people around who reading a lot what I write, especially about roulette computers, but they misuse it and without much understanding often trying to improve their scamming product which simply can’t be improved because of wrong design. It will not surprise me if one day they start reselling this system as their own. But on the end I want this system to be used, and I do not believe it will affect me in any way.

Myrulet site is not profit oriented site, therefore giving away this system doesn’t cost us anything. Our main objective is to learn and to progress. I do not believe that in short time every single person will use it, which could affect my play, however I do believe that this system will help many and that was my objective from the start, when myrulet.com was created. Some of my friends already use it and achieving great results.

The system is based on roulette physic, perfectly balanced, based on roulette ball and rotor parameters. The systems design has idea from my E2 system which is really the only known way of visually predicting roulette leveled wheel with some success. Predictions on tilted wheel with VB2 system are much simpler and for some who are familiar with E2 there is no multiplication factor. Any single person who spend some time to understand system and who applies it on the wheel with suitable condition should have reasonable success.

Most of the other visual prediction systems are based on waiting to identify particular ball revolution. (Check UWE visual prediction http://rouletteplace.com/index.php/topic,531.0.html)
My argument about such systems is that one pocket in ball observation could cause huge error in prediction while with system as VB2 it would be only one pocket of error.
VB2 system doesn’t even require a lot of wheel watching, and unique design allows player to have prediction at different ball rotations. Time of prediction can be early during the spin allowing a lot of time to player to place bets.

I will explain systems strong sides but and weaknesses as well. Same as it is important to know what the system can do, it is important to know and potential problems that we can face during various real play conditions.

To find it all, I have spent almost 3 years, studying and testing this system in real casinos environment. I use it a lot, of course it is not accurate as my roulette computer but definitely it’s legal and it is always with me.

The VB2 roulette system can be used as it is, or we can use electronics timer to give us reference time and slightly increase accuracy of prediction.

For people who do have my roulette computer FFZ or FFA this visual prediction may be very useful. FFA roulette computer can provide to player needed information about physical parameters of the wheel they play. After knowing parameters it’s easier to define how to play VB2 system. FFZ has built in timer so it can be used as a help with VB2 system.
Of course the system can be played without having any of my roulette computers.

Here you can download systems document. It may be not in the best format and the best explained. For someone with previous experience with visual prediction I believe it wouldn’t be hard to understand everything needed from the document.

I provide system for free, but I will not and support it for free.
I know that many people will send me emails with questions and ask for help to understand system better.
I can not do it for free, so please do not send me emails with questions regarding VB2 system because I will not answer it.

There will be a FORUM section with automatic subscription where the system will be available for discussion.
It will cost you symbolic amount. I think this is a fair go, where one particular question will be answered once but all users can read it and learn form it. This fee will eliminate time wasters and it will add to our community only people dedicated to learn.
I will restrict any discussion about specific system questions on any other place then dedicated for VB2.

I also welcome VB experts who do already have access to make their comments about the system.

Of course FF users and members who already have access to development section will have access to this forum.

What you need to know about VB2 roulette system.

First of all it is a great system, if it is other way I wouldn’t use it and use something else.

It is designed to be effective only on wheels with dominant ball drop zone (tilted wheel).

It requires reasonably steady rotor to achieve best results. Few pockets per second change in rotor speed are ok.

The system is not suitable for fast rotors. I do not believe any system is.

Playing VB2 visual roulette system is fun and easy to apply, so enjoy it.

Password to read the file is myrulet.com

Updated version http://myrulet.com/visual-prediction/detail.html
you may need to register

myruletV2.doc (46.1 KB)

VB2a.pdf (129 KB)

2

I think you need to explain the tecknick a little better.

After 1.2 sec it will make more then 1 rotation, at the moment when time elapses read the number. It is your prediction number.

Aren`t you just identifying a certain ball revoloution, using the ball speed, like in ordinary VB ?

3

There are not neccesary to identifying a certain ball revoloution. That is advantage of this way. No matter at which revolution till end you do prediction - prediction number is the same. You have maybe 5 revolutions where prediction number is in range +/- 3 pockets.

4

I agree that the prediction number is located in certain spot intervals in the ball revoloutions before the usual prediction round, the problem is that they are hard to identify because they are too close. At the point where usual VB ¨rs identify the prediction number is the ball revoloution AFTER a steep/identifiable decelleration has taken place. I can`t see how you are going to seperate them earlyer.

If a spin is identical, like, 4.0 sec wheel speed and 15 ball revolutions, its easy to go in anywhere in the spin and locate how far we are in the spin and where the prediction number is located. But it should also be useable in 2 spins with for example 15 ball revs and 24 ball revs ( and same wheel speed).

5

Foresters metod is based on that - say 4.0 wheel speed and 15 ball revolutions - you entered when ball is about 1 sec per rev. say it is about 7 rev to end. You do prediction an get number. The main feature of that metod is that there are no diference - you do prediction one rotation earlier or later - you get the same number. That is because rotor movment compesate ball deceleration. When ball thrown to go 24 rev. and you entered when ball is about 1 sec per rev you are again about 7 rev to end , so you are in the same position like first time. The diference in prediction can make only change of rotor speed if it is big. Of course every time you must entered at the same point ( diamond )

6

Yes but if you do the prediction 1 ball revoloution earlyer or later, the ball speed is no longer 1 sec. So you need to define either 1.2 or 0.9 sec instead of 1.0.

Can we agree that when we do the prediction, we do it because we know for how long the ball will run ? And because we know that, we also know how many revoloutions it will run. Meaning we define a certain ball revoloution when we do the prediction.

Personally i can`t find the explanation of how you predict in a specific ball revoloution or to put it differently, how can you know that you predict in the 8th last instead of the 7th last round ? If you are mistaken, your prediction will be wrong all the way.

If you do it because the ball speed has reached 1.0 sec. then you basicly predict as all VB ¨rs do, by defining a certain ball speed = ball revoloution.

7
Can we agree that when we do the prediction, we do it because we know for how long the ball will run ? And because we know that, we also know how many revoloutions it will run. Meaning we define a certain ball revoloution when we do the prediction.

Yes we can, if you ask Obama, but no we can’to agree on that.

Bebedikus explaining it correctly but you 2 are not on same wave length.
Kelly I’ve told you that I do not have to have prediction at particular ball revolution.

When you apply 1.2 sec and let say want to target 6th rev.
You do not look that ball makes one rotation in that time, but you read number under the ball wherever the ball is. (I think you missed this part)

So let say the ball at that time 1.2s made exactly one revolution, and you read number zero at 12’o clock. That would be something what you would play.
But what happens if I started one sec. earlier.
Then the ball will make one revolution and 9 extra pockets.
If it was going in CW direction it will be at 3 o’ clock.
But because it is happening one sec. earlier and rotor which is moving 9 pockets per sec. will be in -9 pockets position so zero will be at 3 o clock. And we will have again predicted zero because and the ball is at 3 o’ clock. We do not care in which rotation we are or what is the ball position, we getting always same result as it is in our targeted ball revolution.
We can be in about 5 different rotations and still have good linearity that this law will apply. In usual I can be most of the time within single rotation, but if I am on rotation earlier or later it doesn’t matter. Even if system is not perfectly balanced I miss one or 2 pockets.
We can also care how much the ball makes, that depends when we want to have our prediction. We can say we will play if ball makes 1 - 1.75 rev so we know that we are always within 3 rotations.

When timer is used if we start noticing ball position we may find out that if we find ball that made 1,2 rev most likely it doesn’t hit DD, so we can ignore such spin.
I never mastered and applied this part in real play. It is too hard but possible.

I hope this explained it well. That is why it is so easy to apply it.
Once we define time, it is only matter of stating it and reading number under the ball when time elapses.

8
Yes but if you do the prediction 1 ball revoloution earlyer or later, the ball speed is no longer 1 sec. So you need to define either 1.2 or 0.9 sec instead of 1.0.

If the ball is 1 sec/r
In 1.2 sec it makes 44.5 pockets
If you enter one rotation earlier the ball will be ~830ms (in example we have 200ms difference around targeted ball speed of one sec. 1100 - 900 =200)

It makes 37/0.830=44.5 pockets/s which in 1.2 sec will make 53.4 55 pockets.
53-44=9 and that is by how much the rotor will be in different position.

[b]1.2 sec is only example, for wheel as Bob Gordon’s.
In casino time is in usual 1.5 to 2 sec, for about 4 sec rotor.

For people who want to try this, it is important to not wait to late with prediction.
It depends on the wheel but when the ball slows down enough ball deceleration is dropping which can start giving inaccuracy. If we play and use 1.5 sec time, it is good to have prediction when the ball makes 1.5 -2.5 rotations. [/b]

9

Could you explain what you do ball revoloution for ball revoloution ? I mean, you don`t need the rotor to define the ball speed. Imagine you start your reading at the wrong revoloution at 12 o clock which should have been read at 3 o clock.

What triggers your readings ?

If the target is 1.2 sec. then i can`t read anything before i know that the ball has that speed and i need a full rev. to know that. Well, it can be done in 1/2 and 1/4 ball revs. but thats a bit advanced.

You can use the number ring/rotor as gauge to check wether you are in the right revoloution because if you read X number in a revoloution then you know that in the following revoloution X will meet the ball at a specific point and if it doesn`t you will know how to correct. If you are too early, the ball will be faster and will not meet the expected number at the expected reading diamond. In ordinary VB you can do the same thing as a control measure.

10

To do things even more clear I give example - what VB player do - he finds particular ball speed and then reads number under the ball/diamond intersection this is his prediction. What will be if he after finding that particular speed wait for 1.2 sec and read number below ball. Nothing, only prediction number will be shifted in some distance, but that distance always will be constant. For example -at particular ball speed number under ball/ diamond is 0. Say after 1.2 sec ball is over 11. If rotor speed always is constant prediction number always will be shifted by 14 ( in mine example ) So there are no diference which number VB player uses like prediction number 0 or 11. So suppose our VB player always uses number after 1.2 sec. But to get exactly number 11 he must very well determine ball speed. If he will be one rotation earlier or late he will get other number. In Foresters variant no mater he will be one rotation earlier or late he still get that number 11.

11

If the reading spot is not the same from one revolution to another, he needs to know which revoloution he is in when he starts reading.

If we say that he reads 7 revoloutions out, the correct number can only be at 1 single spot in this revoloution. 6 revoloutions out, it will be somewhere else and the same at 5 revoloutions out. If the player starts reading in the wrong revoloution at the wrong spot, he will be wrong all the way till the drop.

12

Kelly, say correct number is 7 rotations till drop an he is number 11 in mine previous post example. I started at 12 clock diamond when under ball/diamond is 0. After 1.2 sec ball is over 11 . If Istarted at 8th rotation ball is over 22 but it is faster., and he will go more way and after 1.2 sec he will be again over 11. If I start at 6th rotation til end he will be over 34 but he will be slover and make less way in 1.2 sec maybe not full rotation and again after that time we will see that number 11. So this way not necesary very exactly to determine ball speed to get corect prediction. We always get the same prediction like in corect rotation.

13

[i]Let’s say we started time when the ball was at 12 o’clock.

After 1.2 sec it will make more then 1 rotation, at the moment when time elapses read the number. It is your prediction number.

(by observing and noticing the distance that the ball made we also know how much accurate we were in starting point. In this particular case if the ball makes 1-2 rotations we will be ok with prediction.

Simply all you need to do is to apply defined time when the ball is at particular position and read the number when time elapses.

Lets say clock way spin our predicted number was 17 and the ball with most common jump stops at number 10, move your observation (starting) point for 10 pockets in ball direction. And your prediction number will be equal as winning number. So our offset from predicted to winning number will be zero. [/i]

This is all very well, but what triggers when i start reading ?

Its all very well that you can roll this particular spin up backwards, but what about the next spin ? When and where (and why there) do we start the reading ? All readings after the first reading is locked by the 1.2 sec. parameter, so the prediction is locked so to speak. (We asume a fixed wheel speed of 4.0 secs. in all spins)

14

It is to simple for him to understand.
So let me complicate it maybe it will help.

Our time in this case 1.2 sec is time that makes that ball (distance in pockets) slowing down per rotation same as rotor makes per that particular rotation.

Imagine the ball slowing down 6 pockets per second
If we have rotor of 9 pockets per sec.

We need to apply time of 1.5 sec.
Because in that time of 1.5s that ball will slow down 9 pockets.

If we start our VB at 10 sec to the end and after 1.5 sec. ball makes 1.5 rotations.
If we started that ball at 12 sec to the end after 1.5 sec. it will make 2 rotations. So 0.5 of rotation more. But and rotor will be 0.5rotations=18 pockets in different position. So it really doesn’t matter did we start it 2 sec earlier or just in time.
If we started 3 sec earlier the ball will make 2 rotations+ 9 pockets…etc.

Did you understand that we read number under the ball. It is the ball that adjusts for us if we are in wrong rotation to still read same number for prediction.

15
This is all very well, but what triggers when i start reading ?

Nothing- you only estimate to start it as much as possible in same rotation.

With another spin is same. Predicted numbers are always related to final outcome.

If in lets say fifth rotation your time of ball rotation is 1.2 sec

That same is valid for another spin.
If another spin we get prediction in 8th rotation it will be same number as if we have had it in fifth.

16

Yes but how do i get the correct rotor position for the reading when i can start when ever i feel for it roughly within the same ball revoloution ?

17

It is same as how FFZ knows.

Your starting number is not important that is what was confusing me when I was experimenting with this.
.
Of course if you start one rotation earlier number will be different (by rotor movement)
But last number will be the same.

You start at number 9 at 12 o clock.
After 1.2 s ball makes one rotation and is at 12 o’clock but now we have there zero, so zero is our predicted number

If we started one rotation earlier, we would start at number 5 (for which we do not care at all.) after 1.2 sec the ball will make 1 rotation and 9 pockets, it will be inline where was number 34 (3 o clock), but because we are one rotation earlier the wheel still did not move 9 pockets so we will have under the ball number zero.

18

So basicly you DO pinpoint a specific ball speed = ball rotation.

The one that takes exactly 1.2 sec. (or another specified interval)
And then you read.

Thats the same way as normal VB. If one played Scotts cross over, he would have to let the ball run from when the deviation happened until the ball passed the reading spot. Because for example the 2X cross over happens 3 times on the wheel in the same revoloution so one let the ball runs until it passes a fixed reading spot. The same with the accoustic method.

19

I guess you could apply the same safety measure to normal VB. You would first look for the revoloution that travelled 1 1/4 revoloution to be prepared for the one that travelled exactly 1 revoloution. You would then need to be focused on the number ring/wheel as well as the ball.

As i play today and as also the accoustic system is played, you focus on the rotor for 1 - 2 sec. to get the rotor speed. You then don`t look for a few revoloutions until you hear the change in sound, you then look at the reading spot for that particular rotor speed and read the number as the ball passes and then make your bet. If im using a thumper for the ball speed, i must look at the wheel a little bit before because i need a few revoloutions just before the one im looking for.

20
So basicly you DO pinpoint a specific ball speed = ball rotation.

NO, I do not need particular rotation, my prediction can be 10 sec to the end or 14 sec to the end of spin or anything in between or even more then that.

Let’s say at the end of my 1.2 sec the ball with speed (A) is at 12 o’lock and remaining time until it drops is 10 sec and predicted number is zero.

If I do 100% same spin but prediction happens 14 sec until ball drops.
We have 4 sec difference and the rotor moves 4s/revolution.
So we will again have rotor number zero at 12 o, clock,
If our time is adjusted properly (1.2 s)
The ball (B) also needs to be at 12 o’clock, above number zero.

The difference in ball speed in between this 2 points A and B is that the ball B in same time of 1.2s makes one more revolution if compared to ball A.

If Ball with speed A in 1.2 sec makes 1.5 revolutions, the ball with speed B will make 2.5 revolutions. Or if ball with speed A in 1.2 sec makes 1 revolutions, the ball with speed B will make 2 revolutions.

We do not care how much ball makes, important is that time is adjusted that if we have prediction 4 sec earlier that ball (in1.2s) makes one rotation extra to cover for how much rotor moves in 4 sec, and in this example it was one rotation.

Ball deceleration in this example in observed time of 1.2s is 37(pockets/s)/4 sec = 9.2 pockets. Which means that ball at point A or B decelerates 9.2 /1.2 =7.5 pockets in second. Which also means that if rotor is for example 7.5 p/s we would need time for ball observation of 1 sec or if rotor is 15 p/s the time needs to be 2 sec.

Rotor speed change.
If we observe rotor also in 1.2 sec.
9 p/s rotor we will see as movement of 10.8 pockets ~11.
And if next spin the rotor is 7.5p/s we will see it in 1.2 s as 9 pockets movement.
So we will spot 2 pockets difference. If our prediction is about 8 sec to the end we can move our starting point ACW by 12 pockets. In this case if we are about 4 rotations earlier in prediction (~3sec.) we will get 6 pockets of error.

Alternatively we can deduct from our time of 1.2 sec about 200 ms.
That is why I start using counting instead of singing tune (o bal di o bla da)
So if instead of 1.2 sec I apply 1 sec when time elapses prediction will be about 10 pockets shorter (regardless in which rotation I predict), which will match final result.

Difference in ball speed for this example when prediction is 3 sec earlier is 27 pockets. Deducting time from 1.2 to 1 sec is 200ms it is 1/6 of 1.2 s.
27 X 1/6 = 4.5 so we will still have error of 1.5 pockets (6-4.5).

If we are in targeted ball revolution of 1 s/r
The ball travels 37p/s, in 1.2 s. it makes 44.5 pockets,
If we apply time 200ms shorter it makes 37 pockets. That’s 7.5 pockets adjustment and we need 12 pockets. Perfect would be if we used time of 0.87~0.9 sec then and 1.5 pockets error will be gone.

This rotor change was from 4 sec per rotation to 5 sec per rotation.