Jump to content

Daggz

Members
  • Posts

    22
  • Joined

Reputation

11 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. As another addition, you wrote "Lightning Node Core" - Which I've never mentioned. I don't have any Core controllers in this system, it's a Node PRO. You didn't get anything right in this thread buddy. I suggest you spend your time on something more useful as you weren't of any use at all here and never even understood what the issue was or what components were involved. Incredible.
  2. So like I said, it's not a hardware issue and I'm glad I didn't listen to your poor advice and spent 110€ on a new one. You clearly don't understand how to read an issue from a support perspective, you asked no questions to get a better understanding of the problem and your advice was simply incorrect and would've costed me much more money than fixing the software issues which was the root cause of this. The problem is the sound modules in iCUE5, when I connect my Corsair Void PRO RGB SE headset to the wired USB charging cable, the Node Pro was found by iCUE again and lit up as it should. So the issues are in the software or the coding of the audio modules or equalizer used to modify the sound in Windows. You could've learned these "revelations" by simply asking a question before judging both my persona and my issues as "unworthy" of your time or efforts. It may be a community user forum, but if this is the Corsair community and their level of engagement with other users, I'm glad I've never had this displeasure in a point of contact of the Corsair Community members, previously. I would suggest you get off your high horse and start treating the other members on this forum with an ounce of respect, before you proceed to ******** all over us with your arrogant and incredibly incorrect "advice" or suggestions. You clearly don't know what you're talking about and you seem to be rather fixated on elevating your social status on this forum rather than trying to provide actual help and support to other members. That's just so incredibly toxic and I sincerely hope you can see this and change how you engage with other people seeking help. They may be frustrated by their issues, and that's their right to be so. If you don't want to or can't help, don't speak at all. You really didn't bring anything of value to this conversation nor into solving the issue, whatsoever. At least now we know, you were wrong and your advice isn't anything to go by. Because you just want to be right, you don't want to help. You're just like a Redditor. Maybe take a walk buddy. Bye.
  3. Seeing how there's multiple other users on these forums with the exact same issue I find it hard to believe we're all having hardware problems. The issues were introduced immediately after an iCUE update to iCUE 4 and have only gotten worse with every update, I still find it hard to believe it's a hardware issue. The reason is; the devices connected to the Node that's malfunctioning, are off-brand (jmmods accessories) I believe this to be a coding issue or software conflict. If I plug the other devices from the other Node into the one I'm having issues with, they're found instantly, always. It's easy to jump to conclusions and say "yeah hardware issue, replace it" without asking questions to further understand the issue. I'm just going to remove iCUE from my system and go for SignalRGB. Their community are much friendlier and actually helpful instead of patronizing and gaslighting their fellow enthusiasts. And thanks for explaining how a wired connection works, having worked in IT Support for 5 years I really had no clue how these things work....... Yes, I'm sarcastic. Again, thanks for nothing.
  4. So I just rebooted a third time after having the system on for a few hours and playing a few games. Now the Node is found in iCUE again and the accessories connected to it, is showing the proper profile colours instead of the default rainbow. So, as I've said, it works. It's just not found by iCUE on every boot. That's the issue. Not the hardware. I've seen others having similar issues in forum posts here (and they received proper replies from people who actually wanted to help and not just ******** all over that person in order to make them feel good about themselves) so it's not just a "me-issue". There's more people out there struggling with this. I've opened a support ticket with Corsair and am awaiting a reply but simply opening a ticket requires one to open up the case and take note and/or photos of the Part number and serial number of the specific device acting up. Something I'm pretty sick of doing already at this point and why I tried asking for help here first instead.
  5. Seeing as the lights still turn work but are set to defaul Rainbow mode on this specific Node I'm having issues with, indicates it does receive power and thus is working but simply not found by iCUE. So it's not a broken Node, it's either a USB issue or an iCUE issue. All other USB devices work just fine on whatever port or header I use, so it's absolutely not a hardware issue.
  6. 1. No, it's not. Because it works on some boots, just fine. It's like it's building up errors until it simply won't respond until I replug the connection multiple times, on different headers. I have tried a direct connection as well already so it's not a foolish assumption, it's the result of my troubleshooting. Had there been a hardware issue it wouldn't had shown any lights at all and wouldn't be found at any time at all. 2. It's not the position of the cables, they are static in their placement and don't move around when the system is sitting on my desk. 3. That's your best suggestion so far but far from a solution. It seems the people on this forum isn't interested in understanding the issue or providing any concrete suggestions outside of willingly misinterpreting or ignoring some of the parameters, only to provide a smug answer of "you're dumb, do this". Thanks for nothing.
  7. It seems you're not reading my posts. It does work, sometimes. Some boots it works, others it doesn't. I don't have to plug it in directly to a motherboard header as it's been working for 3 years in the Commander Pro. It does still work but every 5-10 days I have to unplug it and fiddle around with the connection to make it work again. Please don't comment if you aren't going to read the posts to get an understanding of the issue. You're just muddying the waters here.
  8. As I wrote in my initial post, that's not an option. They are already populated by the NZXT Internal USB hub and the Commander Pro. I have 2 Node Pro's and the other one works flawlessly in the Commander, I've swapped ports on them several times to no success. The RMA period is long past, I built this system 4 years ago and this was never an issue until the last year or so. I need a solution to this issue, replacing the hardware isn't a solution I'm afraid and I refuse to spend further money on something which has been broken by either Microsoft or Corsairs iCUE updates.
  9. So I just rebooted once, no success. Shut down and booted again, still the same issue. I shouldn't have to remove 6 screws and 3 panels, fiddle around with connections for 10-15 minutes, on every single boot, to have my RGB work as intended. Could any Corsair representative, PLEASE help me with this before I do something stupid?
  10. Would also like to add that I tried connecting the Lightning Node Pro to the NZXT Internal USB hub as well but to no avail either. It would either not find it or the Node was in a "non-functional mode" which prevented the connection to take place I presume. Booted today and the Node is not found again. This is an every-day issue and I'm desperate for a solution. I don't have the time to deal with these reocurring issues on a daily basis. It's ridiculous.
  11. As title says, Lightning Node Pro disappears from iCUE on some boots and is only found again when rebooting one or several times and/or if I open up the case and plug out the device and back in again 5-10 times, swapping ports back and forth until it pops up in iCUE again. It's connected to a Commander Pro with a secondary Lightning Node Pro connected to that as well. The other Node works flawlessly, at all times. Are the Commander Pro's that low quality that their USB ports are malfunctioning on 3 separate Commanders? Because I've tried that. I've also tried going through an NZXT Internal USB hub as well, to no avail. Plugging it directly to a motherboard header is NOT an option as those are already populated by other devices (the Commander Pro being one of them, which shouldn't be an issue, right?) This has been an issue since iCUE 4 and has become much more predominent in the last few months with iCUE 5 and the constant updates every 4-5 days. (SUPER ANNOYING UPDATE FREQUENCY!!) I've tried a bunch of things, to the point where I don't even remember everything and it's consumed about 50 hours of my time by now and it's really pissing me off. Every time I think I've resolved the issue, it comes back in a few days. Everything is up to date, everything has worked flawlessly before, but sometime during these constant updates it would seem as if either Microsoft or Corsair broke something or introduced a conflict of some sorts. I'm really sick of this and want a permanent solution to the problem. Does anyone, have any clue what to do to get rid of this nuisance? I'm at the point where I'm almost willing to throw out every piece of Corsair from the system and rebuild it. Almost. Sadly I invested in as many Corsair products as I could at the time of building this system, because Corsair seemed to have the most stable and functional RGB software but somewhere along the road this has changed. What can I do outside of ripping everything out and throwing it in a bin?
  12. Hi there, I'm having issues updating my ST-100 RGB headset stand. I haven't been able to update it for about 6 months or so now and I haven't been able to find a solution for it. My VOID PRO RGB Wireless has started to notify me with "Mic off" at random times despite the mic being off all the time, folded up in the "off" position. I believe this might be related to the ST-100 not updating as the wireless dongle is attached to the top USB port on it. Is there any solution to this issue? It's very frustrating to hear "Mic off" every 15 minutes when playing competitive FPS games as it distracts me and washes away other sounds such as footsteps and shots fired in the game, which thus, decreases my awareness in game and gets me killed. Please, any fix to this? Thanks in advance, Best Regards Daggz
  13. Also having issues updating my ST-100 RGB headset stand. I haven't been able to update it for about 6 months or so now and I haven't been able to find a solution for it. My VOID PRO RGB Wireless has started to notify me with "Mic off" at random times despite the mic being off all the time, folded up in the "off" position. I believe this might be related to the ST-100 not updating as the wireless dongle is attached to the top USB port on it. Could we get any resolution to this issue? It's very frustrating to hear "Mic off" every 15 minutes when playing competitive FPS games as it distracts me and washes away other sounds such as footsteps and shots fired in the game, which thus, decreases my performance in game and gets me killed. Please, any fix to this? Best Regards Daggz
×
×
  • Create New...