Back Today & general update

I’m back today and have just been managing some tasks. While away I was responding to emails so there are very few emails left, and I’ll respond tomorrow. A few of the findings while away are:

 

·         4G works perfectly fine for the Hybrid server

·         4G and any mobile connection is terrible for online casinos

·         NBN and cable connections are overkill for the hybrid server

·         Noosa is over-populated and no longer a quiet country town. It’s great for a holiday but no longer a good value real estate investment. Better options are in outer-northern parts of Perth, and around Adelaide.

·         Brisbane’s roulette conditions haven’t significantly changed. There is some new technology but it doesn’t change much.

 

A few people have asked if I was overseas, and no I wasn’t. Noosa is just a northern part of Australia.

 

I’ve finalized the specifications for hybrid updates that help with the slingshot wheels, but they haven’t been coded yet. They are minor additions but will be available in about 2 weeks because of other tasks assigned to the programmer.

Slingshot wheels with Hybrid

I’ve been testing on a slingshot wheel with the Hybrid and found a physical anomaly that reduces accuracy. It would affect any roulette computer that uses typical primordial charts (jump charts), including the Uber, by making the ball behavior and resulting drop time much more complicated to model. The anomaly is mostly dealt with by using the Hybrid’s equivalent of target. But with any setting that doesn’t use target, accuracy is reduced (eg, from possible 30% edge to 5%). The difference between actual and predicted ball drop time can be +/-2500ms (with predictions about 20s before ball fall) which is much larger than it should be. Depending on the individual wheel, there is still likely an edge, but not the maximum possible. Hybrid users can use the target feature, but this only deals with part of the problem, and you’ll need around 50% more spins than usual for analysis. I’m working on a solution that better models the ball behavior. This will be used in conjunction with target, then the hybrid will beat a larger proportion of slingshot wheels. I’ll work on it while I’m away and possibly the update will be available before I’m back.

JAA support

Support (for JAA): I’m finding some new players are having trouble with devoting enough time to data collection. Unfortunately data collection takes time. The pre-sales website explains the amount of spins you need to collect data for so there shouldn’t be surprises. There are still lots of shortcuts you can take to reduce the time spent getting data but don’t take shortcuts if you are a new player. For instance while you collect data for scatter, collect it also for JAA. If scatter is bad then you might not use the data for JAA.
 
Also if a wheel does not seem to have good scatter, you might not have assessed scatter properly. See http://www.roulettephysics.com/forum/index.php?action=kb;area=article;cont=56
 
There is a lot of important information in the knowledgebase that all JAA players need to read. Also the checklist. See http://www.roulettephysics.com/forum/index.php?action=kb and http://www.roulettephysics.com/forum/index.php/topic,6831.0.html
 
A lot of the questions are already answered in either the video, the checklist or the knowledgebase. Please review them closely.

Hybrid server sessions

I’ve been checking the data transfer logs, and the vast majority of data transfers are from when users are logged on to the visual terminal. Remember not to remain logged on unless you are using it, and ensure the settings are for lowest data transfer. For the viewer, the settings should be 256 colors, and custom compression level set to “fast”.

Hybrid updates complete

The hybrid updates are complete and installed. So whenever you request the server to be online, it will be available for you. But you will need the updated phone app too. Contact me to request it.
 
There are now just minor software tweaks to be done, like reducing a slight audio latency issue. If users have any issues, or think anything can be made easier, let me know full details. If you think something needs adjustment, it could be that you haven’t understood the features so please fully read the instructions first. As far as I’m concerned, it’s pretty close to perfect. But I’ll try and break it next week by putting it through more tests to find possible areas for improvement. I’ll then be contacting waiting partners.

Hybrid updates

The Hybrid server software has been updated, but there will be another update before I install it. This update improves the consistency of frame rates for smoother video (always at 30 frames per second). To use it, you’ll need an updated phone app which I’ll send users soon.
 
The update before I install it deals with an issue where the Hybrid tracking doesn’t start reliably when there is a bad internet connection. Once it’s done, I’ll send users the updated Android app and confirm the server is online.

Clearer support tickets

From Support: My recent post about asking players to ask clearer questions seems to have been mostly ignored. It makes answering support tickets much more difficult than I expected. Two poorly worded ticket gives me heart palpitations. A dozen of them gives me chest pain. Pretty please, if you are writing a support ticket, read back through your ticket as if you were reading it for the first time and see if it makes sense. Some of them really don’t even seem like English and I can only piece together the questions with key words. I recognize that many players don’t speak English well, and if this is your case, you need to use simple language and choose your words carefully.