Having redo a bunch of macros every time would not be fun. Sometimes on the keyboard I find it just as easy to redo simple lighting schemes, but I do keep my common actions stored in the library so I can drag them into new profiles as needed. It serves as a clipboard for moving stuff around. **Also, if you have already created an intended hardware profile as a "software profile", you may be able to quickly recreate it in the HW slot by copying lighting and actions to the Library. If you are not in that group, the link below to Inheritance's guide may help. Such is the way of the world at the moment. Any time I write a paragraph with more than 3 sentences, someone usually responds with "WoT" or "I am not going to read all that". However, even if there was a comprehensive official manual, I am not sure how many people would utilize it. There absolutely is a learning curve to all of this. While you could probably do the same thing with a multi-slot option for "save to device", that brings us back around to different capabilities between hardware and software profiles and this method helps you design it to be savable in the first place. Things are mostly the same, but this is a better way to handle devices with multiple save slots. You just resave them in the order you want. This makes re-arranging the profiles on your keyboard really easy. You can choose to save it in any of the physical memory slots 1-3. However iCUE software "K70 mk.2 HW1" is not directly tied to physical memory slot 1. The software will tell you when you break a rule that won't save. There you can change, edit, and set it up with guidance. Hardware Profile Way (HW1, HW2, HW3) -> You create the save profile in the HW slot in the iCUE software. Typically for use with "one slot" devices like mice. Click on menu drop down "save to device". It's the method of doing so that has changed. No, you can still save profiles to keyboard. ![]() ![]() Are you saying that iCUE does not, and that this is actually a good thing? However, at least it lets me overwrite the HW1 - HW3 profiles from those I create. Fortunately, all I want is a sensible color scheme, with no more than 5 total static colors. The CUE 2 software makes the limitations clear, if I do too much in a profile, and then try to save it to the hardware. I understand that the ARM processor and memory in the device are limited compared to their PC counterparts. Like the OP, I like the idea of saving my profiles to the KB memory. I eventually ignored the directions, and went for 2.24.50, which works (but it turns out to be deprecated now as well, so eventually I'll move to iCUE-not anytime soon, though). Poor printed directions in the box, and poor directions at the Corsair repository of software had me install CUE 1.16, which failed even to detect the KB, and had me thinking it was an issue with HID devices. It took me 2 weeks to go from initial setup of my Strafe Mk 2 to being able to create a specific color scheme, and save it to the KB. Thank you for your helpful replies, here and elsewhere on the boards.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |