Jump to content
Corsair Community

Elestriel

Members
  • Posts

    1,107
  • Joined

  • Days Won

    2

Everything posted by Elestriel

  1. They're working on it. It's better to disable the feature than to leave it in the state where it is potentially harmful to some drives. It's not like they're never going to re-implement it; they're trying to prevent things from getting worse.
  2. Lock indicators are driven by Windows itself. If you plug in a second keyboard, hit Caps Lock on it, you'll see the Caps Lock indicator light up on both keyboards. Yeah, you can hack Windows to screw with the indicators, but that's generally a terribly bad idea. Here's an AutoHotKey script that sends control packets to the keyboard, but they'd be reverted the moment Windows receives a toggle from those switches and you'd have to run it again: https://autohotkey.com/board/topic/9587-keyboard-led-control-capslocknumlockscrolllock-lights/ So yeah, you can control indicators using software. This goes against pretty much every best practice that Microsoft applies to indicators and accessibility, though. No company in their right minds would allow such easy manipulation of important Windows functions; it's extremely bad practice.
  3. If you'd notice the context, this discussion was about Num Lock, Scroll Lock, and Caps Lock; all hardware-driven and cannot be controlled by any software.
  4. The first thing you're going to want to do is clear the devices' memory. Go to the Settings page (the little gear icon) and under each device, there's the option to clear its memory. You can then go ahead and delete all those hardware profiles that got imported. Make a new hardware profile, and set it up however you want. Once you're done, head to the page for the mouse or keyboard. There's a new section on the left, under macroes and lighting effects. I can't remember the name off hand, but it's something like 'Save to device'. Anyway, head to that section, and you will see the profiles that are saved on the device. Select a slot, hit Save, and wait for it to do its thing. Once it's saved to the device, you're done! Now, there's an important thing to note. When you make a hardware profile, you can see its effects while you're editing it in CUE, and you can see its effects when CUE is closed, however you cannot switch to that profile while CUE is open. While CUE is open, you can only use software profiles.
  5. A really good way to get memory or CPU errors to crop up is to use Prime95. I was having BSoDs that I couldn't figure out, and Microsoft Memtest and Memtest86 both reported no issues. Running Prime95 showed me failures within seconds. Turns out that the power controller on my motherboard was supplying my RAM with a little less power than it should have been getting. I upped it by .1 volts and not a BSoD since!
  6. You can't really change any of Diablo's reactive lighting. Unfortunately, you're stuck with the keyboard being all red. :(
  7. Try using USB 2. As it turns out, USB 3.0 is actually trash. It has a tendency to drop packets a lot, which, with file transfers, is fine, since the system notices and can send the data again. On the other hand, it's too late to send the packet again with a keyboard that's displaying 40 frames per second of effects.
  8. If you use my software instead of CUE, you can set a timer to switch profiles. Of course, profiles and effects in my software differ rather vastly from those in CUE, but if you find effects you like, it could be worth a shot.
  9. Check out the status page in CUE. If it shows MALFUNCTION or simply isn't there, that's why. This has started happening to me a lot, and it's driving me nuts. We're working on figuring out how to fix it. The issue for me is that any time my computer is rebooted or wakes from sleep, or sometimes just randomly, my Scimitar isn't recognized by CUE any more. The only way to fix it is to unplug it and plug it back in.
  10. Can you give me some extra details about what you were doing? Do you have a wired or wireless Void? Is it the RGB model? Thanks!
  11. You need the Visual C++ 2013 redistributable. You can get it straight from Microsoft here: https://www.microsoft.com/en-us/download/details.aspx?id=40784 What version of CUE are you using? I'll let Corsair know about the issue.
  12. I don't think this is implemented for the Polaris, yet. Having said that, I've implemented it in my software, if you want to give it a go. :)
  13. This is a feature I built into my original iterations of my software, and that I'm planning on bringing back soon, actually. I'll try to remember to let you know once I have.
  14. You're kidding, right? You want to see improvements but you don't want to put in the small amount of effort required to actually explain what it is you'd like improved? Do you just go to the restaurant and say "give me food", and when you're dissatisfied with what they give you, you just say "this sucks" and leave it at that?
  15. You should consider changing those embedded Youtube videos on the first page to links, instead. That page simply obliterates whatever browser tries to load it!
  16. Try booting it up with only the keyboard USB plugged in, and not the extra one. Once Windows starts up, connect the second one so that lighting effects and stuff can work. This should cause Windows to realize what's going on, and hopefully enumerate them properly in future boot-ups. Also, if it's that message box that says "No device found" or something like that, it's a known issue with CUE. It bugs the heck out of me, too, but the keyboard actually works fine, and once CUE figures itself out it'll be okay. Just wait for a little bit and it tends to sort itself out.
  17. For what it's worth, I'll be implementing something like that into my software soon. It can't do everything that CUE can, but it's better than nothing!
  18. I'll be adding an idle mode to my program soon. I'll let you know once it's implemented! :)
  19. Until then, you could probably do this in AutoHotKey!
  20. C'est possible que vous avez activé l'option de 16.8 millions de couleurs. Si vous le désactivez, est-ce que le problème se règle ?
  21. I'm afraid I don't know much on the topic. I haven't played around with that hack. What I can tell you, though, is that Corsair knows we want this. :)
  22. Why not just write a controller chip that can interpret CUE colour packets? They're actually *super* simple, if you need the protocols I can tell you them.
  23. I've talked to them about this on a few occasions, and it's being considered. I'm actually fairly close to being able to hook into the G-keys, though, so if it doesn't come to the SDK I might be able to release a library that watches the keyboard and returns keystrokes.
×
×
  • Create New...