Yes that is correct.
You need to understand that on “tilted wheel” the ball is coming towards the dominant diamond with possibility of wider angle causing results to be built in main 3 groups, based on position where the diamond is hit.
Additional problem is one that long time ago I highlighted to you. Even if the ball makes same amount of revolutions to the end it will not be in same time therefore and rotor position may be different. (It needs to be compensated).
I may be rued but Ritz VB is not perfect to handle it neither your computer. Because it is based on basics of defining revolution and plain calculation ignoring fact that time of traveling for slightly different ball speeds will change. With one of my attempts with tilt prediction I did it perfectly; taking it in to account and also making where 2 most highly pick points would overlap. But I could get only 40-50% of spins predicted. It was frustrated to me (especially when happen that 3-5 in a row there is no prediction). So I took different approach to get more predictions, losing something in accuracy but not all. There are control pulses; spins marked with such pulses should never pass the dominant diamond. If does clocking point must be shifted. If that is done correctly much higher advantage is possible. Because the FF simply will know where the ball will hit. Sure there will be mistakes but it will do whatever is maximum to do. Even it is tilted wheel approach the FF in most cases will predict correctly and if the ball goes for next diamond. Tilt 2 doesn’t predict only in one rotation with same distance to the end it could be in one earlier or one later as well.
It uses error correction from IQE6 to avoid 30-40 ms errors which really could cause wrong prediction. But that is and main reason why system may not be properly set to get maximum advantage at firs spin. That is why is better to run few spins before set, so the system defines wheel parameters then it can defines time windows more accurately. Everything outside of time windows most likely will be bad hit such as very top diamond hit, or drop point on opposite side of defined most common drop point.
Leveled wheel prediction and scatter is different. Instead of 3 most likely scenarios with almost same probability for any, we may get one but wider. What can be done on tilted wheel with reasonable success on leveled wheel is imposable to do, even if timing is 100% accurate. That is why IQE6 doesn’t go for diamonds but for predicted rotor number. And the diamond is only an obstacle crossing the ball path on the way to reach expected number. The system doesn’t know where and which diamond will cross the ball path but it should be somewhere within deviation of 0-12 pockets +X from expected number. What I explained in previous post is that deviation. It isn’t something that the FF does and should fet credit for that. It it is something that happens on the wheel and the FF only uses it.
Oh, almost forgot. I just explained the best possible but you may be right.
If I add and loses where I did not do everything as is should be done, I may end up with something as that.
However if I separate only" tilt" wheel play I did have more then that. If I refer only to wheels where dominant drop point was very strong and constant (excluding cases where every second ball was spinner) definitely it could be 100%.