Jump to content

Metazolid

Members
  • Posts

    24
  • Joined

Reputation

10 Good
  1. I doubt any super glue will have enough strength to hold the two pieces together, since you're applying vertical force on a vertical weakpoint. I suggest to either replace the wheel, or drill a hole into the center in which you can then set a new shaft. This will give it enough strength to last longer than gluing the piece back in place.
  2. See if imitating the key on hold does the trick for you, as well as select Remap, instead of making a normal macro.
  3. I have a Scimitar as well where the Mousewheel click has a mind on its own. What I've read so far that kinda worked was tilting the mouse and rapidly clicking/scrolling in order to remove any dust particles that might got stuck in there. Out of experience I can tell you that cat hairs tend to get into that section every now and then.
  4. See if you can force a driver update and fix the issue that way.
  5. It's a profile switch key, in case you have several profiles, you can easily switch between them with this button.
  6. To summarize the solutions offered to solve the shutdown/reboot bug The instruction at 0x000000005FC4030B reference memory at 0x000000003ED0860. The memory could not be read. It's common for users with Xonar Soundcards, installing a 3rd party driver could fix the issue (http://maxedtech.com/asus-xonar-unified-drivers/) If it doesn't, go to your boot driver C:\Windows\SysWOW64, here you'll find a HsMgr.exe file. Hsmgr.exe is a driver component for Asus, Auzentech, Creative and other sound cards. If you run it as Admin, the error will disappear. Do this by right clicking it > Properties > Compatibility > Change settings for all users > Run this program as an administrator. Now just restart your system. The error won't be there anymore the next time you reboot or shut it down.
  7. Makes sense, thanks for the summary. Whenever I find an issue like this where I have the opportunity to tinker with I take the chances I get. It's not immedeatly apparent how a newer .cueprofile can be edited to make it compatible with an older version, but I doubt it's impossible. I have 150-200 macros across a dozen profiles and at least as many lightning effects with varying complexity, just creating them from scratch isn't really an option :o: I'll probably stay on 3.31 and see how I can fix the shutdown error I get because iCue is beefing with Xonar for some odd reason. It outweights the pros even if I'd create a tool to successfully migrate a newer iCue profile to an older version.
  8. I actually did, for some reason I thought they wouldn't cause any problems. Once I've deleted the saved settings, old iCue versions worked as intended. Unfortunately my profiles which make no use of any new features, are not backwards compatible so I'll either have to tinker around with the files, or create them from scratch. Thanks though.
  9. No problem You should share the video in here, just in case others find themself in a similar situation and need a solution :)
  10. Honestly I dont have a real clue. Unless you have a rather recent Keyboard which has hardware lighting and hardware actions built in and available as options, I don't have a conclusive suggestion for you. On my K95 I save my main profile on the M1 and that seems to work but then again, I have messed with another profile that I have saved on M1 instead and my keyboard went blank without iCue, giving me inconclusive results about which and how a profile is stored on the device.
  11. I've been having shutdown/reboot issues (already mentioned by someone else here) and since I do have a Xonar Soundcard installed I went on and got the iCue version 3.18.77 directly off of Corsairs website. Installed it and after every start it didn't detect any devices (even after re-plugging them) and just shut down, without any crash messages etc. To make sure it's not just a single version issue, I've downloaded and installed a variety of versions, all with the same results. 3.11.114 3.12.118 3.13.94 3.14.100 3.14.104 3.15.101 3.16.56 3.17.94 3.18.77 Interestingly enough, installing 3.28.77, which is the second most recent version from just a few months ago, won't even start. The fans connected to my Commander Pro ramp up for a second after installation but that's about it. The only version that works is 3.31.81 but has as already mentioned caused issues shutting down and/or rebooting my PC. What causes all previous versions of iCue to just not function at all and how can I fix this?
  12. Happens on my Platinum Rapidfire and K95 Vengeance as well, the springs within the switches resonate and create the common pling sound which varies from model to model and manufacturer to manufacturer but is generally present in mechanical keyboards. It can also be heard by tapping on the metal plate above the arrow keys. If it's too extreme I suggest you to either get used to, or RMA it. I fixed my K95 by adding dampener mats on the inside, as well as lightly lubricate the springs. It's a time consuming process that's not recommended for everyone, but an option.
  13. I made a profile based on the classic Maliwan Style from Borderlands 1 :D: I'm looking at my keyboard every now and then when furiously typing which is why I can't stand whacky and flashy animations. This profile has 4 very slow moving sections, taking 99.9 seconds from start to finish. It's therefore as slow as it can get and not noticeable when typing, though a nice and in some way refreshing/not boring animation to look at. It also has lots of small sections which briefly and non-intrusively light up in an elemental damage effect, not taking up more than 2-4 individual keys for a bit of character. They're neatly organized, have inidividual placeholder layers and one global placeholder to show which keys are animated. The profile supports K95 Vengeance (and therefore probably every keyboard that's smaller) K95 RGB Platinum light bar Vengeance RGB RAM (4 modules) Corsair Scimitar Seems to be onboard storage friendly for the K95 Platinum, didn't test it out very much since it's not my daily driver. May come with 5 unselected fan curves for the Commander PRO. No clue if that's being carried over, it probably is. Due to the inferior RGB controllers from older keyboards, I've included an alternative batch of layers for the more recent keyboards which natively support the 16.8m color mode to keep the coloring consistent. Preview: [ame= ] [/ame]Maliwan2.1.cueprofile
  14. Corsair has an impressive lineup of keyboards and it's not completely apparent wich keyboards are all supported with the Nexus attachment doohickey. I use a K95 Vengeance 9000220-DE and would rather have a second USB cable runnig from the keyboard than to have to put the Nexus somewhere else other than on top of it.
  15. Stupid question, but did you actually put a macro on them, or remapped the keys? By default they don't do anything.
×
×
  • Create New...