Jump to content

MadIce

Members
  • Posts

    92
  • Joined

  • Days Won

    1

MadIce last won the day on September 19 2015

MadIce had the most liked content!

Reputation

12 Good
  1. I love to have those new keycaps. Most that are available, do not support lighting and those who do, are not compatible with the spacebar or other bottom row keys. :) It would be much appreciated. Let's hope these will be available in Europe.
  2. If you mean a switch to change the polling rate (like the K-series) then no. You can change the polling rate in the CUE, though. No specific BIOS-mode option, though.
  3. Here's another variation of my previous request, which is more powerful, because it can be used with any key (not just the lock keys): In the Foreground Lighting Editor I like to see the following changes: In addition to the two existing "Start" options (leave those as they are), have a third option with a dropdown list to select one of the following events: - "On CapsLock is On" - "On ScrollLock is On" - "On NumLock is On" - "On WinLock is On" Example: If "On NumLock is On" has been selected and the mode starts then it checks the NumLock status and shows the lighting when it was set. It should also start when NumLock has been switched on by the user. In addition to the three existing "End" options (leave those as they are), have a fourth option with a dropdown list to select one of the following events: - "On CapsLock is Off" - "On ScrollLock is Off" - "On NumLock is Off" - "On WinLock is Off" Example: If "On NumLock is Off" has been selected then the lighting should end when NumLock has been switched off.
  4. I would like to have the CapsLock, ScrollLock and NumLock act as a true lock status indicator, much like WinLock. One can fake that now by setting a light effect, but that way the "status" is lost during mode/profile switching.
  5. Another simple feature I would like to have: The Void beeps whenever a profile is activated. It also does this during a boot. I wish I could switch off any non-critical warning beeps in cases where the Void just does it job and works as intended.
  6. There is a simple feature that I would like to have: When you start the CUE software from the system tray after a reboot it switches to the first profile (the first one in the alphabetically ordered profile list). This is counter-intuitive, because that may not be the one you are using. What I like to see is that it doesn't do that and keep the currently set default profile active instead. After all, that's the one activated after reboot before you started the CUE from the system tray. The second time you start the CUE in a Windows session it does load the currently set default profile. So no complaints there. It's still confusing as to why it didn't do that the first time, though.
  7. It works fine for me too. At first I thought the microphone level was too low, but I found out how to set it properly. I'm using the USB version, but I don't think the wireless one will be much different. Maybe this is useful to someone. I assume you've connected the headset and installed the CUE software. I've created a profile called "Desktop" and used the following settings: http://madice.home.xs4all.nl/Hardware/Corsair/VoidRGB/USB/CUE/Install001.jpg Set both the Mic and Sidetone levels to the maximum. Also make sure that both are not muted. If the two icons above show different ones on your system then click them until they match the image. http://madice.home.xs4all.nl/Hardware/Corsair/VoidRGB/USB/CUE/Install002.jpg Now we make sure that these settings are actually being used. To do that left click the hamburger menu next to the profile name. In my case the profile is called "Desktop" (but yours can differ). A menu appears. If the last option of that menu doesn't have a tag mark in front of it then click that option. That makes sure that the profile is being used when you exit the CUE software. http://madice.home.xs4all.nl/Hardware/Corsair/VoidRGB/USB/CUE/Install003.jpg Go to the control panel and open "Sound". A dialog window appears like the one above. Click the second tab there ("Recording"). Find your headset. If that headset doesn't have a green tag mark in front of it then right click the headset. A menu appears like the one shown in the image. Click "Set as default device". After that click the "Apply" button. http://madice.home.xs4all.nl/Hardware/Corsair/VoidRGB/USB/CUE/Install007.jpg In the same "Recording" tab in "Sound" right click the headset's microphone and select "Properties" from the popup menu. In the dialog window that appears, click the "Advanced" tab. Make sure to disable the "Allow applications to take exclusive control of this device", like shown above. If the option changed then click the "Apply" button. The above makes sure that background applications cannot take over control of the microphone. http://madice.home.xs4all.nl/Hardware/Corsair/VoidRGB/USB/CUE/Install004.jpg Make sure you are still in the "Recording" tab. Right click the headset's microphone and select "Properties" again from the popup menu. In the properties window use the second tab, called "Listen". If there is no tag mark in front of the "Listen to this device" option then click it, until one appears like shown in the image. Hit the "Apply" button. The step above greatly improves the feedback you'll get: You will hear properly what is being recorded by the microphone. However, you don't need this option, because it doesn't actually change the microphone level. After you are done testing, you can switch it off. http://madice.home.xs4all.nl/Hardware/Corsair/VoidRGB/USB/CUE/Install006.jpg Another way to test the microphone level is to use the Steam voice settings. http://madice.home.xs4all.nl/Hardware/Corsair/VoidRGB/USB/CUE/Install008.jpg In the "Sound" dialog window mentioned above, click the "Communications" tab. Select the "Do nothing" option to make sure that Windows doesn't change any levels when it detects a phone call. Hit "Apply" when required. http://madice.home.xs4all.nl/Hardware/Corsair/VoidRGB/USB/CUE/Install005.jpg Finally, in Windows 10 there is a privacy option which can prevent the microphone from being used. Open the "Settings" window (by typing Settings in the Windows search box near the start menu) and click "Privacy". Then click "Microphone" in the list on the left. Make sure the "Let apps use my microphone" option is set. You may see apps show up there. Here two of them have the microphone disabled. Enable those you feel are safe to use. Some applications, like games, may not show up here. Don't worry, they will use the first option ("Let apps use my microphone"), which we've just enabled.
  8. That's a good idea. I had the same problem with my K95 RGB. I sent it back and got a replacement. And now that replacement has the same issue. Different keys, though. I'm now waiting for the second replacement. To make sure it is a hardware problem, create a new profile. Make all keys white. Do not use any other colors or effects. Save it to the device memory and make it the default profile. You can then clearly see which keys have the problem. In time you will get more. If you tap the keys or shake the keyboard gently, some keys may or may not change their color. It has been discussed before and we think it is a problem with bad soldering of the LEDs. BTW: It doesn't matter if you have 16.8 million colors enabled or not. If it is a hardware problem then it will show up in both modes.
×
×
  • Create New...