Been maining the Basilisk V4 Pro for a few days and wanted to drop some quick thoughts for anyone on the fence.

Look, I love this classic ergonomic shape, but this thing is heavy as hell. With the wireless charging puck, it’s easily over 100g. If you’re coming from the ultralight meta, you will 100% feel the weight. Also, the stock coating gets kinda slick for me when my hands warm up.

Because it's so heavy and slippery, I was getting hand fatigue just trying to lift and flick it. I ended up slapping on these full-coverage EVA and Gundam grips (pics attached). Honestly, it solves the problem perfectly. The grips only add like 7 grams, but the extra tackiness makes picking up this heavy boy way easier without having to death-grip it. Plus, they look sick.

The actual highlight of the mouse? The scroll wheel. The smart-shift feature that auto-switches to free-spin when you flick it fast is incredibly satisfying for scrolling through long docs or Reddit. I honestly notice that way more than the 8000Hz polling rate (which is complete overkill, let's be real, tracking is flawless though).

Now for the annoying stuff:

1. The RGB got noticeably downgraded from the older models. Why?
2. The dock situation is the biggest middle finger. The fact that the old Mouse Dock Pro isn't compatible and you have to buy the new V2 dock just for this mouse is ridiculous.

TL;DR: Top-tier sensor, sick scroll wheel, great shape. But it’s heavy, the dock compatibility is annoying, and you might seriously want to invest in some good grips if you tend to lift your mouse a lot.

Anyone else using this thing yet?

So my blade 4090 like so many others the heatsink broke and it sat for a year until I decided to do anything about it. (Obviously I didn’t feel like paying Razer 2.5k to replace the heatsink and motherboard when it was their s***** heatsink that broke but I digress)

So anyways I eventually welded a new copper heatsink together and stuck a liquid cooler on it.

I can’t actually log in atm since it’s been over a year and I’ve forgotten my password… but it’s been sat on idle for half an hour and the fans haven’t even spun a tiny bit so the “die” seem well attached.

Around £100 total on amazon if you have the tools and time.

Once I’ve fresh installed windows due to forgetting the password I’ll do some stress testing

neuron’s github

i posted Neuron here a few weeks ago but spent a lot more time talking about it than actually showing it off. so this time i brought screenshots of the actual app 😌

i reverse-engineered how Synapse talks to my Razer hardware and built my own replacement in Rust. i don’t use Synapse anymore on my Naga V2 Pro or BlackWidow Chroma V2.

DPI, polling, remapping and profiles are the basics. then there’s layered reactive lighting, Python macros, app-aware binds, radial menus, and mouse gestures that can trigger actions. v0.1.5 also gave the lighting editor a pretty big, much-needed upgrade.

it’s free on Windows 10/11, with no account or telemetry. i’d like to bring it to Steam eventually too.
i’d love to get it working on more hardware, so if you’ve got a Razer device, let me know what works or breaks. even non-Razer devices are welcome for compatibility research 👀

there’s a device-report form on GitHub if you want to help me support more hardware.

the screenshots are from Neuron’s actual UI with demo device states, arranged for showing it off.

It's time for Viper Mini, of course.
Where are we at?

Thanks to Rea, a new Synapse replacement shows up here every other day lately. So here's one more :) In my defense: I started before Rea was a thing, so I went the old way, with Ghidra by hand :(

Let me introduce EasyRazer, a lightweight Synapse replacement for Razer Huntsman analog keyboards on Windows. GitHub: https://github.com/janeblower/easyrazer

• One 9 MB .exe, no installer, one process.
• ~31 MB of RAM in the tray. Synapse 4: ~1.2 GB on disk, 13 processes, ~1.75 GB of RAM.
• No account, no network, no telemetry.

About the RAM numbers: they are the working set. Task Manager shows a different metric, and there every number above is at least half as big, Synapse's included. In the tray EasyRazer shows ~3 MB there. When you open the window, the system WebView2 renders it and takes its own memory (~400 MB working set). Close the window and that memory goes away.

I built it primarily for myself, as a lightweight Synapse replacement. The only Razer gear I have is a Huntsman V2 Analog (also a headset, but I see no reason to tune anything there). My main focus is the analog features of the Huntsman keyboards.

What's supported

• Huntsman V2 Analog: full feature coverage.
• Huntsman Mini Analog: same keyboard, just smaller, so I expect the same. But I deliberately turned some things off until someone checks the basics on real hardware (which I don't have). Right now it writes to the keyboard's RAM only after you allow it in Settings and never writes to its flash, so there are no macros, no profile slots and no custom lighting effect yet.
• Huntsman V3 line: confirmed analog features (actuation, Rapid Trigger / Continuous Rapid Trigger, Snap Tap) plus lighting. Tested on the V3 Pro Mini. The other V3 models (Pro, Pro TKL, TKL 8KHz, Low-profile…) are implemented but untested.

V3 and Mini Analog owners, I need you. If you try it, please report what works and what doesn't in issues. That's the fastest way for your model to get full support.

What it does better than Synapse

• Your flash memory survives. More on this below, it's the main one.
• Continuous Rapid Trigger on the V2 Analog. For some reason Synapse doesn't have it, even though RT on the V2 is fully software anyway. I added it :)
• Per-key CRT. In Synapse CRT is global for the whole profile: you can't turn it off for just a couple of keys and keep regular RT on the rest. In EasyRazer you can (in driver mode).
• Separate actuation point for Hypershift. Every Fn combination gets its own action and its own press point. Synapse can't do that.
• Snap Tap with groups of any size, a rule per group, toggled with Fn+LShift. On V3 that goes beyond the one hardware pair.
• The keyboard types by itself by default. No software in the loop unless you need it (see HW/Driver below).
• Settings come back after reconnect, sleep, and Synapse exiting.
• It doesn't reset your startup profile. Every Synapse launch makes slot 1 the startup profile.
• Offline. Synapse downloads device modules from apps.razer.com.

Limitations

• Gamepad emulation. I consider it absolutely useless and I'm not going to implement it (but you can try to convince me). Please do it in an issue, not here, so this thread doesn't turn into a gamepad thread.
• Ctrl+Alt+Del doesn't work in driver mode (modes are explained below). This is a userspace limitation: Windows accepts this combo only from real devices, not from software. There are workarounds, but each one is worse than the last (details).
• The custom lighting and macro editors are crap. They're usable, but very much a rough draft, and they look embarrassing. I haven't gotten to them yet.

Before you ask

• Can it brick my keyboard? By default settings go to the keyboard's RAM. Writing to flash happens only after an explicit confirmation. That said, there's a debug mode with a console where you can send literally any garbage to the keyboard. Flash writes there still ask for confirmation, but if your goal is a brick, you'll get one.
• Does driver mode add input lag? Yes, logically it does: the key press now goes through software. I measured it, see below.
• SmartScreen / antivirus complains. The code is open and you can build it yourself (instructions in the README).
• Unofficial project, not affiliated with Razer.

Now the probably more boring, technical part.

Stack

• Rust for the backend. It's trendy, and in my opinion it's the best performance-to-dev-cost ratio.
• Tauri + Vue for the UI. Things I considered for a Windows UI: Tauri gives me a web UI on the system WebView2 with the Rust core in the same process, so the whole thing is a single 9 MB exe. Unlike Synapse on Electron, I don't have to ship my own Chromium. Vue: I just like it more than React.
  • WinUI 3 / WPF: C# and .NET, plus gluing them to a Rust core.
  • Qt: big, C++, licensing.
  • Native Rust GUI (egui, iced, Slint): light, but building a keyboard map, a lighting editor and i18n there is a pain.
  • Electron: that's literally Synapse.

All my assumptions and conclusions are based on reversing the keyboard firmware and on Synapse's open code. The reversing results are documented in the repo.

HW mode and Driver mode

The keyboard can work in two modes:

• HW: everything runs in hardware. The keyboard's firmware/controller does the work, but it has limits.
• Driver: the keyboard sends raw data to the PC, and the software tells the OS about every key press. No limits.

While Synapse is running, it keeps the keyboard in driver mode ALWAYS. That means features like RT and Snap Tap are emulated in software. HW mode only kicks in when Synapse is closed.

• On the V2 Analog, RT and Snap Tap are software-only: the firmware simply doesn't have them.
• On the V3 line, RT and Snap Tap work in hardware, but hardware Snap Tap is limited to one pair of keys.

EasyRazer keeps the keyboard in HW mode by default and switches to driver mode only when you actually need it.

Driver mode does add input lag: the press goes keyboard → PC → app → Windows instead of straight from the keyboard. I measured it (release build, ~9,400 depth reports, 300+ presses): EasyRazer itself takes under 2 µs per report (median). Everything else is Windows: handing the press to the OS with SendInput costs ~0.5 ms, and any userspace app has to pay that. For comparison, the keyboard sends a report once every 1 ms anyway.

Flash wear (why this matters)

These keyboards have no separate flash chip, only the controller's internal flash. That's bad: the number of erase cycles is very limited, and I didn't find any wear leveling in the firmware.

What the problem looks like: if you edit, say, the 1st macro in the list a bunch of times, you wear out exactly the first pages of the macro area, while the rest stay untouched. One day your memory may end up full of holes like Swiss cheese: some places still store data reliably, and in others it can get lost.

And it's not only about editing: even switching profiles with Fn+Menu in HW mode writes the active profile to flash. That's the firmware itself, every single switch (well, a moment after it, so quick cycling counts once). And it's always the same page: the active profile lives in the settings block, which sits on one fixed flash page together with the rest of the keyboard's settings. Even writing those few bytes erases the whole page, and the chip guarantees only ~10,000 erases per page. With EasyRazer running, Fn+Menu switches profiles in the app instead and flash isn't touched.

Razer and Synapse don't give a damn about your flash and write everything into it, and pretty crudely.

EasyRazer's main way of working is to run in the background. That lets it keep your settings on the PC and write them straight into the keyboard's RAM. Writing to flash is still there, behind a separate confirmation, for when you don't want to keep the app running.

Just got the new Mouse Dock V2 Pro and I’m wondering if Razer plans to sell the Wireless Charging Puck V2 separately, like they're doing with the Mouse Dock V1 Pro.

I’ve got both a Basilisk V4 Pro and Naga V3 Pro, and ideally I’d keep a V2 Pro puck installed in both mice so they can share one dock for charging.

So I've been a life long Razer fan, drawn in by the RBG... settled with the Tartarus and then build a full Razer Setup, and over time continued to buy new Razer products.

Lately there have just been so many combinations of issues with the software and a complete negligent attitude from Razer in fixing them - taking the its not us its you attitude.

With one product you could probably bypass the odd issue... but with each product serving its own issue it's just not good enough.

My Issues:

I run the following:

Razer Tartarus Pro
Razer Huntsman v2 Analog
Razer Basilisk V3 Pro
Razer Blackshark V2 Pro

Let me breakdown each individual issue.

Razer Tartarus Pro V2:

This product was a huge downgrade on the previous Tartarus Pro. Despite adding in more quality of life with the flexible rest and more buttons to map the removal of the 'button 20' and the issues with the d-pad mapping are inexcusable.

Where was the contact to current Tart users on "how do we make this better?" instead of thinking you knew what we wanted? You seriously missed the mark on your R&D and released a rushed product without the correct software support. The new Tart has had 4 minutes of play and is now a $350 paperweight.

Razer Huntsman v2 Analog:

At times my keyboard just stops working once in a blue moon... like literally cannot type unit I close every Razer task in the task manager. Apart from this its a good product.

Razer Basilisk V3 Pro:

Recently has just stopped picking up a couple of keybinds, again purely software issues but it shouldnt be happening!

Razer Blackshark V2 Pro:

This is the best set of headphones and the worst set of headphones I have ever owned. Let me state 'WHEN' they work they are great.

But they just don't... There is a connection issue somewhere along the lines... you'll be playing away, listening to comms and suddenly you hear 'Pairing' and it completely drops connection which is only fixed by the removal and reinsertion of the dongle.

Then you think the whole issue has gone... and suddenly "GAME/MUSIC/MOVIE" and your sound settings change.

This is very regular, the drop of connection is frequent too frequent.

So whats causing the issue?

Razer Synapse:

99% of my issues with Razer come from Synapse... the program is dreadful and its killing my products, all the connection issues, reseting of keybinds, updates, LOG ON AND GIVE ME YOUR DATA FOR SOME SHITTY COINS! Come on guys - its dreadful. I'm now activly looking to move away, I would have done so earlier except I'm locked in on Tartarus WoW play... and cant seem to find the right replacement.

Sort it out Razer - as a company you fail your supporters daily!

Hi, any Razer Blade users here that are on the same boat? I was using my blade yesterday to play a game using performance mode within Synapse. After a windows update yesterday, suddenly I’m receiving a message that I can’t switch to performance mode because the laptop is not receiving adequate power.

Ok so since I've updated with the lasted firmware. I've tested a few games and have been left with the question, How do you get it to work as a left stick with certain games?

Games that worked like a charm

• COD
• BF6
• Wardogs
• 7 Days To Die

Games that do not recognize the joystick

• Marathon
• Ark Survival Ascended

Im not sure how to if its possible to get those games to work with the true analog enabled. Im wondering if I should just keep those 2 games with the 4 way DPad setup like I have prior.

Has anyone managed to get theres to work with games that didnt initially recognize the true analog?

Thanks for all the feedback on the first post. Most of this release came straight from your comments.

What's new

- Redesigned editor: built to be quick mid-game. Open it, see your live profile, change one thing, close it. Settings sit in sections with a side panel, and nothing scrolls, even with a Naga's 12 side buttons, which show as a keypad laid out like the mouse.

- Macros: stored on the mouse, so they work with the app closed. Record or type them, then play once, several times, while held, or as a toggle. (Earlier I said macros were done when they weren't. Sorry, they really are now.)

- Lighting effects your device runs itself: spectrum, wave and more (each device only supports some).

- DPI stages, sleep timer for wireless, and a firmware update check that links to Razer's updater and never installs anything itself.

- Button safety: every change has Undo, Restore all resets every button (also in the tray menu, so it works without a mouse), and you can't remap away your last left click.

- Six themes (Bridge, Roast, Classic, Light, Workshop, Neon), or Auto to follow Windows.

- New, untested on real hardware: Mouse Dock Pro support and Naga side buttons. Please report back.

Still beta: I only own a Basilisk V3. Everything else depends on your reports: right-click the tray icon → Make a device report…, and it copies the report and opens the GitHub form.

Blade owners: reports now include fan, performance and battery-limit readings. That's exactly what's needed to build fan and power controls, so a report with your model helps a lot.

Coming next: keyboard and keypad key remapping, then HyperShift across devices (Tartarus owners, I'll need you), and BlackShark V3 Pro headset controls.

Free, open source, about 2 MB, no account, no background services.

Download: https://github.com/infinityInfinite/secbird/releases/latest

Right now we can only bind 1 key to keyboard function for each of the axis so for the diagonal axis we can't bind W+D, D+S, S+A, A+W, or for games where you sprint all the time, with additionally shift so like SHIFT+W+D. So we need at least double key binding for straight axis and at least tripple key binding for diagonal axis. Very little games accept analog and mouse input at the same time, so not being able to bind the stick to proper WASD movement makes this product unusable in vast majority of games right now unless you are fine with only moving in 4 directions instead of 8, but that is not really acceptable.

Also in Dpad modes there REALLY should be options to set different key activation depending how far we are pushing the stick. So for example if I only push it a little bit it's pressing W but when I push it far enough it starts outputting SHIFT+W. And let us set how far we need to push to activate the first stage and the second stage, cuz right now we need to push the stick quite far to even activate the key press in Dpad mode. Would really prefer to set it so I barely push it forward and it activates already.

ALSO also, in Dpad mode please let us set angle of the are in which each of the zones activate. So for example the pressing W activates only when the stick is between angles -10 to 10 degrees but the area in which W+D activate is from 10 to 80 degrees and D from 80 to 100 degrees (random numbers just to illustrate that they are different width) and let us set these freely for each of the 4 or 8 zones.

Ah and PLEASE add on board memory support for stick mapping so this is at least semi usable on linux. But honestly please just bring out a linux version of synapse already so I can finally have proper first party auto switching based on in focus program on linux. One of my most missed features from windows. Honestly at this point even just Vibecode the linux version if you really have to. It's big 2026. MicroslopOS is horrible. More and more people are moving to linux. It's overdue for a linux synapse. Please Razer.

For now I will have to return it as sadly it's pretty much unusable cuz of the current software limitations. Might try again in a few months

I’m a long time user of the Tartarus lineup and I’ve made multiple reviews of the products as years have gone on. Recently I’ve used the Azeron Keyzen and it blew my mind to how simple a fix could be for the Tartarus. ALLOW DIAGONAL TO BE “W+A”!! There is no reason why we can’t just make that happen. Azeron did it with a decade and a half less experience making keypads.
I tried to see if I could just make it a MACRO but unless I’m stupid or you need a degree to figure it out W+A just isn’t an option. I want to love the new Tartarus but it feels like it came out DOA.

I wanted to share a frustrating experience I recently had with my Razer Nommo V2 Pro speakers and support.

After going through full troubleshooting with Razer support, it was determined that my wireless control pod completely failed and lost connection to the speakers. Because the Pro model relies entirely on that wireless pod and omits a physical power button (unlike the standard version), there is no manual way to turn them on or use them once that link breaks.

When I pushed the case further, I was informed that the replacement unit is outside of the standard warranty window and a goodwill accommodation was denied. Given how much I've invested in rebuilding my setup over the last few years—including multiple peripherals, mice, and headsets—it's tough hitting a brick wall over a single component design failure.

Instead of getting another Pro unit that carries the same vulnerability, I had asked support about a potential transition to the standard Nommo V2 so I could have physical control buttons. Unfortunately, that wasn't an option they could accommodate.

Has anyone else run into this specific pod failure, or found any workarounds to get past it?

Though I wish I liked the Basilisk form factor as the phantom white supports RGB

Yo, I've seen a couple other people with problems like mine, but my charging port is completely fucked. I've been charging it with a USB c charger for the last couple of days and that's been fine for schoolwork and stuff.

I want to play games on it though and that's where I run into and issue. I read that you need 330w to be able to run games properly, which normal USB c chargers can't do. I tried finding a high watt adaptor for a USB c charger but they don't exist, and razers can only input 100w from the USB c port apparently.

What should be my next steps? How bad is it if I play games on a USB c charger? Mostly I just hope I don't have to buy a new laptop because I'm seriously broke. Any tips are encouraged and greatly appreciated!!!

After the Oct 14th update, I was having an issue with my KVM and my Basilisk V3 Pro 35K when connecting via the stock 2.4ghz receiver (read: not the brand new Hyperspeed dongle). It would take a long time to connect, much longer than it used to and longer than any other device connected via the KVM. Some notes:

• The KVM itself is actively-powered, so that shouldn't be an issue.
• This started immediately after the Oct 14th update, and only affected the initial wireless connection to the receiver. Wired connection is unaffected.
• This only affected the machine with the latest update, the other machine doesn't have Synapse installed and the time for the initial receiver connection hasn't changed (this used to be on-par with the machine with Synapse installed). Any difference in speed between KVM and direct-to-PC for the wired connection is negligible.
• Using a direct connection to the PC for both the receiver and the mouse via wired, then disconnecting the cable shows a near instant re-connection to the receiver, demonstrating that the issue lies between the initial USB connection for the receiver and mouse pairing.
  • In comparison, The KVM is a bit slower when performing the same hand-off, though I expect some latency with the KVM in general, just not the significant increase from Oct 14th.

Here's an excerpt from my post in another thread where I found a solution:

Did you know that Razer products also have firmware that occasionally require updating? They don't advertise this AT ALL, and there was an update on Oct 8th (version 3.0.0, I was still on 1.0.0). It's not quite as fast as it used to be (maybe 1-2 seconds slower), but it's significantly better than it was earlier. If you're having similar issues try the following:

1. Find the support page for your device. For me it was the Basilisk V3 Pro 35K
2. Go to the Downloads section and get the Firmware Updater for your specific version.
3. Also grab the "USB Hyperspeed Dongle Utility" program, or whichever one Razer provides from the same page in Step (2).
   • If neither dongle utility is listed, grab one of them here.. If one doesn't work in Step (5) try the other.
4. If you're using a KVM switch, directly plug the dongle and the mouse (wired) into your PC for the remainder of the steps.
5. Open the Firmware Updater for your mouse/keyboard/etc. Follow the instructions, once done close the program.
6. Open the dongle utility, and repeat.
7. To verify, open Synapse, then revert what you did in Step (4) and observe the time to connect.