Mechanicus Power Sword special attack broken on MMO Mice on Linux

Issue Type (Required):

Weapons

Issue Description (Required):

I’m running the game on Nobara Linux through GE Proton 10-28, so this could be a linux specific issue, but i might as well document my experience just in case.

I am using a Razer Naga v2 Hyperspeed (MMO Mouse with a ton of buttons) and with a software called Input Remapper i map one of my side keys to Mouse 5 (most likely irrelevant to the issue).

With this way of remapping inputs, every weapon’s special attack EXCEPT for Mechanicus Power Sword works when bound to a mouse button.

No mods because they are all broken right now anyways.

How my linux system sees the Naga

Since this is a mouse with extra buttons it connects not like a normal mouse but as several different HID devices

sudo libinput list-devices | grep -A 5 -i "naga"
Device:                  Razer Razer Naga V2 HyperSpeed
Kernel:                  /dev/input/event14
Id:                      usb:1532:00b4
Group:                   4
Seat:                    seat0, default
Capabilities:            pointer 
--
Device:                  Razer Razer Naga V2 HyperSpeed Keyboard
Kernel:                  /dev/input/event15
Id:                      usb:1532:00b4
Group:                   4
Seat:                    seat0, default
Capabilities:            keyboard pointer 
--
Device:                  Razer Razer Naga V2 HyperSpeed Mouse
Kernel:                  /dev/input/event16
Id:                      usb:1532:00b4
Group:                   4
Seat:                    seat0, default
Capabilities:            pointer 
--
Device:                  Razer Razer Naga V2 HyperSpeed
Kernel:                  /dev/input/event18
Id:                      usb:1532:00b4
Group:                   4
Seat:                    seat0, default
Capabilities:            keyboard 


As a gamer best I got is speculations, but my money is on the fact that Mechanicus Power Sword has 3 levels of charge, and thus has something different compared to other sword, which directly messes up with how it interacts with special action binding.

It could also be a problem with input intents / input actions (however it’s called in stingray) and their interaction with HID devices that have multiple Devices sitting at the same Id (notice how every device in the output has the same Id: usb:1532:00b4)

Steps to Reproduce (Required):

Case 1 (simple):

  1. Enter the game and go to the settings. Click the button on the mouse to set the binding to special attack. The binding is being set properly, the game recognizes the input as Mouse button 5 (side button)
  2. Press the button in game with a Devil Claw Sword. The sword parry animation plays.
  3. Press the button in game when wielding Mechanicus Power Sword. The input produces no result

Case 2 (using a mouse that naturally has the Mouse 5, without proxying it over Input Remapper):

  1. Wield Power Sword.
  2. Hit Mouse 5 on Naga.
  3. Works. Both holds and taps.

Case 3 (Arbites Shock Maul):

  1. Wield Arbites Shock Maul
  2. Hit mouse 5 on Naga
  3. Works

Case 4 (Disabling Input Remapper)

Taking out the variable to localize the point of failure.

  1. Disable Input Remapper. Side button defaults to Num_Lock. Bind Weapon Special Action to NUM_LOCK *(1)
  2. Pick Arbitrator. Shock Maul works
  3. Pick Skitarii again. Devil Claw works
  4. Pick Mechanicus Power Sword. Broken

Case 5. Just using a keyboard

  1. Mechanicus Power Sword special attack works (but this is incredibly uncomfortable (to me))

*(1) Might sound weird but it’s used to toggle the 12 buttons on the side which are bound as a Numpad in the default mode. We don’t have a software to flash Razer mice outside windows so this is the most generic case that works for me.

[PC] Do You Use Mods? (Optional):

Yes, and I’ve tried disabling them

Reproduction Rate (Required):

Constant (100%)

Platform (Required):

PC - Steam

[PC] Upload Console Log & darktide_launcher.log (Optional):

console-2026-06-24-18.33.40-72fcc6e7-ae2f-4612-acbb-042daad903d7.log (243 KB)console-2026-06-24-18.03.59-7ad796e8-6335-45ab-91ab-6a3e2581e94a.log (387 KB)