I wanted to give everyone an update on the internal progress of CUE and the top issues that are widely discussed. CUE is something we’ve been hard at work here that involves an immense amount of resources from the developers, software engineers, validation, and the beta testers. As I’ve stated in many threads, part of the difficulty of resolving bugs is both the frequency of which it occurs and the hardware configurations they affect. For the vast majority of users, most people are able to use their keyboards without any issues. However, we want everyone to have a flawless process and we are working with a number of you to note the issue and to document as much information as possible to resolve it.
To give some layer of transparency, I’d like to update you all on the top 3 issues that people have been reporting for CUE:
1.) 16.8 Million Colors: This is considered to be issue #1 in house and we been working on a solution for this for a long time now. We apologize it has been so late since the last promised update, but we are still progressing towards a resolution. The reason for this long delay is that it is a combination of both firmware and software. They both work in conjunction and both the developers and our software engineers are doing everything they can to resolve this as soon as possible, unfortunately I still don’t have an ETA to provide.
2.) Steam Issues: The good news is that thanks to everyone who submitted their system data, we have been able to follow-up and may have a resolution with the issue that affects the small minority of users affected by either light freezing while Steam games are running, or issues that may cause Steam to crash. The bad news is that the fix is a long and complicated one that may take at least 8-10 weeks to resolve. Like the 16.8 million color issue, it is a combination of both firmware and software that involves a massive workaround to encompass all the different aspects of hardware. Again, because this doesn't affect a majority of people, but the solution has to work for everyone anyways.
3.) Long POST process in BIOS: This issue is actually related to how certain BIOS in a small group of motherboards have a difficult time communicating with the keyboard in POST. To be frank, the USB enumeration from the keyboard is too quick for some BIOS to properly receive and hence ends up hanging the BIOS for a prolonged (2-3 mins) at a time. This doesn’t affect all BIOS either but it is aggravating for those who experience it. The temporary workaround you can use is to toggle the button on top of the keyboard to change the polling rate from 1/2/4/8 to BIOS and then change it back afterwards. The long term solution is that we may implement some type of delay for the keyboard to be registered to bypass those systems that have this BIOS issue. We’re also working with some of the motherboard manufacturers to resolve it through a BIOS update too.
In the meantime, while working on these issues with long term solutions, we are planning a new CUE update by the end of the month that is currently in validations (if no serious issues are found). We will have even more bug fixes in this version not noted here as well as a newly implemented feature for users who desire out of the box effects. So while the top 3 issues may take a long time to resolve, we are working in parallel to resolve lesser known issues in order to improve the overall experience. It has been a slightly bump road but I am sure all of you have seen the improvements since release back in September. I encourage all of you to continue posting issues you may have so we can deal with them as they come up.
If you have any specific concerns or questions, my PM box is always open (give me 1-2 days to reply as I can get a lot of messages). We want to ensure that everyone is happy with our products. If for any reason you’re not, our support team, and I will do what I can to make your experience a positive one.
