trendyideology

Gone round and round with support on this issue before, on multiple computers, clean installs, the whole cornucopia of troubleshooting. Please, just add a "Save" button. Please. Since you guys can't figure out how to make the application properly save anytime a change is made, just give me a manual save button so I don't have to choose between constantly exporting/reimporting, or losing work anytime the application dies/crashes, or my computer reboots or crashes. We're not talking "I just did a thing 5 seconds ago and then I crash" - we're talking "My computers and iCUE have been running for days, and now anything new I do will be lost no matter what, 100% of the time, because iCUE's internal process that saves changes has long since gone to sleep never to awaken again until freshly launched"

This is a direct quote from a support ticket I had opened with Corsair a few months ago. If your repair function did the same things or comparable things, or just got the job done regardless of similarity, there'd be no issue, and support would recommend using the built in repair function rather than a third party tool. The feedback I'm giving you is "Fix the install process, update process, and repair process, so that they work properly without third party tools, including resolving whatever underlying issues result in needing to do reinstalls/clean reinstalls/etc, in the first place". I'm not giving you guys a hard time about fixing stuff with a stopwatch that's started tracking "the time since iCUE4 launched", expecting that iCUE4 be magically perfect overnight - I'm giving you guys a hard time because there's been a stopwatch running for years now as all these persistent issues have plagued users across countless releases/updates/iterations/etc. ------------------------- Lemme try a different way here. The Corsair iCUE installer and application, as it gets originally installed on your system, and as it lives on your system through normal day to day use, is doing something on your computer, to your computer, that's resulting in the need for clean installations to ever be performed. Some registry key that's now incompatible with the current version? Some file you guys forgot about that now interferes with normal application functionality after an update? A configuration file that is version specific that's now causing compatibility issues? -- I don't know. I'm not a software developer. My point here is just that it should really be a priority to track down "the thing that leads to a clean install being necessary in the first place". -- If a clean install ever fixes anyone's issues, something logically happened there, right? Something existed that was "a thing we didn't think of that caused an issue with the application working as intended" and part of a clean install removes the thing, allowing for a fresh install to return the user to the expected "working as intended" state. Right? So find "the thing" and make it so "the thing" doesn't happen anymore. I realize I'm oversimplifying it, but I think the core of what I'm saying is pretty straight forward - the overwhelming majority of software I use in my professional life, and in my personal life, behaves this way. If there's a thing like this, they find it, fix it, and everyone moves on with their day. They don't carry forward and endless policy of "well, whatever, if things get totally messed up, we can always just have them do a clean install". Typically what's left behind by applications and uninstallers is things like registry entries, config files, and random other files/folders. It's honestly not that daunting of a task to have iCUE operate in such a way that it's only ever changing specific locations in the registry, writing data to specific directories, etc, and know/track all of those things, and then have the ability to nuke all of those entries through your own software/process should the need ever arise to do a totally clean installation. If Revo Uninstaller can do it, the repair function, and update function, can do it, too. But to my original point, it should never be necessary in the first place. And hey, I know you personally are just another human doing your job. And I'm sure you have good intentions. So don't take any of this as being aimed at you. This is aimed at Corsair in general as a company, and my hope is just that the spirit if what I'm trying to convey here eventually makes it to someone who's in a position to make some things happen and take things in a better direction than where I feel like we're at right now. I do appreciate you taking the time and effort to reply, even if it's your job. :)

You're sorta missing the point and the mark with your response here. 1) Make your software do it properly with a repair function - I was told to use a third party tool, by Corsair support. This should never really be a necessary step as an end user. 2) If you can't bundle it with the software, create a script or something yourselves that performs the function. 3) 1&2 shouldn't be necessary in the first place. You guys should be working very hard all these years to figure out why the way your software works/is installed/updates ever necessitates this step in the first place, and why a clean install is necessary in the first place. And then fixing that thing. From my outsider perspective, it seems like you guys have grown complacent with being able to throw countless variations of "just reinstall" "replace the hardware" "blame the profile" "ask the use to rebuild everything from scratch" "blame the macro" - at problems, and since users either have their issue resolved with these steps, or give up out of frustration, you just keep using these steps rather than fixing the issues causing these steps to be necessary in the first place. I'm assuming the reason internally for the lack of accountability on these points is because someone is looking at cost/benefit and concluding that X% of unhappy or inconvenienced users is an acceptable number, and so it doesn't make sense to spend more to address that volume of user's issues. TL;DR - My point was never that I thought it's an erroneous step, but that it should be a step that you guys should be visibly and publicly working on addressing so that it becomes an erroneous step. I'm really disappointed in the total lack of transparency and engagement. People just wanna know that their issues and concerns are actually being heard, understood, and that something is going on to address them. You say "We are listening" - But there's no follow-up there. You don't call out anything specific that's yet to really be acknowledged by staff in the thread and elaborate on the situation, or give us any indication of what kind of stuff has been taken back to the team to internally work on. Are you guys working on bringing back OSD? Are you guys working on support for the older hardware? Are you guys working on making iCUE3 and iCUE4 play nice together so people with order hardware and newer hardware can continue to use their older hardware's functionality while getting the perks of the newer software for their newer products? No one knows, because all we're getting is a single line saying "Yep, we hear you, we're working on it". And I'm really disappointed in the caliber of help I've received every time I've reached out to Corsair support. Based on my experiences with support so far, I'm going to go ahead and guess that there's virtually no internal processes to escalate an issue to higher technical tiers or the development team, no one actually reads or understands the debug logs at the T1/T2 level, and there's no interest in working with individual users to actually track down the source of any bugs/issues and then fix them, unless it's affecting a significantly large amount of users.

I wonder if Corsair is aware that countless products work through constant version updates without ever needing to do "clean reinstalls".

This man gets it. I opened a ticket for icue3 because it would basically "die" after running for days, and then any changes I'd made since last "clean exit" wouldn't be saved. They had me do 32 flavors of uninstalling, reinstalling, and even tried to get me to roll back to prior versions. I ask them "Ok, how do I migrate my existing macros to the old version since you arbitrarily versionstamp my profiles so they're not backwards compatible even though literally nothing has changed with macro functionality between most releases?" -- no answer. They said they'd look into it, and never even bothered coming back to me to say "Yeah, we know that's an issue and have no intention of fixing it, so sorry, but go pound sand" -- All they did was come back with another half baked idea for troubleshooting. Eventually they tried blaming my mouse as being defective hardware and started trying to troubleshoot that. I went around and around with them on this for weeks. Nevermind that I have 2 identical mice and both exhibited this issue, ditto for two similar keyboards (old and new version of the k95) It's absolutely the software being garbage, and their internal policy once again is more or less proven to be "blame literally anything except the software being garbage because we have no intention of actually fixing it" - just exhaust the customer with nonstop useless replies until they give up and you can close out your ticket due to lack of response. I don't need sensor logging. I don't need dashboards with graphs. I don't need background pictures. I don't need profile icons. I don't need 500 options related to RGB Who asked for "Scenes?" Who signed off on that? Fire that person. Who cares. What I DO need is to see what profile I'm swapping to with the profile swap button, except you removed the overlay so I could actually see what profile I'm on. What I DO need is to see what DPI I swapped to, except you removed the overlay so I could actually see what DPI I'm on. What I DO need is macros to work properly, send accurately, not hang up randomly, and SAVE when I make them, make changes, etc, so I don't lose work constantly or have to manually export the whole profile constantly just to be able to restore it from backups. Bottom line: Y'all're lucky you have extremely limited competition in this space. If Logitech and Razer hadn't managed to implement even worse UX than iCUE, which is an accomplishment in and of itself, I wouldn't put up with this nonsense. You guys seriously make some of the most baffling design decisions. I pray for humanity if the fact that I'm now forced to look at hieroglyphics for my macros is a result of focus groups telling you that people preferred seeing tiny hard to read icons versus being forced to read words in plain english. But would it have really killed you to give me an option to have the icue 3 style of just saying "Left Mouse Button Down" instead of "mouse emoji" "click emoji" "pressed button emoji" ? Props for having a flyout window for macros so I can view more lines at once. But -1000 points for making it impossible to edit the rest of the macro options from that window. There's just this huge blank area to the right, where all the other options could be... that you're doing nothing with... again ... why? While we're at it: The entirety of the "Recording" "General" and "Advanced" could be easily displayed when the window is full screen, rather than making me swap between tabs. You guys waste so much space in the UI for no real reason. Making me click around constantly to get where I need to go with no option to just show more at once. Are most of your users using high end gaming accessories in machines with 800x600 resolution or something?

Why? Was it because the feature was buggy and inconsistent and so you guys decided to scrap it going forward rather than invest resources on making it work correctly? Cause idk about anyone else but I'd gladly sacrifice all the unnecessary stuff like "scenes" to retain core functionality that's actually useful to me when I'm playing games. Why am I losing useful functionality and gaining cosmetics as a tradeoff with iCUE4 and who on earth authorized that?

I'll make this super short and sweet. Corsair breaks things in iCue every single release. The latest (that I'm impacted by) is this "unpressing held buttons" bug: https://forum.corsair.com/v3/showthread.php?t=200050 https://forum.corsair.com/forums/showthread.php?t=200090 Every single time I come to these forms, someone is quick to remind anyone who potentially needs to roll back their software version that profiles will not work if they made any changes to their profiles on the new version. It's been like this for a long time now. A few things: - The update process should be backing up profiles for users, this should not be a manually initiated end user process, especially since things breaking and profile incompatibility is a known situation by Corsair. - Updates shouldn't even be invalidating profiles - y'all aint doing anything special to the app each time that actually makes profiles incompatible, you're just stamping profile files with a version number and telling the app to not work with anything past [currentinstall] stamps. - If you're gonna insist on that, you should have a way to bypass it within the app.

Same. I was on the line with Amazon to send back my brand new k95 because the googled description of the issue made it sounds like key switch "chattering" or "contact bouncing" - which for all I know that's something the current iCUE is somehow screwing with. For such robust software it sure consistently fails to deliver on the basics.

- Added simulated "chattering" / "contact bouncing"

Same issue as OP. It's absolutely not anything to do with profiles, actions, etc. It's their software and it's changing how "chattering" / "contact bouncing" is being processed, or somehow through a bug simulating its own. Half of my number keys, and F# keys, experience this issue, only while iCUE is running, and only on the most recent version. Rolling back fixes it. I should not need to do this kinda troubleshooting/testing ...

Alternatively export your profile, edit the XML file, and find the macro in question (and set the delay to something conspicuous that's easy to ctrl-f for) and try to manually set the delay to 300,000 ms and then import the profile back and see if it works. Imports might have some kinda sanity check/validation/whatever going on though, so I have no clue if this would actually work. Option 1 is probably your best bet.

Recorded actions: Left mouse button press pause 25 Left mouse button release Action trigger: while pressed Action repeat: repeat constantly Repeat delay: 25-50 ms (this has also been static with no change in behavior for 25/50 ms) Same exact type of macro works flawlessly with no issues from: AHK, Logitech mouse/software. As title says, mouse left click appears to stay in a "down" state frequently when using a rapidfire click macro. I can clear the issue by manually left clicking. I've tried adding additional "left mouse button release" events to the start and end of the macro and it does not resolve the issue. Since it happens to anything I assign the action to (M1, M2, G1-12, etc) I'm assuming it has nothing to do with the mouse itself. Any help would be greatly appreciated. (This was originally posted to "Corsair Product Discussion > Keyboards and Mice" and retrospectively that was probably not the most appropriate place to post it given that the problem is likely with the iCUE software and not the mouse itself, so I'm reposting it here since I can't move the thread)