Our mechanical gaming keyboard model RAVEN now comes with GTX1060 6GB and 4K display options.

Hi there

Can I have your serial number?

Hi Eterman,

For RAVEN, the EC does have the smart charging feature.

The MyApp does save the settings, there might be a bug or error. Can you pm me your serial? Will assist.

serial PM-ed. i stumbled upon a fix or it is the actual method of saving setting. 

i need to spam click on the "save" button, then the light intensity will be saved, even when coming out of idle mode.

Hi Eterman,

The new Raven EC is released together with the Intel Vulnerability BIOS fix. You may request from support@illegear.com with your serial number.

any updates on raven keyboard lighting not saving?
There are some further lighting behavior i wanna clarify, including the mycolor2 process.

1. as per my previous post, my lighting brightness setting most of the time doesn't set, when coming out of idle (not sleep/hibernate), it will default to original medum brightness (the setting in the app remained at medium-low)

2. mycolor2 process taking up CPU power when some of the lighting options are selected :
-static color : 6-10%
-stacker : 6-8%
-impact : 6-7%
-music : 7-15%
-other color options show usage <1%

is this a bug, or it is normal for keyboard lighting to use so much CPU power?

3. the "Saving mode" according to description, if i tick it, the lighting will go off after 10minutes idle or when the screen goes idle(blank), but to me , it doesn't make a difference, the lighting is like on permanent "saving mode", the lighting will go off after idle or screen goes blank, regardless whether i tick or untick "saving mode".

just did some research and found out nvidia optimus actually had more problems. but last time i had a fren who use a single-gpu laptop with no intel and he complained his laptop getting super overheated and it restarted everytime he played games. any existing user had similar problem before?

Didn't actually have any of the micro-stutter thing on my S5X TBH, though I don't actually have any of the Intel/Nvidia stuff on my context menu (removed them all via registry) and actually stuck with the stock drivers for both Intel and Nvidia so that might just be it.

Also, yeah, overheating is more the cooling system (heat paste, sinks and fans) then either Optimus or the GPU/GPU. I mean, the chips get hot anyway, if it overheats to the point of restarting then that particular chip has NO place within the laptop it's being used in, i.e. it's just bad design.

For example, the SHIT loose-tripod heatsink system on the current Alienwares are the MAIN reason why some Alienwares have the infamous unbalanced CPU overheating as the heatsink isn't being evenly held down against the CPU.

Although, heat paste application quality can actually vary quite a lot amongst laptops so it might just be that.

We have gathered most of the feedback and sent them to FAE so we shall expect new EC and BIOS updates very soon.

Meanwhile, there will be a new ONYX/RAVEN Command Center released next 2 weeks as well.

What is affected? 
AMD, ARM, and Intel CPUs are affected by CVE-2018-3639 to varying degrees.

What is the risk? 
Microsoft currently assesses the risk posed by CVE-2018-3639 to our customers as low. We are not aware of any exploitable instances of this vulnerability class in our software at this time, but we are continuing to investigate and we encourage researchers to find and report any exploitable instances of CVE-2018-3639 as part of our Speculative Execution Side Channel Bounty program. We will adapt our mitigation strategy for CVE-2018-3639 as our understanding of the risk evolves.

What is the mitigation? 
Microsoft has already released mitigations as part of our response to Spectre and Meltdown that are applicable to CVE-2018-3639 in certain scenarios, such as reducing timer precision in Microsoft Edge and Internet Explorer.  Software developers can address individual instances of CVE-2018-3639 if they are discovered by introducing a speculation barrier instruction as described in Microsoft’s C++ developer guidance for speculative execution side channels. Microsoft is working with CPU manufacturers to assess the availability and readiness of new hardware features that can be used to resolve CVE-2018-3639. In some cases, these features will require a microcode or firmware update to be installed. Microsoft plans to provide a mitigation that leverages the new hardware features in a future Windows update.