[New Device] Steelseries Rival 5 Destiny Edition & QCK Prism XL Destiny Edition
<!-- When naming the support request please title the request as `[New Device] <Name of new device>` Please open one issue per device you would like to add --> ### Name of device: <!-- Please put the name of the product, including manufacturer, beneath this line --> Steelseries Rival 5 Destiny Edition Steelseries QCK Prism XL Destiny Edition ### Link to manufacturer's product page: <!-- Please add a link to the manufacturer's product page beneath this line --> https://steelseries.com/gaming-mice/rival-5-destiny-edition https://steelseries.com/gaming-mousepads/qck-prism-xl-destiny-edition ### Please select what type of device/interface the device uses: <!-- Please select from one of the following This determines how the device connects to the PC --> ~"DeviceType::USB" <!-- The device connects to an internal header or external usb port --> <!-- Please delete any lines that are not relevant --> ### ID information: <!-- For PCI (GPU) devices we will need the Vendor ID, Device ID, Sub-Vendor ID and Sub-Device IDs To get the Device ID formation for a GPU on Windows run the following command in Powershell: wmic path Win32_VideoController get name,PNPDeviceID Linux this can be found using the terminal: lspci -d 1002: -nnvm | head -6 | tail -n 4 && lspci -d 10DE: -nnvm | head -6 | tail -n 4 --> <!-- For USB devices we will need the USB VID and PID Windows Powershell: gwmi Win32_USBControllerDevice |%{[wmi]($_.Dependent)} | Sort Manufacturer,Description,DeviceID | Ft -GroupBy Manufacturer Description,Service,DeviceID Linux Terminal: lsusb --> USB\VID_1038&PID_183E&REV_0100&MI_01 Not sure about the mouse pad, cannot identify it from the long list of HID ### Please attach screenshots of the device's official control application here: <!-- Screenshots of the official control software should show lists of supported modes, color selection, and zone/LED selection capabilities of the device's official software. --> ![_L_O6Z5J_NZYTZNO_8FJCZ1](/uploads/49207661283a222c7e5bc1ffc5b74d10/_L_O6Z5J_NZYTZNO_8FJCZ1.png) ![_F4XM_Z__9__FG2XG__X__N](/uploads/fd52c5372b0b1d69b2350ac26788bdf7/_F4XM_Z__9__FG2XG__X__N.png) ![_B__77_D_FX_UG_P__DDL4J](/uploads/4e9bd75a893b9f5a07fd4d62da6d3af0/_B__77_D_FX_UG_P__DDL4J.png) ### Please attach device captures here: <!-- If you have code examples from other projects please link them here or alternatively for information on how to capture device packets please refer to the wiki article https://gitlab.com/Dr_No/OpenRGB/-/wikis/OpenRGB-doesn%27t-have-my-device --> <!-- For admin purposes: Please leave this section as is --> # Checklist for Step2 - [x] Name of device - [x] A link to the vendors product page has been included - [x] The transport bus has been identified and the appropriate label added to the issue. - [x] The device ID's have been included for [USB](https://gitlab.com/Dr_No/OpenRGB/-/wikis/USB-Vendor-Identification-and-Product-Identification) or PCI - [x] Screenshots of the OEM Application are included - [ ] There is either, appropriate code examples linked or suitable device captures attached <!-- For admin purposes: Please leave this section as is -->
issue