SteelSeries gaming controllers are designed specifically to bring the PlayStation and Xbox console gaming experience to any platform, with easy pairing, extreme durability, and long battery life on Apple, Windows, Android, Bluetooth, and more.
New trigger designs and clickable joysticks
Windows XP/Vista and OS X 10.7 are no longer supported. For support for current SteelSeries devices on these platforms, you can install a special legacy version of SteelSeries Engine, 3.4.5, for Windows XP/Vista or OS X 10.7. Future SteelSeries devices will require at least Windows 7 or OS X 10.8 for use with the latest SteelSeries Engine 3. This package provides the installation files for SteelSeries Device Factory Driver version 1.1.10.3. If the driver is already installed on your system, updating (overwrite-installing) may fix.
I am trying to get some help here, seeing that Steam Support takes eons to answer you. I bought a Stratus XL Controller and Bluetooth Dungle for my PC, as I read that The Witcher 3 is 'better' to play on a controller. I can easily pair the controller to my PC(and it is succesfully paired, as I can use it as a mouse on t.
SSteelSeries gaming console controllers are designed with Hall Effect magnetic sensors for ultimate gameplay precision and a consistently smooth feel. Our controllers also include clickable L3/R3 joystick buttons so you can enjoy the full console experience.
Be the best via Bluetooth or USB
Easily game on the go with any Android or Windows device using SteelSeries gaming controllers. No software needed – pair and play on Windows, Android, Oculus Go, and Samsung Gear VR via Bluetooth or the USB Wireless Adapter.
Steam-supported controllers for all your favorite games
SteelSeries gaming controllers allow for gameplay on 5000+ controller-enabled Steam games and 20+ hours of gaming via a lithium ion battery that allows for gaming while charging.
Get the best deals online or in a store near you
Whether the Stratus Duo for Windows, Androidâ„¢, and VR or the Nimbus+ for Apple devices, SteelSeries has the best gaming console controllers in esports and at the best prices.
-->This section describes the class-of-device (CoD) registry subkeys and entries that apply to the Bluetooth driver stack.
'COD Major' and 'COD Type' Values
Original equipment manufacturer (OEMs) can use the COD Major and COD Type values to indicate the Class of Device for a Bluetooth-enabled Windows device. After the Bluetooth class installer sets the Class of Device based on these registry values, a remote device can determine whether it is connecting to a portable computer, a desktop computer, a phone, and so on.
The registry path to the COD Major and COD Type values is:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesBTHPORTParameters
Steelseries Bluetooth Devices Driver
Note that setting these values changes the Bluetooth Class of Device for the system, regardless of which Bluetooth radio may be attached. You can set the COD Major and COD Type to DWORD values as defined for the Class of Device field values in the Bluetooth SIG Assigned Numbers.
The Bluetooth profile driver, BthPort.sys, reads the COD Major and COD Type values to determine how it should respond to a device inquiry. These values affect only the COD_MAJOR_XXX and COD_XXX_MINOR_XXX bits of the Class of Device. The COD_SERVICE_XXX bits are not affected by this registry entry.
If the COD Major and COD Type values are not set or are set to invalid values, the Bluetooth class installer will set these values to COD_MAJOR_COMPUTER and COD_COMPUTER_MINOR_DESKTOP, respectively.
Scanning Parameterization Settings
Profile drivers can specify scanning parameters settings for their device(s) in their profile driver's INF file to tailor to the specific needs of a given device scenario.
You can override the default system scanning parameters by providing one or more of the following scanning parameters listed below into the AddReg directive. More information on how to use this directive can be found in INF AddReg Directive.
| Value Name | Type | Min Value | Max Value |
|---|---|---|---|
| HighDutyCycleScanWindow | DWORD 0x10001 | 0x0004 | 0x4000. Shall be equal or smaller than the HighDutyCycleScanInterval parameter |
| HighDutyCycleScanInterval | DWORD 0x10001 | 0x0004 | 0x4000 |
| LowDutyCycleScanWindow | DWORD 0x10001 | 0x0004 | 0x4000. Shall be smaller than the LowDutyCycleScanInterval parameter |
| LowDutyCycleScanInterval | DWORD 0x10001 | 0x0004 | 0x4000 |
| LinkSupervisionTimeout | DWORD 0x10001 | 0x000A | 0x0C80 |
| ConnectionLatency | DWORD 0x10001 | 0x0000 | 0x01F4 |
| ConnectionIntervalMin | DWORD 0x10001 | 0x0006 | 0x0C80. Shall be smaller or equal to ConnectionIntervalMax |
| ConnectionIntervalMax | DWORD 0x10001 | 0x0006 | 0x0C80 |
Note
Steelseries Bluetooth Devices Drivers
Changes to scanning parameters make a global impact on the performance of the Bluetooth stack. Making changes to scanning parameters programmatically is not permitted. Using Low Duty Cycle scanning parameters that are too aggressive can not only have a negative impact to the available bandwidth for other Bluetooth Low Energy connections, but also for Bluetooth BR/EDR connections.