But in my opinion I've never really had any problems with synapse. That all depends on whether your keyboard has onboard memory. So you can just install the software, set everything how you like and then uninstall it. IDK about that keyboard but the new viper mice and the new v2 lines of deathadders and basilisk have it as well. But as soon as I got another razer keyboard, everything worked instantly without issue.Recently, Razer has finally listened to all the hate regarding their software and they are making big strides to make new products not require keeping the software installed.wait, I said big strides didn't I? No, actually they are just YEARS behind everyone else and finally put onboard memory on their new mice. Whether its on purpose to force people to exchange it for a more expensive keyboard, or just a random software glitch… who knows. I actually returned my V3 tkl yesterday and picked up the Blackwidow Mech Full-sized green switch (I actually like the clickyness lol, who woulda thought?!) and as soon as I plugged it in, everything worked perfectly. Maybe Synapse is trying to read the “mouse” drivers for the keyboard, gets confused, and greys it out? (Is that even possible?) ![]() The blackwidow is also in the mouse drivers section for some reason? It’s additional details are the same as the Basilisk V3 (shows the same 3. ![]() If I then click Driver Details, here’s what it additionally says: Razer Firmware updater says that both M+KB are version 1.02.00ĭevice manager lists both M+KB as version 3.0 Razer Central (in the about section) is version 7.13.0.628 In the “updates” section of Razer Central: 20231003 In the “About” section of Synapse (and windows Control Panel): 3.8.930.92719 I hope that it’s a software issue that can be fixed, as I otherwise like this keyboard (and having to use my old one while this one is shipped in the mail is gonna be miserable). Upon restarting, both are greyed out (and as usual, re-plugging the mouse fixes just the mouse). ![]() Upon the update finishing, keyboard is greyed out (and the mouse too, even though it wasn’t before the keyboard update). When I do the same for my keyboard, both Synapse and windows tell me it has to restart to finish installation. I download it, and the mouse is configurable. I’ve tried some of these things many, MANY times over the course of a full day (minus firmware/fresh install of windows) but nothing reliably works to have keyboard customizable.ĭuring a ‘fresh install’ of Synapse, when I plug in my mouse it gets detected, and an update pops up in Synapse. bat), cleaning out program files/program data/etc folders, clearing the registry of anything razer related, tried installing all optional modules, tried installing no optional modules, tried the repair utility, tried every usb port, tried updating firmware (keyboard was up to date, mouse update didn’t change anything), and did all of the previous steps with: Windows defender on (with exceptions for all razer stuff), windows defender turned off, windows update disabled, automatic downloading of drivers disabled, and even a new install of windows. I’ve tried uninstalling/reinstalling synapse, re-downloading synapse each time, running it as admin, clearing all drivers manually (and automatically with Driver Cleaner. Even when it wasn’t greyed out, the configuration I made to hypershift keys didn’t seem to work (could just be user error). Upon PC restarting, or closing/re-opening the software, or re-plugging the keyboard - the keyboard gets greyed out again. I can’t reliably have this happen, though. There has been a tiny handful of times the keyboard wasn’t greyed out after I did a full reinstall, or ran the repair utility. ![]() The mouse keeps its configurations (on-board memory) even after I close the razer software (aside from the RGB, which is then handled by SignalRGB). I can configure RGB using another program (SignalRGB, which needs razer software closed). This doesn’t work for the keyboard.īoth of their RGB lights still work by default, cycling through colors (keyboard) or using what I chose (mouse). If I ONLY have the mouse plugged in, the mouse is configurable after a system/program restart, and never gets greyed out. I can unplug/plug in the mouse to fix the mouse, but this doesn’t work for keyboard. Strangely, if I restart with both M+KB plugged in, both end up greyed out after a system (or Synapse) restart. The keyboard is greyed out, and cannot be configured. Both work if plugged in, including the standard hypershift keys. Just bought my first mechanical keyboard (Blackwidow v3, with yellow switches (if that matters)) along with a mouse (Basilisk v3). I’m glad that I’m not the only one with this issue.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |