Year: 2015

Hybrid 1-3 second – further testing

NighthawkPlayer updates
Another day spent testing, but everything so far is working perfectly. Accurate predictions are generated within 1-3 seconds after ball release. When I say accurate, I mean accurate as is physically possible. Factors that reduce accuracy are:
 
1. Ball track deformations (earlier predictions are less accurate)
 
2. Faster rotors
 
3. Smaller arc for tracking rotor (if we tracked only 10 degrees of motion, there would be a lot of errors in calculations than if we say tracked 360 degrees).
 
There is still more work to be done, but the rest comparatively easy.

Hybrid 1-3 second prediction mod

NighthawkPlayer updates
I received the latest version today. Almost everything works perfectly, but there is an elusive error in calculations somewhere. I’ve been testing all day to pinpoint the source, and likely will be testing all tomorrow too. It is likely just an error in an equation somewhere. Clearly the majority of coding is done for it (all the difficult parts), but I don’t know how long it will take to make it perfect. I can only guess within a week.
 
Afterwards, a part of it needs to be refined so it’s more foolproof. Because if you use it incorrectly, then you’ll reduce accuracy. This additional part is not essential, but I’d rather help avoid players from making mistakes.

Android roulette computer

NighthawkPlayer updates
The development of the Android roulette computer will continue once the “system phone” is complete (the phone that applies the JAA system without needing pencil and paper). With the designed algorithms, the accuracy of the Android and Uber versions will be virtually identical. Originally I wanted to use the Hybrid’s algorithms but it may not be feasible.
 
In any event, the Uber 2-player version is capable of getting earlier accurate predictions than the Android. This is because the Uber 2-player phones use a unique approach to enable 2 players to clock the same wheel at the same time. There will be virtually no difference in accuracy between the 1-player Android and Uber versions.
 
So what is the point of the Android?
 
1. It is designed more for profit split partners, where data is monitored and stored on my server.
 
2. It is designed to be more user-friendly for new players. For example, the Uber may take 1 week to fully learn, and the Android may only take 3 days to fully learn. But once a version is learned, there is no significant difference.
 
3. The Android will be more affordable (lower start up costs, but higher long term costs)
 
So there are positives and negatives to both versions. If you are considering these versions, with price not being an issue, the benefit of getting earlier accurate predictions makes the Uber the better option.

JAA linked to mobile phones

NighthawkPlayer updates
The “system phone” should be available for use in about 2-3 weeks from now. Development stopped for a while because I didn’t have time to test the developed software, but recently did and development is nearly complete.
 
The cost of the software $0 to existing players, but you will need a compatible Android phone with some modifications. I should be able to provide suitably modified Android phones for around US$1000 but if you have some electronics experience, you can do the mods yourself.
 
This is basically an Android phone app where the player can input the winning numbers and various data about the wheel, and the phone will automatically tell you where to bet. And if the wheel ratings aren’t good enough, it will tell you. You input the data using a hidden cable and wireless earpieces, so nothing is needed at the table, and nothing is visible to casino staff. You don’t need betting charts, pens or paper. But keep in mind the use of electronic devices in this way is still illegal in about half of the casinos, so check your local laws first.
 
Remember though, although it makes application of the system even easier, you must still properly evaluate your wheels. Remember to carefully read the checklist too.

Help desk tickets

NighthawkPlayer updates
I’ve responded to all help desk tickets and emails. Just a reminder that when you send me a long list of questions, you should use the format:
 
1. This is one question
 
2. This is another question.
 
And there should be one clear and direct question. This means one question mark per question.
 
But many players are asking questions like: What can I do if this happens? And what about this or that? And what about this when that happens? (all on one line)
 
And long questions like this are very time consuming to respond to. Especially when there are many paragraphs like this.
 
If you have background information about a question, then please very clearly explain it. For me to give everyone good support, I need everyone’s help in making things easier for me. Do not ask poorly worded questions. Put some time and thought into what you are typing.

Android Vs Uber computer

NighthawkPlayer updates
Many players are asking me about the differences between the Uber and Android computer. See the below points:
 
* There will be different stages of development. So gradually more capabilities will be added, although at this stage I cannot guarantee how far the development will go because everything that can be done in such a computer has already been done in the Uber. So the below points are based on development I know will be done:
 
* The accuracy is almost identical if you get late predictions. In the first version, the Android will be less accurate, but later the accuracy will be the same
 
* I may or may not implement some of the Hybrid’s algorithms, which will make it more accurate than the Uber. But this may be around 5-6 months from being available. I cannot guarantee I will even implement those algorithms.
 
* If you need very early predictions with accuracy, only the Uber does this. I dont plan to develop the Android so that it can get accurate predictions that are very early (by using two players clocking the rotor and ball at same time). This is because the Uber already does it and its a very complex mod. I may change my mind – it more depends on my available time to work with the programmers.
 
* The main purpose of the Android’s development is for partners or lease agreements. All of the wheel’s data is uploaded to a server so I can easily check the data and advise players. The Uber requires the user to send me data manually.
 
* The Android’s screen is bigger and easier to see. This makes no real difference though. You see see more than what you need on the Uber’s screen. And for those who don’t know how roulette computers work, no you do not watch the phone’s screen while using it at the table.
 
* The Android version will have like a wizard process for assessing wheels and applying the computer. So it will be simpler for new players to use.
 
In all, the Android is not a needed computer. It is overkill and perhaps I have an obsession with roulette computer development. The Uber already does everything that is possible. There are several main reasons I wanted to develop it, with the primary reason being I wanted to create a version that was as dummy proof as possible, by using a setup wizard that guides you through the whole process of assessing the wheel and applying the computer. And it is easier to work on Androids than the Uber phones. I didn’t want to modifying the already perfect Uber source code. And for players that understand perfect English and don’t mind a bit of extra reading, the Uber is likely to always be a more capable device than the Android.

Android roulette computer

NighthawkPlayer updates
There are no further developments with the android roulette computer yet. The programmer is still working on higher priority tasks I’ve assigned. It still may be another month or two before the android is available. I will post another update when he begins work. There is an a lot of work left, so once he starts, he won’t take more than a few weeks.