Computer Support Meeting Results

Not one bug was found over a 6 hour period, so everything went well.

We tested on the Mk7 Huxley wheel with Velstone, and ivorine ball. Predictions were roughly 8-9 seconds before the ball fall although we weren't focusing on how early predictions were - it was more about the ball scatter (what happens after the ball falls from the ball track).

Results were as below:

PART 1: With very basic settings, ie no dynamic adjustments for ball deceleration changes, no scatter management, and no target: very poor accuracy. It was difficult to ascertain if there was any edge at all. The equivalent settings of the lite and basic computer were used. To determine this, we observed the raw chart.

PART 2: Basic "correct revolution" auto targeting with adjustments for ball deceleration rate changes: The computer correctly noted the ball position at the end of the spin almost always within 1-3 pockets accuracy. When it was incorrect, the computer perfectly automatically adjusted. While the computer did everything perfectly, the ball scatter was "all over the place". The accuracy was roughly about 60% wins betting 18 numbers. To determine this, we observed the COM chart. So there was an edge, but only slight.

PART 3: Auto target for targeting diamond hits with adjustments for ball deceleration rate changes, and varying ball bounce for different rotor speeds and minimization of ball scatter:  The computer correctly noted the ball position at the end of the spin almost always within 1-3 pockets. It did all the adjustments it needed perfectly. Even with the terrible scatter, the accuracy was approximately 90% wins covering 15 numbers which is roughly the same accuracy achieved in the last public demo. "Risk" was called on average about half of the spins.


NOTES ABOUT THE WHEEL:
Whenever the wheel is set up, you never know how the ball will fall until you actually test over 50 or so spins. Less than 1mm tilt makes a significant difference to not only where the ball falls, but also HOW it falls (including scatter, amount of floaters etc). This makes results different each time. Overall the ball scatter was abysmal, hence the poor performance of the basics settings. Observing the wheel with traditional methods would indicate the scatter was completely unmanageable.

The ball deceleration changes were considerable throughout the meeting. At one stage the ball was completing two fewer revolutions than normal from the point of prediction, and then soon changed back (from ball track grit). So that's about 5 revolutions when there would normally be 7 - so it's quite big difference.

The computer correctly noted the ball position at the end of the spin almost always within 1-3 pockets. When it was incorrect, the computer perfectly automatically adjusted

Overall the wheel rating was 9/10 which is probably the most difficult I've seen it. In such circumstances, it was not a surprise to see the basic algorithms perform poorly. Although it was great to see the advanced settings work perfectly.

While there were no problems/bugs, I did note one tweak that will slightly increase accuracy, and another that will make application even easier. These are being implemented now. At least one is a very minor tweak to the point where I could almost do it myself without the programmer (being done tonight). The other mod might take a bit longer, but it is not overly important anyway.

SHIPPING: I'm putting together packages for shipping. It takes me about 30 minutes to install each phone from scratch, so I wont get them all done overnight. And I have a lot of other work to do so I cant just do all shipping in one day. Shipping will be done progressively over weeks for those who are waiting. I'll contact you just before your parcel is shipped to confirm delivery address.

So essentially for the latest version, it's done. If there are bugs, 6 hours of testing didnt reveal any, in addition to other testing I've done. If you want to update your computer, follow the typical procedures and send your hardware back. Remember send only the phone itself - NO BATTERY because I cannot ship lithium batteries.

Computer update

The programmer has now fixed the issue - it turned out to be even simpler than I expected. I'm in the middle of testing it. I'll give it a full day test in Wednesday's support meeting, and if all is ok, I can commence shipping and updating computers.

Roulette computer update

I've done more testing of the latest roulette computer mods. With one exception, it is perfect as far as I can tell. What I found is more a misconfiguration, not a bug. It is being corrected but I don't yet know when - likely tonight. We are talking about something very minor like one line of code, like a plus where there should be a minus so it is not a difficult thing.

I am aware people are waiting for the computer. I am aware of people wanting to make travel arrangements to play. I am aware that people are eager to get moving. But I am doing everything I can to move things along quicker. Understand the issue is that the programmer no longer works full time for me. He struggles to find the time to fix even small issues. It is not as simple as getting a new programmer because it will take someone new a long time just to understand the source codes, and even then they are far more likely to make mistakes and changes that adversely affect the rest of the software. So it is better to "bust the programmer's balls" to get things done. I understand and appreciate how eager everyone is, but busting my balls, figuratively speaking, wont help.

Remember, what needs to be fixed is very minor and it should be done tonight. Either way I'm expecting to be able to ship this week, but keep in mind it is mostly out of my hands.

Updated roulette computer instructions

The roulette computer instructions (English only) have been updated to explain application of the new auto target feature (chapter 20). You can download them from the same link(s). You will not need new registration details.

Roulette computer updates

The roulette computer programmer was unexpectedly able to work most of today, so the most relevant recent roulette computer bugs are now corrected. From initial testing, everything appears to be perfect but I'll continue testing tomorrow. If everything is ok, I'll prepare packages for shipping.

Roulette Computer Support meeting 27th July & Roulette Computer Updates

Roulette Computer Support There will be a roulette computer support meeting on Wednesday 27th July (from 10am-5pm). This is ONLY for purchasers and partners who already have the roulette computer. The purpose of the meeting will be to cover some of the new features, and how they are applied. To attend, please email me directly to confirm your attendance. It will be a small meeting (no more than 6 or so seats) so if you want to attend, please contact me asap.

Roulette Computer Updates: I did more testing last Thursday, and couldn't find any new issues. Because it will take some time for the programmer to fix the known issues, I've requested that he do a patch job to remove the bugs. The bugs are that about 10% of the data saved to the charts is incorrect. This 10% only occurs on specific spins when the computer is calibrated for certain conditions (ball deceleration). The request I've made is to make it so the calibration still takes place, but without the incorrect chart data. All this means is application takes about 10% longer than it normally would. Accuracy is not affected.

Roulette computer mods, calls thursday, and player support meeting

Computer mods: Besides the already known bugs, I haven't been able to find any other issues. The known bugs are not critical for the most important settings, so most users will not encounter them except for one of the bugs. And that bug only means application will take 5-10% longer than it could. It's not 100% perfect so I'm not completely happy, and I'm on the programmer's case to get it perfect asap. But at least for the auto target mod, it works perfectly and I couldn't be happier. I'll start work on the updated instructions.

Calls on Thursday: I have a meeting this Thursday so wont be around to take calls. During the meeting I'll do even more testing of the latest version to further check for issues.

Player support meeting (for computer): Assuming the testing on thursday goes well, after Thursday I'll schedule a player support meeting for the roulette computer. IF YOU WANT TO ATTEND, PLEASE EMAIL ME ASAP AND SPECIFY A RANGE OF DATES THAT SUIT YOU. I expect it will be held about 2 weeks from now, during a weekday.

Roulette computer mods

The mod is complete, but the changes inadvertently caused errors with other parts of the software. I expected this because of the complexity of the source code. From testing I've done so far, it appears to only have affected MANUAL diamond targeting which will only rarely be used anyway, so it doesn't really matter. There is also one other issue that needs to be fixed (that does matter), then everything is done. If it cannot be fixed in a timely manner, we'll just use a patch that only means computer application will take about 5-10% longer than usual.

I'm submitting a full test report to the programmer today and hopefully it wont take him long to fix things. Either way I've started preparing shipments so they'll be ready once the loose ends are tied up.

Regarding a player support meeting to cover the new mods, I expect to arrange a date some time this week. Before I do this though, I will need to thoroughly test the mod again. I spent about 4 hours testing it over the weekend and couldn't find any issues, but just need to be sure.

Roulette computer update

The programmer will be spending half of tomorrow working on the updates. I'll make sure he does the priority parts first, then I can at least organize another player training session (melbourne, australia) for computer players, to cover the mods. They are very simple to apply though (which was the point of them), but any training session helps players anyway. I don't know "when" yet - it'll simply be when the programmer is done, and I've tested it all.

Also for anyone waiting for a computer, I'll ship once the mod is complete and fully tested. As painful as the wait is (most painful for me I assure you), understand there are only minor things that need to change in the software from a coding perspective. The problem is getting the programmers time. It's not as simple as finding another programmer as previously explained - the source code is just far too complex and takes at least a week for new programmers to follow, and even then they may accidentally make mistakes that affect the whole software, and I'm not even counting firmware integration.

Computer mod

The programmer still hasn't finished it. He said he'll work on it tonight. Either way I'll give him until the end of the week, then will have no choice but to use a different programmer. Understand it is a tricky situation because the mods left are so small for the current programmer, but to get a new programmer to do them will take them at least a week just to follow the code, and there's always the chance they change wrong parts which cause more problems.