Greetings to all,
a few days ago i was sorting out what of the various public VB techniques could be well suited for my style and abilities.
after i lost 20$ with martingale (in which i never believed in first place, but hoped for a wining streak so long to actually make some few chips in order to play VB, but eventually failed with 6 or 7 bad hit on a 50% winning prob with the online ZERO house advantage at betvoyager), started immediately reading posts by kelly and his take on VB, plus his evergreen pictures of some German ballistic prediction book :).
I started drawing several triangles of ball, ball after 4th revolution and outcome (like the ones inside the pic with Su and Sg)
i tried to focus on patterns, but i couldn’t get a definite pattern there, and that was because of:
- bad scatter
- bad rotor speed
- bad wheel speed
- wrong diamond hit (and consequent bad scatter)
- and not least, human error
so i immediately dumped the whole practice, but it had taught me something ofcourse, taking some reference that will end up building some consistent result. Thanks Kelly for that.
In the search for something more functional, and by that i mean something that can produce quite constant data in order to be used to do some statistics, or even know if i am doing good or bad, i read Forester reply to a user which was starting VB and did his bets on a whole quarter of wheel based on the start position of the ball when the dealer spun it.
in that reply, forester was describing the whole VB work as it was full with errors.
He said that you can take into account and focus on ball speed, but then you’ll lose rotor speed variations, and you might mess it up
The opposite is true, and you’ll end up not knowing which revolution is good for the ball to be.
He suggested to remove one variable, the ball, and focusing on rotor… then he went on but that was the main thing, to loose focus on one variable…
that is what his VB2 system is all about, after reviewing the expression, he put rotor speed and ball deceleration inside the equation, and the number you get is related to that particular rotor revolution.
I have found my system, and in the last 72 spins test, by betting 5 numbers i got 1/4.2 hit rate, with 5 betting you need better than 1/6 so that’s a sign of goodness but still i didn’t do NOTHING of what i call ADVANCED, and which i will be describing and asking questions here below:
to both Kelly system and Forester one, wouldn’t be better to mark out the ball drop point instead of the outcome and then add the scatter accordingly? so you will sooner find if prediction is good without the error of the scatter, i think that thing is done brillantly by the FFA computer, by finding the drop zone, not the actual prediction, which my vary on scatter.
to Forester this time: your system basically states that ball and rotor are syncronized at some time when applying the time in the function (t). So, i thought of a way to predict which diamond will be hit on the final spin, and this could be accomplished by noting the position of the ball in the track (the closest diamond) when you make the prediction, and the final diamond hit.
if the wheel is tilted, we clearly have a larger section of the wheel in which if the ball is inside when we read our prediction we can be sure the ball will hit our DD. Then we can filter out bad spins, as spins that hit a different diamond. And this can be done with almost no eye stress during our normal prediction time.
to Forester again: i don’t find why your system couldn’t be applied if the wheel is not tilted… maybe for the reason i explained before? for example in a wheel which is not tilted the section of the wheel in which happens the prediction that leads to one of the diamonds is too small to estimate correctly? so any diamond could be hit thus prediction might be good but scatter will be random?
to Forester again: i found out that the vb2 is good for rotor speeds actually varying slightly, it has some sort of accuracy (if mentally timing the ball ofcourse) of ±0.15 seconds, so you have a good results with a large span of rotor speeds,… i thought that one might prepare himself before with like 3 variations of the formula and mentally memorize different timings in order to adapt if dealer change his rotor speeds. good point?
Dealer change: how do we disguise the fact that we are predicting during dealer change? what are the betting strategies in these situations?
if we are able to predict which diamond is hit for each spin, wouldn’t it be wise to accumulate scatter data JUST for that particular diamond?
Do you think that with time is convenient to reduce sector betting size or statistically a fixed number is better? if not, do you adjust it with rotor speed? and if rotor speed is faster than normal, do you move the bet with some sort of calculation or you just guess what more scatter will be by experience? because i do that alot, i feel i don’t have much time to place the bets if i do the calc…
but of course i only play online casino right now, i’ll try soon on a live casino, buddy told me betting time are more tolerant there…
Oh, if some of you find out in my post i am unveiling something, feel free to edit as you like
thank you so much for reading this long,
Semi Engineer V.