@Sekuroon:
@GeminiFyre:
The USB\VID_0A5C&PID_21E8 hardware id is supported, it's a Broadcom BCM20702 Bluetooth 4.0 device. I have one of these, branded by Belkin - and have used it for testing.
Windows decides which driver to install by ranking, the Broadcom driver will be picked by default as it has a higher ranking. To override this click
Force Install when running ScpDriver.
The Bluetooth 4.0 spec is backward compatible with all previous versions, so it does support Bluetooth 2.0+EDR.
@phly95: writing a complete BTH stack would go beyond the scope of the project.
@G-Man: the X360 DInput driver maps the D-Pad to a Hat-Switch, sounds like TF2 has limited support for this.
@Muguetsu: sorry, I missed your post about the ScpServer screenshot. I'm kind of at a loss as to what is happening with your machine. The behaviour is bizarre at best, tbh it sounds like you have a virus / malware which is preventing the ScpControl.dll from being loaded. are you seeing any other strange behaviour on your PC?
@bluejeans: yeah, as MaJor replied - did the same thing on my HTPC.
@azkrath: added an update for your hardware id, see Post
#1.
@mintos5: I don't think I can support the Gasia gamepad - I don't own one so testing and support of it would not be possible, there is no way to distinguish it at runtime other than it fails Service Discovery.
@Ba'al: I'll look into adding it.
@justwow: did you read and follow the install instructions? namely around the Microsoft Xbox 360 Controller drivers.
@kimec: The Navigation Controller has the same USB/HID messaging as a DS3 - only the hardware id and BTH name are different. The Motion controller has nothing in common, messaging wise, with a DS3. Consequently adding support for it would be non-trivial.