Jump to content

DCBeast

Members
  • Posts

    19
  • Joined

Reputation

10 Good
  1. Are you able to turn off both VT-d and VT-x and test iCue?
  2. Fully understand the confidentiality aspect of it. I also agree that an issues list - unmaintained - will actually cause more issues. Whatever you're using for bug tracking might have some kind of export function that would automatically keep a public list up to date... hopefully :) For me the top questions would be: 1] Confirmation that there is a plan to do something about the "unicorn vomit" when the machine is locked. 2] A rough estimate of when we might see it (e.g. Q3 '18) 3] A top-ten of issues that are being investigated 4] Is there a plan to allow a key-press to trigger a lighting event on keys other than the one pressed? For example; I would like all keys that are impacted by shift to change colour if I hold a shift key down. Also... Caps Lock state changing the colour of the alpha keys to indicate if I'll get a upper or lower character. If you are able to implement 1 & 4 I would be about out of ideas for meaningful improvements for me. BTW... 3.5.111 is your best release yet (I'm no longer having to restart the corsair service to fix my fans).
  3. That's good to hear. A specific, even if static, profile for lock state would make a lot of people very happy. I would love for Corsair to have a public high-level road-map for iCue; I think that would stop a lot of negative discussion on here.
  4. Although I would really appreciate the ability to set a profile for when my machine is locked; I really despise the rainbows and would prefer almost anything over it (except mad flashing!). I think the simplest thing to do would be to offer an 'LEDs are off' firmware version for those of us that hate the rainbows. Change the UI to let you pick which firmware you want to run (off or rainbows) and the rest of it becomes a much lower priority. I quite often work in the evenings with minimal lighting and lock my PC if I leave my desk. With four LL fans and four LED strips it's deeply unpleasant what happens to the room in these moments...
  5. Something to bear in mind specifically with the i7 3930K is that there are three steppings of the CPU. Only stepping C2 has hardware VT-d. There are generally two settings in the BIOS for virtualization support for the CPU. I'm running a C0 stepping 3930K (which overclocks like a BOSS!) and I get no black screens at all. Since Intel changed aspects of the CPU with stepping C2 to fix hardware VT-d it is possible that there is some difference with all aspects of VT between all steppings. So... you might have a C2 CPU with VT-d OFF but VT-x ON and get black screens (if that is the cause). What steppings and VT-d/VT-x settings are people running?
  6. I'll do some testing tomorrow with the VTd/x settings to see if I get any issues. Also, I wonder if there is something in the power state management and/or CPU settings. I have one of the power states disabled in BIOS because it causes my PSU to whine. Can't remember which setting that was so I'll go through and check in the morning when I'm back at my desk.
  7. Answers: 1] 4701 [05/06/2014] 2] Corsair(!) Vengeance: CMZ16GX3M4A1600C9 (4x4GB SIMMS) 3] VT-d is on. VT-x is not 4] 397.31 - Manual driver update - GeForce Experience is not installed 5] I'm using the motherboard soundcard - I actually disable the monitor audio devices because Windows likes to swap the default one from time to time. 6] 1083 - 17134.112 (Enterprise edition of Win 10) Also - your specs say you're daisy-chaining your monitors. It might be worth disconnecting one and seeing if that helps
  8. This is strange; I'm running an Asus x79 Sabretooth board with a 3930K with a 1080Ti and I'm not seeing black screen issues. The issue I have is when I disconnect a USB device attached to certain controllers on the board. This causes a complete rescan of all hardware devices on the system. For example; I have a Logitech G900 mouse that I sometimes need to plug in directly for charging purposes. When I do this, there is a sequence of USB disconnect noises followed by a sequence of connect noises. During this process my screens go blank/freeze. If I don't have iCUE installed, this does not occur. My strong suspicion is that the black screens being reported are due to a device living on the USB bus is disconnecting/reconnecting and causing the black screens rather than it being 'random'. Furthermore, I believe it will be down to specific USB chipsets or connection scenarios (e.g. a different USB chipset is servicing the ports that trigger the above than the onboard header that the LNP is connected to). It might be worth people with this issue to try disconnecting as many USB devices as they can to prove/disprove this theory. Frankly, I'm building a new machine when Threadripper 2 is released and I'm currently of the opinion that my Corsair investment will not be making the cut over. Regarding CPUID SDK usage... I can have CPUID running (with iCUE uninstalled) and disconnect USB devices without issue. I would suggest that the cause of the issue is elsewhere. Full specs: Asus Sabretooth x79 3930K overclocked to 4.4GHz 16 GB RAM Gigabyte Aorus 1080Ti - standard clocks Windows 10 latest build & patches Corsair stuff: H100i v2 K70 RGB Rapidfire Lighting node pro - 3 x 120LL RGB fans - 1 x 140LL RGB fan - 4 x RGB strips EDIT: Attached monitors: 1x 4K (Display Port) 1x 3440x1440 Ultrawide (Display Port) 1x 1080p in portrait (HDMI) 1x 1280x800 USB (DisplayLink) Let me know if there is any further information you would like. I'm also more than happy to install and run a debug build with whatever logging you've got going on to assist with pin-pointing the cause. Darren
  9. Thanks for the response. Would it be possible to go over the corner cases for this? I would like to contribute to a solution if you're open to it :cool:
  10. This relates to keyboard lighting effects: can you please expand the "Start" and "Stop" trigger list to include changes to keyboard state including: 1] Caps On/ Caps Off (Not the Caps key... e.g. If caps lock is on, but I'm holding shift I would like this to be the state "CAPS OFF") 2] Shift down/up (maybe even split left and right) 3] ALT down/up (maybe even split left and right) 4] Key modifier combination x (e.g. CTRL + SHIFT) I would like to be able to highlight keys effected by these states in my profile. For example, I would like the alpha keys to change to a different colour if they're going to be CAPS. I would also like the number and symbol keys change colour if SHIFT is down. I'm aware I can do this with a macro to change profiles but, like previous versions of CUE, this is very easy to break and is also slow. The above approach would be a lot quicker since it's in the same profile.
  11. Just to add further information on this. I was experiencing my main monitor blanking as CUE started along with USB disconnect / reconnect. The issue appears to be an incompatibility between the K70/software and the 360 wireless controller USB adapter that was connected to the same USB hub. Disconnecting the 360 wireless controller eliminates the screen blanking and usb disconnect / reconnect. Clearly this shouldn't be being caused by the CUE software but it should give some pointers to your development team and maybe offer a solution to other users.
  12. I completely agree this is a work-around. The sad part is that it doesn't actually work: Create a CAPS LOCK profile and setup the switching Confirm switching is all good by tapping CAPS LOCK a number of times Lock the PC Hit CAPS LOCK an ODD number of times Note that the profile doesn't switch Unlock the desktop Note that the profile for CAPS LOCK on/off is now inverted I would prefer to have two new features: Layers within a profile triggered by events (e.g. key modifiers, switches of key state, timers (e.g. last key pressed), external triggers via the SDK) Allow a static layer with > 0% opacity and RGB of 0, 0, 0 (black) to have the effect of turning the brightness down on the selected keys. These two features would enable responsive dynamic layers that react to modifier keys and also to be able to timeout the LEDs after a period of inactivity. Even more, it would enable something like different colours on certain keys if I hold down CTRL + ALT for example.
×
×
  • Create New...