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.
