Hybrid V3 and Uber Updates

The new programmer is moving very quickly, and is understanding everything very well. He has started actual coding initially for some Uber updates (minor updates to begin). But so far he is unable to test them because the Uber software will not run on anything but the specific phone models the Uber is developed for. The Hybrid V3 uses the same phones. The software wont even run in an emulator. As the phone model is discontinued, I've shipped him phones from my stock. They'll arrive in a few days, then he'll be able to continue development.

 

Once the minor Uber update is complete, he'll begin work on the Hybrid V3 phone component. As he is proving a competent programmer, I don't expect this part of development will take more than 1-2 weeks once he focuses on it. So at this stage it looks quite certain that within 30 days, the Hybrid V3 will be fully complete and ready for actual use, including testing, all components ready and all. The testing alone will take 1-2 weeks depending on what, if any, bugs are found. Almost always there are bugs which is a normal part of development – we just do all testing and correct them when found.

New Uber Version

I now have a new programmer for further development of the Uber roulette computer. One of the determining factors of a player's success is their ability to understand the chart data. Players tend to think they understand it, but still about 80% of players don't accurately recognize their edge – they look for wheels with glaringly obvious peaks when often you don't get this despite having a clear edge. This is partly due to the fact that visually determining an edge with mere charts is insufficient. So the Uber upgrade will give players a perfectly clear indication of whether or not there is an edge, and if so, approximately what it is. This is not as simple as highlighting peaks on a chart.

 

As I have said previously, I don't think the accuracy of the Uber can be improved further. But there is still room to make it easier to use, and this is the focus of development. In roughly 2 weeks, I will know more about when it will be available.

Hybrid V3

I've now hired the new programmer for the mobile phone component of the Hybrid V3. At this stage he is just reviewing various material to become familiar with the overall project and requirements. Based on what he knows so far, he estimates realistically including understanding existing code, he should be able to complete everything within 30 days. This is more a conservative estimate though and expect it wont take that long.

 

JAA

The programmers are still working on JAA, but I tested this morning with a 1500 spin profile, and it seemed to work no problems despite it taking about 2 minutes for the server to complete the analysis. The analysis did appear correct but I wont be fully checking it all until the programmers tell me they've finished tinkering with it.

 

The test this morning suggests the main bugs with the functionality are corrected, but still there are no performance enhancements as the mods were supposed to achieve. But still a 2 or so minute wait for analysis to complete is more bearable than auto analysis not working at all. Anyway I'll give more updates in time, but for now don't use auto analysis for real.

Hybrid V3, Induction Loops and General update

Hybrid V3: Again all that's left to do is the mobile phone programming part. But I need a new programmer for this. My focus is mostly on finding the right developers for the work. It is literally only about 1-2 weeks of coding left for it to be complete, but having to find an additional programmer takes a long time especially for this kind of work. We really need people that know what they are doing or they may waste weeks just trying to understanding the existing code. I did have a programmer set a short while ago, but he didn't like the complexity of the code despite initially assuring me it wouldn't be a problem. Nevertheless I expect to have chosen another developer by mid next week. At the very least all the difficult coding and development is already done and working better than I even hoped for.

 

Induction Loops: You may recall earlier batches were easily "blown" if you put the battery in the wrong way. It seems the newer batch still has this problem. So for anyone who needed new loops, I'll send two of the older ones which work perfectly fine, unless you put the battery in the wrong way. So don't do it, and carefully check how you put the battery in (the polarity)! Nevertheless I've ordered 100 loops with the vulnerability properly addressed.

 

General update: Most of my time is being taken up by communicating with programmers either for JAA, Hybrid V3 or other projects. So I'll be on Skype a lot, but I'll be unable to chat much to anyone but programmers. If you see me online it is ok to ask a quick question, but by quick I mean quick. I do not want to appear rude or abrupt, but when 20 people each want only 5 minutes of my time, a large chunk of the day is used. Believe me I'm prioritising tasks so issues for the most people possible are addressed.

JAA Software

The software has many issues that appear to be server resource issues. ie we need a more powerful server. Currently a few people using auto analysis at the same time with 1,000+ spins will cause a crash.  First we'll try upgrading the server. If that doesn't work, we'll need to do a complete move. I'll know more within about 24hrs.

Code Requests

Many players are incorrectly using the code request form. For example, the incorrect product or item is specified for the code submitted. Specifically a player may request unlocking of a document for product they do not have, and such requests are automatically rejected. Additionally, many players are forgetting to specify their e-mail address, so I cannot verify who has made the request. If you haven't received an unlock code for any recent request within 24 hours, your submission had some kind of error and you will need to resubmit.