Conversation
The V3 Pro was deliberately excluded from the DeathAdder V3 rule while it was test-needed, so it fell to the generic placeholder. It has since been verified on hardware (mouse-protocol 0x00b7, firmware 2.1). The V3 and V3 Pro are one shell (the Pro drops the cable), so it shares razer-deathadder-v3.png the way the V2 family already shares one render. Note in the artwork README that razer-deathadder-v3.png is currently missing from the img.openmouse.app bucket (404), so both V3 models, and the showcase entry that lists it, need a maintainer upload before the art actually shows.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
With a DeathAdder V3 Pro connected, the device panel showed the generic placeholder. The V3 rule in
src/ui/device-images.tshad(?!\s*pro\b)on purpose, because the V3 Pro was still test-needed and the file deliberately leaves those models out.The V3 Pro has now been verified on hardware on both transports (
0x00b6wired,0x00b7receiver) (OpenMouse-Project/mouse-protocol#107), so this drops the exclusion. The V3 and V3 Pro are one shell (the Pro just has no cable), so it sharesrazer-deathadder-v3.pngthe same way the V2 / V2 Pro / Essential family already shares one render. Tests updated: the driver-reported name "Razer DeathAdder V3 Pro" and "DeathAdder V3 Pro (Wired)" both resolve, andisUnknownDeviceis false.Heads-up for maintainers: the V3 render is not in the bucket
https://img.openmouse.app/razer-deathadder-v3.pngreturns 404 today (checked 2026-09-15), so neither the V3 nor the V3 Pro will actually show art until it is uploaded, and theSHOWCASE_DEVICE_FILENAMESentry for it 404s too despite the comment saying every showcase file was checked. The Desktop repo has a normalized copy atpublic/devices/razer-deathadder-v3.png(1026x1026 RGBA) that could be uploaded as is. I added a note topublic/devices/README.md; I have not touched the showcase list. A dedicated cable-free V3 Pro render would be a nice follow-up but isn't needed for this to work.Tests
node --test src/ui/device-images.test.ts: 39/39 pass.tsc --noEmitclean.