V4 DVD with uber

For players testing the computers on the #4 DVD, that video is a perfect example showing:

• a good set of dominant diamonds, with bad scatter
• How variation of rotor speed affects ball bounce
• How gradual ball deceleration rate changes affect outcomes

For testing, I suggest use the basic auto target, so don't aim for specific diamond hits. Check the raw chart which shows the basic computer algorithm. Keep comparing it to the COM chart for target. With correct application you will find that the raw chart starts out with great accuracy, but after about 40 spins the accuracy turns terrible. But the accuracy is maintained on the COM chart with target. If you do it right, after the 110 or so spins, you will see the difference between almost no accuracy with basic settings, and about 80% wins covering 18 numbers.

Uber Dynamic Tuning & General Update

Many variables determine how the ball's bounce will vary betweren different rotor spins. On a set of spin dvds sent to me by a player, the ball travelled 19 pockets extra when the rotor was just 1 second faster. So if the rotor is just slightly faster, the ball will biounce completely differently. On such a wheel, it would be just about impossible to achieve any accuracy unless you used dynamic tuning, which adjusts for the different ball bounce on different rotor speeds. The lite and basic computers don't do this, same as devices from other developers. Even software used by casinos to assess wheel vunerabilities don't have this feature -= they all assume the ball will bounce the same regardless of rotor speed which is obvious nonsense. It is a feature only user by the uber and hybrid versions.

I also did further testing on the news uber modification, but this time there wasn't a significant improvement (about the same results as target). This is because of a ball and rotor combination anomaly that sometimes occurs. You cant always predict when or it it will occur though without collecting 60+ spins per direction. I'll continue work on it but again it will be months before this is fully implemented.

As for the uber and the new programmer, he's still learning the code but told me he expects to be finish about mid next week. Then he can start coding.

Calls tomorrow

I'll be taking calls tomorrow but please only call if the matter cannot be resolved via the support forum or email.

Uber and Hybrid development

I've done more research into the possible new algorithm/setting. In the last test, the results were:

Basic algorithm: near no accuracy
Target algorithm (no dynamic tuning): +122 units
New algorithm: +220 units

This was a similarly very difficult wheel. So again it showed a big improvement in the results, but it was more the data the confirmed the improvement.

Testing is one thing, but implementation to make it a practical setting is going to be very difficult. It is a lot more complicated than I expected especially when incorporating the dynamic tuning algorithms (different ball bounce on different rotor speeds).

To do it all in the optimal way will need a 3 dimensional chart using 3 dimensional areas to calculate predictions. A normal pc can do it, but I'm not yet sure if the mobile phones are capable of it. And no off-the-shelf microprocessor can do anything close to it. The phones we use have the storage, but may not have the RAM (memory). So perhaps only the hybrid will be able to do it, unless we can either do further firmware modifications or code the algorithm to use minimal resources on the phone.

Nevertheless, first for the uber we'll get the new programmer working on the firmware compatability issue so I can resume shipping. Within 2-3 weeks I will have designed the algorithm, then we can start coding it. Coding will take roughly a month so it will not be ready for perhaps 2-3 months. Only at this time I will know if it is viable for the uber, or only the hybrid.

The current uber version will do part of it when we re-enable the required menu items, but it is only a limited version of what will be possible. So users can test the improvements, but it is quite fiddly to do compared to what it will be.

Software bug

The online software programmers modified something and introduced a bug I only just found. It seems to affect the simulation feature. It doesn't seem to affect betting charts though. You can compare the betting charts with the simulation to see the difference. I've notified them and they'll correct it asap.

Update on schedule

Im about 2 days behind on emails but will catch up tomorrow. Please done resend emails.

Uber and Hybrid V3

I've completed testing of a new setting for the Uber and Hybrid V3. It has been run on my pc so the timings wont be as accurate as the phones, but the difference isn't overly significant. The purpose of the setting is to better deal with very difficult wheels, in particularly where the scatter is quite bad. For the testing I used a dvd where the velstone mk7 gives virtually random results when using typical roulette computer algorithms (X ball revs until drop, like VB). Of course you aim to avoid such wheels, but it isn't always possible if you are unable to travel.

The results over the same 100 spins were:

1. Basic settings only (no target etc): break even (no significant profit)
2. Target with standard tuning (not dynamic): +24 units
3. New algorithm (not dynamic tuning): +145 units

#1 was pretty much a flat-line chart with no discernable peaks. #2 had marginally clearer data. #3 was much clearer. There was an enormous difference. Keep in mind this is one of the kind of wheels you would normally not bother with because the accuracy is normally not worth your time compared to other wheels.

While this difference may not be as dramatic with different spins or a different wheel calibration, the results are certainly promising. You may know even rotation of the wheel of 20 degrees can be the difference between a wheel being very easy or very difficult to beat.

The current uber version already has part of this implemented, but the option to use it is removed from the menu system because it is too impractical to use. To make it practical requires about 8mb storage on the phone (which wont be a problem), and a bit more coding. Once the new programmer is more familiar with the software we'll get it all done, then I can test more.

How it works is basically better dynamic modelling of the relationship between the variables, in particularly detected ball speed, and the variations in ball deceleration.

Regarding uber progress, for now the new programmer is still learning what the code all does. The code is a lot more complex than when I last changed programmers so its taking longer than anticipated.