Corsair CJ

Thanks for putting this together guys. I've pinned this post for reference.

You can work around mystic light by disabling SDK in CUE/iCUE's settings panel. You should also be able to tell Mystic Light to ignore DRAM by unassigning them in the software.

Godspeed and best of luck with the build. I look forward to seeing the results. We've built a few 1000Ds in the office and the sheer size and scope of what you can cram inside of it takes a bit to adjust to. :)

K68 RGB does not support hardware playback which in turn would mean no hardware profiles. If you're trying to save static lighting, there should be an option to save any static lighting effects from a profile to the keyboard. Make sure you have the K68 selected and setup whatever static lighting you want. Then expand the profile options menu and click the save icon in the drop down that appears. Screenshot from my K70 for reference (it should be similar to K68 RGB).

1000D does not have curved glass due to manufacturing complexity and the resulting QC that would need to be maintained. That spare part listing has the incorrect image. I realize that might be a bit of a downer, we tried our hardest to make the original Concept Slate aesthetic work for mass production, it just didn't pan out.

We know you guys have been wanting this since we showed off Concept Slate at Computex last year... So today we're proud to announce that the new Obsidian Series 1000D has been released to the wild! https://www.corsair.com/us/en/obsidian-1000d-case [ame] [/ame]

Solarity's got it. iCUE combines CORSAIR LINK and CUE into a single software utility.

Don't be hard on yourselves, the feedback is still very useful. There may be a way to make this more obvious in the future, since I imagine many other folks that aren't on the forum have run into this.

Hey everyone, Attached to this thread is what we call a QSG (Quick Start Guide) for the CORSAIR ONE. Please note that the .zip file contains different languages. CORSAIR ONE QSG WEB PDFS.zip Also! If you're having trouble finding the physical quick start guide in your CORSAIR ONE packaging, I've reposted a diagram that Corsair StormShadow put together last year to help you find it. (Link to original thread) CORSAIR ONE QSG WEB PDFS.zip

I see. Thanks for trying that for me. Would you mind sending me the .zip file that's generated by the "Export Log" function in iCUE's settings panel? Please send this over DM rather than posting in this thread. I'll log this as a bug and report it to our dev team.

Try running iCUE / CL4 without HWMonitor running. If there are different USB 2.0 headers on your motherboard, try moving to a different header as well.

Thank you everyone for your interest in Sync It! We've taken the first step to realizing the Sync It concept with the early access release of CORSAIR iCUE. New Forum Section for iCUE Discussion: http://forum.corsair.com/v3/forumdisplay.php?f=280 CORSAIR iCUE Introduction Video: [ame] [/ame]

ML RGB fans should be supported with the next major update to iCUE. As DevBiker said, you can fake it for now by treating the ML fans as HD fans in the Lighting Setup panel for your LNP/CLCP.

Understood. The team is aware of this and are looking into the cause.

Spectre and Meltdown Vulnerabilities Affected CORSAIR Products These vulnerabilities affect: • Bulldog (with motherboard) • Bulldog 2.0 • CORSAIR ONE What are Spectre and Meltdown? Undoubtedly there is some alarm about the security exploits dubbed “Meltdown” and “Spectre,” both of which center around a fundamental design principle of modern processors. High performance processors designed within the last ten to fifteen years can predict with a high degree of success what the next instructions will be when performing a task, and in doing so are able to substantially improve performance. This “speculative design” is one of the cornerstones of modern high-performance computing. Unfortunately, researchers have recently discovered two security exploits you may have heard about, dubbed “Meltdown” and “Spectre,” which abuse speculative design through virtual machines (virtual PCs running on top of existing hardware.) We’ll talk about Meltdown first. Meltdown is a flaw endemic to Intel processors designed over the past decade and affects almost all of them, dating back to at least the original Core i7 and including all the way up to the recently released Coffee Lake and Skylake-X processors. This is something intrinsic to the silicon itself; it can’t be remedied by a BIOS update. Note that this does not affect AMD processors. Patches have already been released for major operating systems (including Windows) to close this exploit. You may have heard of an upwards of 30% performance impact as a result of the security patch, but note that this is primarily on the data center side. Our customers will receive the patch automatically from Microsoft and should see virtually no performance loss; TechSpot ran both synthetic and real world benchmarks and revealed no perceptible difference to end users (https://www.techspot.com/article/1556-meltdown-and-spectre-cpu-performance-windows/). The other flaw is Spectre, and it affects all modern processors, Intel and AMD alike, extending even to smartphone processsors. This exploits any modern CPUs that utilize speculative designs to improve performance. The industry is collectively working on ways to solve this problem, but because of its nature as a fundamental exploit in modern processor design, this is going to take a longer period of time to fix. Individual software suites will need to be patched to close this exploit. On the flipside, Spectre is also much harder to abuse than Meltdown is, and it’s important to note that in both cases, these are read only exploits. On their own, they can’t run malicious code on your PC, and they can’t open the door to additional malware. Additionally, they require code to run locally on a system in order to work at all. What to Do Intel, Microsoft, NVIDIA, AMD, and other software and hardware vendors are working aggressively to mitigate Meltdown and Spectre. Here are some things you can do to protect yourself. Update Windows One of the easiest things you can do is make sure Windows is up to date. Windows 10 installs updates automatically, but to manually check, do the following: 1. Click the Start button. 2. Click the Settings (gear-shaped) icon. 3. Click “Update & Security.” 4. Click “Windows Update.” 5. Click “Check for updates.” Update Your Video Card Drivers The next thing you can do is update your video card drivers. You can always get the most recent version of your drivers from https://www.geforce.com/drivers if you have an NVIDIA GeForce graphics card, or http://www.amd.com if you have an AMD Radeon graphics card. For CORSAIR ONE users, we are providing an updated graphics card driver on our download page (http://www.corsair.com/en-us/downloads). You can also visit the product page for your CORSAIR ONE model to download the updated driver. Update Your BIOS The BIOS in your CORSAIR ONE or Bulldog system will also need to be updated to mitigate Meltdown and Spectre. We are working with Intel and our motherboard vendors to provide these updates; once they are available, they will appear in this section with instructions on how to perform the update.

I recommend contacting our support team regarding your current kit if you're having issues. Memory version can be found on the label on each module. Different versions can use different ICs depending on availability (the market tends to fluctuate from time to time), but they are validated and tested for the rated speed advertised.

I've tried this on a number of versions of CUE and it's worked fine with multiple applications. I'll ask James if it was addressed in a specific version and/or if he was able to reproduce it on his end when he first responded. Edit: Managed to reproduce it with notepad, but only if I execute the launch app macro with desktop in focus and no other windows onscreen. I'll reach out to James as mentioned before.

The Vengeance LPX and LED listings you posted should work just fine. Ryzen can push up to 3200MHz DDR4 depending on the config. 3000MHz seems to be fairly easy to get to on most boards with a two up module config, 2666MHz is going to be safest of course. It's up to you if you want LED lighting, or want to save a few bucks and go for the LPX model.

I wouldn't recommend going in and unplugging the front LEDs, you can however set the front LEDs to a dim, but not completely off setting. Not ideal, I know, but they shouldn't flicker at that point. I've reached out to our dev team to see if they're able to recreate it on their end.

Have you updated to the latest version of Corsair LINK for the Corsair ONE? Direct download link: http://downloads.corsair.com/download?item=Files/Corsair-One/CorsairOne_CorsairLink_02282018.zip

Intel Z370 supports up to 4 physical DIMM slots on larger boards, but the m-ITX board in CORSAIR ONE cuts that down to just 2 physical slots. The phantom slots reported are likely a minor oversight in the diagnostic software. To get 32GB in CORSAIR ONE, you'll want to find 2x16GB modules Here is a selection of kits that would physically fit in the CORSAIR ONE. They have not been validated to work with CORSAIR ONE specifically, but should work as a drop in upgrade since we're still talking about memory that'd be used with a Z370 board and i7-8700K at the end of the day. http://www.corsair.com/en-us/memory/vengeance-lpx-series?color=Black|&memorysize=32GB%20Kit%20(2%20x%2016GB)|

http://forum.corsair.com/v3/showthread.php?p=939440#post939440 Programming individual key lighting is not something we had planned for the K63 wireless. That being said... we're currently looking into similar functionality for future firmware/software releases as a customization option in CUE due to the feedback we've received so far.

Our dev team is investigating the cause behind these crashes that some of our users have been experiencing with the most recent update to CUE. Here are some instructions for a workaround that should get most of you up and running again: Open up File Explorer and go to %APPDATA% Locate the Corsair folder and rename it to Corsair.OLD (or simply delete the folder) Start CUE and it'll recreate the folder If these instructions do not work in your case, please contact our support team at support.corsair.com, use the search feature of the forum to see other workarounds, OR create a thread and ask us/the community for help.

There will be changes, obviously. Can't confirm anything at this time though.

I can see this being achieved through our CUE SDK. A community dev could write an application that talks to smart lights and our peripherals to enable this sort of functionality. We'd just be missing the component side which is currently handled by CL4. :thinking: