Well a lot of wheels are beatable if you know under what conidtions to play or what conditions to adjust bets. However, people fail to understand what cause the outcome of roulette and how change in conditions can affect the numbers.
I can tell you that the ballspeed on the moment it leaves the rim is always the same. The startspeed or the acceleration at start is always different and depents on the dealer.
It’s weird to hear from a mod / support personnel, suggestions that it can’t be done by a computer, but a person can do it and it’s better than a program… I had this talk with 1 gentleman 4 years ago.
Since i was there years ago, all i can tell you, to make a roulette wheel simulator that reflects what’s happening on the wheel, if you never did it, you’re not a programmer, you’re not good at math and problem solving, you will have a ton of never ending problems, and they show up when you try to stitch everything together, a full predictor that’s universal, that can collect data when you can see just a part of the wheel, while most of the diamonds as well other things happening are hidden from that perspective, with a wide range of applications for different conditions, fast/slow rotor, fast ball, changing deceleration curve and drop points, with ball scatter isolation for different conditions as well, isn’t a simple app at all).
If you want to make a simulator, you first need a good data collection approach, to collect the data needed, then you need to process it, and generate additional variables that you can’t collect at that moment by what you got, the app has to be applicable in real environment, and there you can’t see everything at once.
Then you have to verify, that the simulator is replicating what’s happening on the wheel, from ball/wheel speeds, to positions at specific time. Sometimes the rotor position is traced correctly, sometimes suddenly it isn’t. You will have to track partial rotor clocking, 1/4 rotor clocking for both directions, and test for various starting numbers, with constant and changing deceleration, depending on the rotor, and if something is wrong, there’s a ton of time wasted to debug this.
Deceleration curve generator from multiple samples, adjusting for air pressure and deceleration changes over time, as well drop point speed range changes, is another challenge.
For various methods, you will need to create different settings and find optimal values working together. I assume you develop for desktops, but you have to make it applicable, so if you ever make a computer / app for Android, you will be able to replicate it with two buttons (the system can’t be too complicated with data inputs).
I am in the process of refurbishing my program, cause regardless of what you said in your newer posts, it’s not a “2’nd grader thing”, to make a fully working app, with everything that you need, with custom system settings, data corrections, adjustments, with plugin-ready features that are stable and extensible while don’t create new problems(like automated timings from image recognition), and the never ending dilemma if you’re using the most accurate method for everything, realistically you will write your systems multiple times, and have to test each of it, especially if you have some problems with perfectionism.
If you’re not a good programmer, you will start having trouble maintaining that structure, and will lose track on what’s going on there, especially if you take longer breaks from development.
It’s been 5 months, when I was starting with this weird hobby 7 years ago, there were no AI coders or math emergencies, that could help you in any way, so i assume you got what you wanted already. Perhaps you could record some roulette spins and demonstrate how it works and predicts, and probably i can show you something as well.
Actually working on it. Check my last post for details. After recording around 100 spins on a wheel, my physics-based simulation program can consistently narrow the outcome down to a sector of about 12 numbers.
I also shared the formulas I used, which are derived from spatial motion equations
12 neighbors or 12 overall numbers?
12 neighboors
Have you implemented rotor & ball position tests? Do you have any reference to check if the ball deceleration rates are correct? Before you do any predictions that part must be done, and there should be some reference numbers given at the last ball rev to check if everything is correct.
im sure most of us can play 7 neighbors without any tools
Not neighboors sorry sector of 12 numbers