Hybrid V3 Progress

Current progress below:

 

Part 1. Main component (central computer) that tracks the wheel location, and rotor / ball timings (100% complete): This is the "high tech" part and it works perfectly.

 

Part 2. Mobile phone and central computer data processing (90% complete). This is the set of procedures that tell each component what it needs to do with the data, how to reset and wait for the next spin etc.

All the mobile phone parts are done, except for telling the central computer when to start actually tracking the wheel, but this part is simple. The central computer still needs to have a few extra routines although they are minor.

 

Part 3. The wireless communication (90% complete): The communication is working perfectly on a MAC O/S, but there are still issues on a Windows PC. Specifically it works on one Windows PC, but not another and we just need to find out why to ensure the central computer (PC) is working as it should. It is just a matter of using the right drivers.

Online Casino Bot Upgrade

The bot for online casinos now allows 2000 spins before unlocking is required. It was previously 500 spins. Download the new version from the same location.

Hybrid V3

The wireless messaging is working two-way but has a cache issue that causes instability, although it shouldn't be difficult to fix. It's more about bug fixing.

 

So the work done is:

 

Part 1. Main component (central computer) that tracks the wheel location, and rotor / ball timings (100% complete): This is the "high tech" part and it works perfectly.

 

Part 2. Mobile phone and central computer data processing (70% complete). This is the set of procedures that tell each component what it needs to do with the data, how to reset and wait for the next spin etc. This is straight-forward coding and about a week from completion.

 

Part 3. The wireless communication (80% complete): this is what caused the main delays because different devices have different firmware, and they need to work together. Now its more bug fixing to ensure the connections are reliable.

 

Once part 2 is complete, its just a matter of ensuring the connection is stable, then testing.

Uber Update

Work has begun on an Uber Update. The modifications are more to do with making the advanced methods much easier to use. Already auto target does much of the work without much effort, but this update will be more about automatically isolating the individual spins on which the ball will fall most predictably. It is closely related to the existing auto target, but this will take things even further.

 

This is not a minor update so it will take around a month. The coding itself is not complex, but working around existing code is so we don't create bugs.

 

Unfortunately it will not work on all phones because a lot of data needs to be stored, which is more than the phone's native firmware supports. It is possible that some existing phones will only need various tweaks without a firmware upgrade, but we wont know until further in development.

JAA and Hybrid V3

JAA: The JAA software has had an update to security to protect from hackers. If the hacker could try again to assist with testing, it would be much appreciated. Additionally, soon the latest version will be installed, which will add features like importing spins from text file etc. I'll announce when its available, then ask that players report any issues/bugs.

 

Hybrid V3: The delay is because the wireless communication between different parts is very fiddly. The electronic components use different firmware, and the conflicts cause instability with the wireless transmissions. In the last 24hrs we identified that this is because the central component uses a 64 bit operating system which is "buggy" when it comes to wireless communication. So we are testing on a 32 bit system asap. Like some of you, many plans for me are on-hold until this Hybrid version is complete. There's barely a minute of the day where I'm not thinking of how to speed progress up. Unfortunately this part is very tedious and painful and we can only wait while we sort out the issues. Remember though, the main parts that deal with the tracking of the wheel (including getting all timings) are already done and working perfectly. The only issue is now just wirelessly sending those timings between the various components.

Calls & Email responses

Just a note that tomorrow I'll be away until midday so can only take calls when I return. In between calls, I'll respond to the rest of emails.

Hybrid V3

The programmers informed me this morning that they are "a few small bits from full completion". There was an issue where one component would send the wireless message no problem, but on the second message, a crash occurs. So they just have to fix this issue then tidy up. There's nothing else I know for now.