Jump to content
Corsair Community

Leaderboard

Popular Content

Showing content with the highest reputation since 08/20/2021 in all areas

  1. Hey all, I'm a big fan of Corsair stuff I must say. I've had numerous cases and peripherals over the years, and i'm quite happy with everything. In fact on the reddit/r/corsair sub, I recently posted my new 5000x /w XD7 build. Huge amount of Corsair stuff inside the case, as well as keyboard / mouse / headset. I even picked up a Nexus yesterday for monitoring. (That I think is fantastic for what it does, for what I need.) BUT FOR THE LOVE OF ANYTHING HOLY! Please, please, please fix or enable the ability to SAVE the bl00dy HOME page and DASHBOARD layouts. EVERY time, I reboot, or even lock my workstation and come back, not only is the layout reset, but all the sensors and graphs that I have lovingly ordered to my preference, have gone back to some ordering that Icue thinks is better than me. That's it isn't, the the icue stuff is silently judging you. Also, the Multi / Single OCP settings on my ax1500i, well they just don't work.
    3 points
  2. Hey there everyone! DevBiker from deep in the heart of Texas and I'm just starting down the path of rebuilding my rig into a Corsair 7000 series case. I've gotten my hands on the iCUE 7000X RGB in white as well as the front and top panels for the 7000D Airflow editions (also in white, though black may have been an interesting contrast). I do plan on playing around with it a bit ... to rearrange things a bit and rebuilt it several times, looking at different options. Over the next month or so - before I do the actual build - I'll be playing around with the case and measuring things and seeing how different things may or may not fit. I'm not going to go over all the marketing fluff - except for a single Obligatory Marketing Image - because y'all can read all of that stuff on all the various reviews that are out there. So with that ... this should also be a discussion. What ideas do y'all have for the 7000? I've already talked with one other forum member that was looking to put a monitor screen on the PSU window and I got some measurements for that. You'll that info in the FAQ as well (under PSU installation) I'm using the new Album feature for the FAQ; comments are enabled for each photo so you can ask questions there or here. It's best to view the Album by Caption. I like the List View, personally. Table of Contents - each link points to the first image in the 'section' . 0001: Intro, Marketing Image, in the Box 0002: Devices, including the Commander Core XT 0003: Motherboard Mounts 0004: PSU Shroud, including vertical GPU mounting 0005: PSU Installation 0006: Drive Cages and SSD Mounts 0007: Front Fans and Radiators 0008: Side Fans and Radiators 0009: Top Fans and Radiators 0010: Outer Glass and Panels (In Progress ...) Corsair 7000 Series Cases / HydroX Options : This is an ongoing list of different configurations with HydroX and the 7000 series cases. Diagrams: RGB Diagram for 7000X with 2x XR5 420mm Much thanks to the folks at Corsair as well for helping with this by answering questions and providing a LOT of goodies for this build!! Links to the 7000 Series Product Pages: iCUE 7000X RGB Tempered Glass in Black and White. 7000D AIRFLOW in Black and White. The system that will be going through this will be my main rig: Asus Zenith II Extreme ThreadRipper 3970X with HydroX XC9 8x 16GB Corsair Dominator Platinum RGB @ 3466Ghz nVidia RTX 3090 Founder's Edition with HydroX XG7 (I paid MSRP for this!) MP600 1TB (System Drive) MP600 1TB [This will be replaced with an MP600 Core 2TB] MP510 960GB [This will be replaced with an MP600 Core 2TB] Sabrent Rocket Q 2TB Seagate Ironwolf NAS 10TB I have lots of RGB in there (of course) but all that's likely going to be replaced. I've even got 4 LL140 RGB fans in there from way back just after the LLs actually launched ... and they are still going. Those things have seen some use. On of them even has an RGB cable that I had to cut and re-crimp because I snipped the wire. I've got Commander Pros, Lighting Node Pros and Fan Hubs that are around 4 years old or so ... still going. Of course there's gonna be a ton of Corsair in here because that's just how I roll. None of y'all are going to be surprised by that in the least.
    2 points
  3. I run the Pro on balanced not quiet and its still silent. I run my fans on silent though and you cannot hear anything. Cappelix looks amazing but the noise is terrible so had to go.
    2 points
  4. Since the problem is known, I would have expected the support to react faster. I have received the confirmation mail, but in my account it says that I do not have a support ticket. Apparently the service is as bad as the software they deliver. If the headphones don't work again on Tuesday, I will send them back. Unfortunately, I already have to give a bad rating because the description makes everyone fall into the trap, even if the headphones are actually good.
    2 points
  5. Oh my God, I stepped in the same shit. I hope the German support is faster than the forum. I was able to use the headset for 20 minutes. After so much research, I guess I chose the wrong manufacturer after all. With any other manufacturer, you can download the FW yourself, here it seems to be a company secret. I hope for a quick solution, otherwise they will go straight back to the dealer with a corresponding evaluation.
    2 points
  6. remember the PSU rating is always given just for the 12V rail(s). If you get a 850W, it's 850W on 12V. You'll still have on top of that the usual 25A at 5V (125W). So you don't really "need" to calculate anything, unless you're working with a massive case with 20 or 30 QL fans that will slam the 5V rail. as for the 12V power draw, fans will never reach their max rating unless you run them at full speed and block them all at once. The pump will be the only real power draw since it's constantly under load, but even then.. only at max speed will you see something close to 30W 🙂
    2 points
  7. Had some time to play around with HS80 and came up with this one.
    2 points
  8. pour l'insert de cintrage : https://www.docmicro.com/tuyauxliquides_tuyau-accessoire_Alphacool-Meche-Caoutchouc-pour-Tube-Rigide-10mm-Interne-1-Metre_13146.html Pour l'offset de 7mm : https://www.docmicro.com/embouts_embouts-accessoires-adaptateurs_EK-Water-Blocks-EK-Quantum-Torque-Rotary-Offset-7-Noir_15127.html Bitspower fait aussi des raccords de décalage qui s'accorderaient plus avec les raccords Corsair (Bitspower X-Cross), mais je n'en trouve pas en france en noir de la bonne taille (pas chercé longtemps non plus ^^)
    1 point
  9. That is the latest firmware for your headset unless you have another Slipstream capable device and wish to use the multipoint feature. If you are not being prompted for the 5.xx firmware that means you do not have any other multipoint capable devices and therefore you will not be prompted for the update.
    1 point
  10. Please Provide Firmware update to have the elite line of PUMP to spin lower than 2200 RPM. It is way too loud for normal pc usage. I have found that Platinum line of AIOs also had this issue and was fixed via firmware update - link below https://forum.corsair.com/v3/showthread.php?t=182257&highlight=corsair+platinum+pump&page=3 As a reference H150I Pro RGB (Asetek pump) which I also own have quiet profile of 1100 RPM which is silent. thank you.
    1 point
  11. Ok muchas gracias, lo dejaré entonces como en la segunda foto, con las mangueras arriba. Un saludo!
    1 point
  12. How many total fans do you have in that case? You really can't put enough fans in there to require a Commander Core and 2 Commander Pros. Heck, we've even managed to get a fully loaded 1000D with 32 fans all controlled by a single Commander Pro.
    1 point
  13. @c-attackIt's not at the top anymore, but it's still in the footer. https://help.corsair.com
    1 point
  14. Now that it's getting cooler, how are you adjusting your battlestation accordingly? Are you adding a fall touch? Show your desk, setup, fan orientation, room setups etc. with that extra pumpkin spice touch?
    1 point
  15. takes a breather... "CORSAIR MP600 PRO XT HX Gen4 PCIe x4 NVMe M.2 SSD" ... That long name will certainly trigger a long haired hardware youtuber 😛
    1 point
  16. 1 point
  17. You won't be able to do the auto-detect on the Commander Pro - even if you can have multiple fan types (dunno).
    1 point
  18. Danke euch beiden für die schnelle Hilfe
    1 point
  19. Hola, Confirma por favor que el kit especifico aparezca en el QVL para la placa: https://www.asus.com/us/Motherboards-Components/Motherboards/TUF-Gaming/TUF-GAMING-B550-PLUS-WI-FI/HelpDesk_CPU/ Si se puede, usa un solo modulo en cualquier puerto disponible y trata de actualizar el bios. -Art
    1 point
  20. You need a G1/4 male to male extender. If you simply must have the valve pointing a particular way, get a G1/4 male to male rotary extender. Corsair don't carry the fitting you need but since Bkyski is the OEM supplier to Corsair you can match your Corsair fittings with one from Bykski although other companies such as EK do make them as well.
    1 point
  21. Yes, instead of showing up in CUE with the AIO Pump picture, it will display like a Commander Pro showing the controller. Everything else works the same. 6 PWM headers. 6 RGB headers. Too bad only 1 temp sensor, but then you may not need it. You might have to tell us more about what your looking for in the Hardware Lighting set-up. Using it or any other controller won't change the end result. The HW lighting is 1 set programming for each effect, so different fan types with different LED counts look different under the same effect. Some things like Rainbow Wave are nothing like their software version. No cure for that presently.
    1 point
  22. Thanks! It's not perfect but not bad for a second build and first hardloop attempt. Not sure if / when I will worry about the soft tube but I am already considering some changes. Considering moving the distro plate / pump to the MoBo tray and doing a more traditional intake fans / radiator front and exhaust fans radiator top. Also possibly push / pull on the top. So if I decide to do that I will try and fix the tubing at the same time. I did add some filter material to the back of the case since it functions as an intake with no filter icluded at all. The door I was complaining about.....I didn't realize until towards the end of building that it came off, duh.... Some pictures attached. The computer on the right is similar spec (MSI z490 - 10th gen i7) and is complete except I haven't found a GPU for it yet. 🥺
    1 point
  23. On almost all the controllers the LEDs work in series, so a bad LED early in the chain will typically cause 1) everything after to go dark or 2) irritating flicker. If you are experiencing this, try each fan one at a time in the #1 slot on the RGB Lighting Hub to isolate the bad one. When the chain goes dark, it's pretty easy to pick the right one to start with. Flicker can be harder to pinpoint. Series circuit rules are still in place, so if you pull the #2 fan, 3-6 should go out and only #1 will light up. xx71 is the single LL120 black fan package. xx72 is the 3 pack of black LL120. These are identical and can be used in any order or configuration. The only difference is the 3 pack includes a Lighting Node Pro RGB controller and another RGB Lighting Hub for 5v power. With a Commander Pro + RGB Hub already, you won't use the additional hardware. However, if the price difference is close between 3 singles and the triple pack, always get the triple. The extra hardware is often of use later down the line or as an immediate quick fix replacement.
    1 point
  24. That makes it sound like there might be some kind of interference happening, which would be odd. Is your WiFi connection 2.4Ghz? Can you switch to wired to see if it changes anything?
    1 point
  25. Thank you, I appreciate it. But I can live with that. I mean the mic quality is really good and just noticed a little bit of hiss and thought maybe it could be lowered a little bit with future updates, but if not I'm still fine with it. I mean, it is still the best wireless headset mic with the one from virtuoso. The hiss also got better now.
    1 point
  26. Sorry to hear you're experiencing this issue. I've created a ticket for you, so our support can further look into this and provide assistance.
    1 point
  27. Schwer zu sagen, ob es normal ist, oder ein Problem. Wenn möglich, teste das Headset an einem anderen Rechner. Wenn es weiterhin auftritt, melde dich bitte via http://help.corsair.com/ (Klicke im Menü auf "KONTAKT") direkt bei uns, damit wir dir bei der Lösung weiterhelfen können.
    1 point
  28. Yes, exactly. Alternatively, you can use a powered PWM hub but you shouldn't need to go that route with 9 fans. Who is "they"? You can put LL's on the Commander Core but you can't mix the fans (at least, not right now). But even with splitters, you have too many fans for the power delivery on the Commander Core to handle. So you'd need to put at least some of them on a fan hub, which the Commander Core won't control. That's correct. You can make your own or get them from PirateDog Tech (https://piratedog.tech). These are pretty standard PWM splitters. Any PWM splitters will work.
    1 point
  29. The SATA power for the Commander Pro is utilized by the fan controller, RGB, and the USB connection of the Commander Pro device itself. The two additional USBs on the Commander Pro are purely USB passthroughs and are not powered by the Commander Pro.
    1 point
  30. Hello, in my virtuoso XT the bluetooth turn off After 10 minutes when i use it with my smartphone, Can you tell me how to fix this problem. Thank's for your help.
    1 point
  31. If you plug the USB directly into the internal USB 2.0 header on the motherboard instead of the Commander Pro and it gets detected your issue is most likely due to the limited power delivery of the internal USB 2.0 headers on AMD motherboards. The solution would be to utilize a high quality internal USB hub that gets supplemental power directly from your PSU.
    1 point
  32. Hi, I purchased the K65 Mini RGB today. I would like to remap my caps lock key to act as FN. This is something you're able to do on both the HyperX Alloy Origins 60 with software, and on the Ducky One 2 Mini using the switches at the back of the keyboard. I already set up FN + WASD to serve as arrow keys. Remapping caps to fn would allow me to use the arrow keys with one hand. However, I seem unable to do so through iCue. Is this even possible? If so, how do you do it? I can't manage to do it through both Keyboard and Keystroke assignment types under key assignment.
    1 point
  33. If you add 5v strips later, you will be able to connect them directly to the unused Commander Pro RGB channel #2. You won't need the Lighting Node Pro at all and strips don't need a RGB lighting hub. This is the prime reason for using the Commander Pro vs the Lighting Node Pro/Core in the initial set-up. Device order matters for those that want their lighting link effects that move (Visor and Color wave) to run a specific path through the case. I don't think you should worry about this and it makes more sense to arrange the fans in relation to their necessary controller (radiator fans need to be on Commander Core) and then their location in the case. So in your diagram above, a person who wants the visor pulse to travel from the bottom rear fan, to the side wall, up to the top, and back to the top rear would need to put the bottom fans 1-2-3 on the Commander Pro, then either a) side wall fans 4-5-6 on C-Pro or 1-2-3 on Com Core, then remaining top fans 1-2-3 on Com Core or 4-5-6 depending on the previous decision. All of that so you can run visor back and forth around the case. In your particular instance, it might not be such an issue but for some people this means swapping in/out different controllers in order to achieve this one effect. You have to really, really want to run the visor pattern 1 <-> 9 and specifically for the O11 it interferes with the more natural top/bottom row as a lighting group presentation. Preset effects cannot be altered or their timing adjusted beyond slow/medium/fast (and those are relative to each effect). So if you want to manually program a custom moving effect (wave, ripple, etc.), then it would look something like what you wrote with a given set programmed with a "pause" (no effect) for a specific length of time until the previous effect finishes. It's mostly a math problem with a "16 LED fan" moving at 8 LED/sec and a tail of 48 LEDs, needing 12 seconds to complete it's pattern or properly an 8 second delay to maintain the 3 fan tail as it transitions from one controller to the next. It can be done, does require some thought, planning, and experimentation to get the timing down. However, there are a lot of complaints in these forums that it's too much work to open the CUE app and click one item to change a profile, setting, or other operational state. That is not someone who is going to be doing math calculations to set up their lighting patterns. Even if you are interested and compelled, it is not something you want to jump into on the first day. It takes some time to figure out the programming rules and behaviors. This is one of several reasons why I advocate for using the 3x3 programming in the O11. It will allow you to use presets to simulate full case movement and the timing will take care of itself. So for color wave that is really just a series of random primary RGB value color waves, you use the 3x3 and not the lighting link. There will be a color wave on every fan simultaneously. With 6 possible colors and 9 fans, the concept of sequential 1-9 order doesn't really matter unless you are dying to watch Cyan ring #2 pass through the 9 fans among all the other color rings. Visor is the only effect where the sequence matters and it's a rather frantic effect. Someone with QL fans is likely to enjoy all the special ring effects quite a bit more.
    1 point
  34. Correct and specifically for the 3x3 arrangement in the O11, it is really easy to quickly set up 3 instances of infinity, gate, ping, pong, or whatever that will give the same appearance of moving around the case. They will auto-sync if you swap to another profile and back to reset the timing clock. That's not so easy with an asymmetrical fan arrangement like you find in most cases. Here is another thread where the Lighting Link device order is spelled out. Note the LNCore and LNPro devices fire before Commander Pro or Core. So if you use either LNC or LNP, those 3/6 fans will go before the 3 on Commander Core (radiator). So now we are getting into cross-wiring RGB fans to one controller and PWM to another, while doing the opposite for another set of 3, all to make color wave run 1-9. It's tricky business with a cost when you have high fan counts. I used to go to great length to make this work in an asymmetrical case, pairing 2 fans to act as one to balance numbers. I just don't see the reason to do this in the O11. 3 independent color waves (or even just 2) looks pretty much like a 1-9. It's more fun to do 3x3 with the other effects. https://forum.corsair.com/forums/topic/170742-sequencing-rgb-effects/?tab=comments#comment-990648 All independent physical devices will show up in CUE as a separate entry in the device page. The one exception is the RGB Lighting Hub that supplies 5v current for fans on the Commander Pro and Lighting Node Pro. On Core devices, that 'RGB Hub' is incorporated into the body of the lighting controller making it one smaller piece than the two separates. Of course, no free lunch so the tradeoff is you only get 1 channel and all Core devices are for fans only. That brings up around to the LNP vs Commander Pro decision. You are correct and with 4+ QL fans on 1 channel of a LNP, the other lighting channel is disabled. It is an older controller from back when 12 LEDs was the high count. Now it's 34 per fan. This makes the decision as to whether to use the Commander Pro + RGB Hub vs Lighting Node Core or LNP a bit more meaningful. This is likely better decided now. Lighting effects are saved to profiles with device specific identifiers. I have a LNC with 6 QL and add another LNC so I can add 3 more, it doesn't duplicate the first. It treats it as a new controller (LNC #2). However, this also means lighting effects are saved this way too so your controllers do not have to be duplicates. If you create a bunch of profiles on the LNC or LNP, then 6 months down the line realize you need the 2nd lighting channel for strips and swap in a Commander Pro, all of your fans on the Commander Pro will be blank. The lighting effects will not transfer from the old device different to the new. Whether this is of consequence depends on how you use it. Some people just write over the top of one profile with whatever lighting effect strikes their fancy on that day. I create dozens of different themed effects and use them throughout the year. Adding a new controller means re-programming each one. I think you are going to want 5v D-RGB strips. It's kind of hard to go back 12v after having so many control over digital. There are also a couple of external Corsair products like the LS100 (big frosted external strips) and LT100 (towers with strips for ambient lighting) that have their own controller/power and would not fall into the trap above. Corsair internal strips are 5v and connect to either a Commander Pro or Lighting Node Pro. If you do go the 12v route and connect them to the MB, the Asus plugin brings lighting control over that into CUE. It requires you have Armory Crate installed and CUE is accessing them through the AC program. There are no miracles here and you can't make limited MB LEDs do overly elaborate things.
    1 point
  35. From the album: XV

    1 point
  36. 1 point
  37. 1 point
  38. Uhm, this IS a Corsair support forum, right? So is there any supporter reading this?
    1 point
  39. So glad you got your issue solved, I know how frustrating it is! You would at least think @Corsair would see this thread and throw some swag my way for helping solve several peoples problems!
    1 point
  40. Dear support, I'd like to pick this thread up again since I'm facing the same issue. I recently got me two K100 keyboards. Used to have K70's in use. I want to use the on-the-fly macro recording (actually that was the main reason for buying the K100's). It generally works as expected, but recording a macro ALWAYS stores it in the hardware profile. It does not matter whether the iCUE software is running or not. I have the iCUE window open (so yes, the software is running for sure). No macros are currently existing in iCUE mode (and there also are none in hardware mode): Now I switch the Control Wheel to "red mode", press the button to record a macro, select G6, press "a" two times and G6 again. But the macro is recorded to Hardware Key Assignments and shows up there: That is not the expected behavior which is: Control Wheel Macros - In software mode, it will add the macro to your current software profile. In hardware mode, it will add them to the current hardware mode profile Instead all macros I record using the wheel go to hardware mode, no matter whether iCUE is running at recording time or not. Please help and tell me what I'm doing wrong. Thanks! Chris Edit: I'm using the latest V4 version which currently is v.4.13.226
    1 point
  41. Evening all, just thought I’d drop some pics of my all Corsair build that I recently completed. Specs are as follows:- AMD 5900x Nvidia 3090fe ASUS X570 Dark Hero 32gb of Corsair 3600mhz Vengeance RGB Pro ram 1tb Sabrent rocket 4 NVME Corsair 5000D airflow case (slightly modded to fit the rad in the roof recess) Corsair H150i capellix Corsair RM850X 10x Corsair QL120 fans Cablemod modmesh pro kit + 12-pin gpu cable
    1 point
  42. Same happen to me with Sabre Pro RGB Championship, i decided returned for malfuction. Hope more lucky to you.
    1 point
  43. 1 point
  44. 1 point
  45. Hey man thanks for this, it ended up doing the trick for me. I suspected a power issue as well as the headset was left directly under the air stream of my A/C all night which probably over-discharged the battery. Stopping the blinking for 2min let it charge enough to start working again. Imo this is probably the issue for everyone on here, dunno why support is linking them to pages about re-pairing and updating firmware when the headset doesn't even have power and isn't able to connect to iCUE at all to do said updates and to pair...
    1 point
  46. I have this issue with Corsair Virtuoso. Both wireless,usb and 3.5mm. Even tested with connecting the 3.5mm through ST100. Seems to only happen with custom EQ when im using a high bass setting and also with bass boost eq preset. The sound will go suddenly loud for a short time and then normal and then loud again. Its not an extreme loudness but it is annoying. Also does not happen if i terminate icue. But then nothing else works properly either with my rgb or fan settings. Its not a constant problem some days it works just fine. I also tried installing icue 4 but no difference. Dont know if its icue or the headset itself that is causing the issue anyone have an idea of what more i can try?
    1 point
  47. Ordered a prebuilt from a UK System Integrator despite building my own PC's for 15 years in order to get a GPU and closer to MSRP and much quicker. Its a Lian Li O11 Dynamic Midi Tower White, with a Ryzen 7 5800x, Asus Strix Gaming F x570 motherboard, 4x 8gb sticks of Corsair Vengeance RGB Pro 3200mhz DDR4, Asus Strix RTX 3090 OC, 512GB Samsung 980 Pro NVME (Gen4) for OS, 2TB Samsung 970 Evo NVME (Gen 3) for Games Storage and I will transfer from current build 2x 3TB Toshiba 7200rpm HDD's for Media. As this SI doesn't have all the parts I want I will order the following items separately. 10x Corsair Black Framed QL120 RGB fans, an iCUE Commander Pro and an NZXT Kraken Z73. Sorry Corsair, but I fell in love with the Kraken Z73 so no Corsair AIO for me this time with this build. So the plan is basically this aesthetically speaking though some parts differ from the build in the video: [ame] [/ame] There is room in this case to run the 360mm Radiator in Push/Pull if I decide to put the Rad in the Side mounting point to the right of the Mobo in that Vid. So my 10x QL120's would be all the visible fans in the case like the VID (10th Fan as another exhaust over IO Shield) but I would also have the 3x NZXT Radiator fans hidden on the backside of the Radiator. So the question is how to wire all that up. Do the Nodes that come with the 3x 3Packs of QL120's combined with the CoPro cover the RGB connections for the 10 QL120's? Can the CoPro in combination with some PWN Y splitters or a seperate PWM Controller cover the 13 fans? Ideally I want to be able to control all 6 fans on the Radiator (ie. 3x QL120's and 3x NZXT Rad fans) with the iCUE or NZXT Control software such that they are based off of the Water temperature and not the CPU or Core Package temps. Back in the day with my Corsair H110GT cooling a 6700K, no matter what fan curve I set the fans would ramp up and down even in google chrome on a media heavy web page. It was only when I realised that it should actually be based off of the AIO Water temp which is much more stable, did my fan ramping issue get solved. I would like to maintain that functionality with this new PC. WHats the best way to achieve that? All 6 rad fans connected to CoPro headers and the other 7 case fans on a separate Fan controller. Or those 7 case fans connected to the CoPro (with 1 Y splitter) and the 6 Rad fans on a separate controller connected to where it needs to be for the NZXT AIO Control software to manage the rad fans? On my old build I also used Speedfan to base the Case Intake and Exhaust fans speeds off my GPU temps. ie My GPU fan profile was set not to even spin up till the card hit 50ºc. Case Intake and Exhaust were set in Speed fan to minimum RPM. When gaming though, once the GPU temp went above 50ºc, I set a curve in Speedfan to increase the RPM's of the Case Intakes and Exhaust. Is this possible to replicate in iCUE? Is it possible to shut down iCUE without losing fan control or shut down the RGB component of it at least. Apparently iCUE can flood the USB sub system with 'interrupts' as it controls the RGB which can affect VR negatively. So when I VR game I may need to shut off the RGB control. Other users in my household on my home network will also be VR gaming on this PC remotely as well as 2D Pancake gaming via Steam In-Home Streaming/Remote Play without direct access to the PC. Ideally when they use this PC remotely and wake it up WOL with a 'magic packet', I wonder is it possible to set up a scripted or scheduled task or something like that, that would shut off RGB when they connect and re-enable it when they disconnect. Not sure if that kind of thing is possible though.
    1 point
  48. I signed up specifically for this forum to ask a question about why my new H150i pump is so loud, even in quiet mode, and stumbled across this thread. It's too loud, Corsair! This isn't bubble noises or a hardware fault, it's simply the sound of the pump. I have 7 fans in my chassis running on quiet, and all I can hear is the pump which is also set to quiet. It's extremely distracting. Is there likely to be a firmware update to fix this, or should I swap it for something else?
    1 point
  49. Doesn't really help you but I stumbled on your post after having issues with my K70 Lux RGB. I've had it for 4 years and it's been working fine but one day my keyboard only shows Red now. I've since reinstalled iCUE but still stuck on Red. I suspect it's a keyboard firmware issue but it contacting support doesn't sound promising from your posts. Any luck sorting it out?
    1 point
×
×
  • Create New...