Updated : I've been working on a replacement for the Filter Driver + Wrapper which provides USB + Bluetooth + Native XInput support. This is now released and available for download. [See Post #937 for Screenshots]

Download latest version here.

Requirements
1. Microsoft .NET 4.0
2. Visual C 2010 Runtime.
3. Latest DirectX Runtime.
4. Latest Xbox 360 Controller Drivers available.
5. Genuine Sony DualShock3 or SixAxis Controller(s).
6. Minimum of Bluetooth 2.0 + EDR Dongle (if using Bluetooth).
7. Administrator rights on your PC.

Note : The Bluetooth Driver requires that you dedicate a Bluetooth Dongle to DS3 use. It will not be usable by other Bluetooth devices after the driver has been installed.

Important - make sure your Bluetooth dongle and DS3(s) are plugged in via USB before installing the drivers.

Xbox 360 Controller Drivers - these are available from Microsoft here.
Windows 7 - Run before installing the SCP Drivers. (Windows 7 shipped with outdated drivers which may cause stability issues)
Windows XP and Vista - Run after after installing the SCP Drivers.

New Install
1. Connect your Dongle and DS3 via USB and let Windows install it's default drivers.
2. Unpack the archive.
3. Create a directory where you want the Service to run from. [Recommended - C:\Program Files\Scarlet.Crush Productions *]
4. Copy the contents of the ScpServer\bin to the directory you created.
5. Run ScpDriver.exe.
6. XP/Vista - check the Force Install option. Win 7/8 leave it unchecked.
7. Click Install.
8. Click Exit.

* create from an elevated command prompt if you have UAC enabled. The directory should not be created anywhere off your User directory (eg on your Desktop, or in your Downloads directory), it should also not be on a Network drive.

Pairing a DS3 to your Bluetooth Dongle - plug in the DS3 to USB while the Service is running, the DS3 will be automatically paired if required.

Disconnecting a DS3 - Press and hold L1 + R1 + PS for 2 seconds.

The drivers support 4 DS3s connected by USB or via Bluetooth (one dongle can support 4 DS3 connections).

Supported OS - XP (x86), Vista (x86, amd64), Win 7 (x86, amd64), Win 8 (x86, amd64) [all binaries are signed]

Currently Supported Dongles
USB\VID_03F0&PID_231D
USB\VID_045E&PID_3500
USB\VID_0461&PID_4D75
USB\VID_046D&PID_C709
USB\VID_047D&PID_105E
USB\VID_0489&PID_E011
USB\VID_0489&PID_E042
USB\VID_0489&PID_E04E
USB\VID_04CA&PID_3006
USB\VID_050D&PID_016A
USB\VID_05AC&PID_821A
USB\VID_05AC&PID_821F
USB\VID_07D1&PID_F101
USB\VID_0930&PID_0215
USB\VID_0A12&PID_0001
USB\VID_0A5C&PID_200A
USB\VID_0A5C&PID_2101
USB\VID_0A5C&PID_2146
USB\VID_0A5C&PID_2148
USB\VID_0A5C&PID_2150
USB\VID_0A5C&PID_2153
USB\VID_0A5C&PID_217D
USB\VID_0A5C&PID_2198
USB\VID_0A5C&PID_21E1
USB\VID_0A5C&PID_21E8
USB\VID_0B05&PID_1715
USB\VID_0B05&PID_1783
USB\VID_0B05&PID_1785
USB\VID_0B05&PID_179C
USB\VID_0B05&PID_17B5
USB\VID_0B05&PID_B700
USB\VID_0C10&PID_0000
USB\VID_0CF3&PID_3002
USB\VID_0CF3&PID_3004
USB\VID_0CF3&PID_3005
USB\VID_0DB0&PID_3801
USB\VID_0DF6&PID_2200
USB\VID_0E5E&PID_6622
USB\VID_1131&PID_1001
USB\VID_1131&PID_1004
USB\VID_1286&PID_2044&MI_00
USB\VID_13D3&PID_3304
USB\VID_413C&PID_8126
USB\VID_8086&PID_0189
USB\VID_8087&PID_07DA

Tools
ScpServer.exe : GUI based version of the Service.
ScpPair.exe : GUI tool to allow pairing with an external device (eg Nexus Tablet).

Updates
USB\VID_0930&PID_0214 - SCP-DS3-Driver-Package-1.0.0.103-Bth-Update-1.7z
USB\VID_0A5C&PID_2154

USB\VID_0489&PID_E04D - SCP-DS3-Driver-Package-1.0.0.103-Bth-Update-2.7z

USB\VID_413C&PID_8197 - SCP-DS3-Driver-Package-1.0.0.103-Bth-Update-3.7z

USB\VID_0A5C&PID_2021 - SCP-DS3-Driver-Package-1.0.0.103-Bth-Update-4.7z

USB\VID_05AC&PID_8286 - SCP-DS3-Driver-Package-1.0.0.103-Bth-Update-5.7z

USB\VID_0A5C&PID_2100 - SCP-DS3-Driver-Package-1.0.0.103-Bth-Update-6.7z

Install Update
1. Unpack the archive. *
2. Copy the contents of the ScpServer\bin to the directory you created.
3. Stop the Service [net stop "SCP DS3 Service" - from an elevated command prompt, or use Service Control Manager]
4. Run ScpDriver.exe
5. Uncheck Configure Service, then click Install.
6. Start the Service [net Start "SCP DS3 Service" - from an elevated command prompt, or use Service Control Manager]

* Bluetooth Hardware Id updates contain all previous updates.
___________________________________________________________________

The Filter Driver + Wrapper is no longer supported, but is still available for download here.

An updated XInput Wrapper is included as part of the Driver Package and maintains backward compatibility with :

- DS3 on SCP Filter Driver
- DS3 on libusb-win32 Filter Driver
- DS2 on Play.com USB Adapter
- SpeedLink Strike FX pad.
___________________________________________________________________
XInput-Wrapper-SCP-2.2.1.88.7z: MD5 - 0D011D6F6CD89D2DD3E0C2A616E9953A
SCP-DS3-Driver-Package-1.0.0.103.7z: MD5 - 9ED702316E50358722FEA4499A72A9B3
SCP-DS3-Driver-Package-1.0.0.103-Tools.7z: MD5 - A3B5A22B6D5319B0393516F2DB7C11CD

So in essence, all you have done is what x360ce has been doing way before you even thought about it.

VBA-M

I wrote a utility which solved a specific issue for me and shared it with the community. Personally I prefer to do things for myself if possible and learn a few things in the process. If anyone else can learn anything from the source code or make use of the utility so much the better.

Your problem with that is?

My problem is your opening post, shows a lack of understanding of what was wrong.

A device does not have to support xinput in the least to work on windows 7

Drivers on the other hand, of which most adapters can work just dandy with the native HID driver installed, can be the limitation on many cheap adapters.

So to bypass the issue of drivers, you are passing the raw device information as Xinput functions i take it?

VBA-M

I wrote what is essentially an Upper Filter for an HID Class device (specifically targeted at the Play.com device id - VID_0B43&PID_003). If this was installed as a Filter the Driver would have to be signed to install on Vista or 7 (barring the usual workarounds), so to bypass this requirement I wrote it as an XInput wrapper.

Yes it reads HIDClass reports and convert to an XInput (X360 specific)compatible form, that is what filters do.

By 'does not work correctly' I meant - it installs fine as a USB HID Device + HID-compliant game controller, but is no longer usable in any games.
The specific game I was playing at the time was FFXI, which would not recognize it any longer, and could not support X360 Triggers as buttons.

Yeah it sounds like the adapter fakes a HID just enough to get it to be detected as a HID device, and allow hid driver installation, but the information it sends is not compatible with the native HID input driver to accept button and axis data, same as the PS3 control.

I wasn't dismissing your work btw, just refuting the idea that the control wouldn't work because it lacks xinput.

Good idea overall.

VBA-M

As an aside - x360ce doesn't recognize the DS2 Gamepads connected via the Play.com USB adaptor ... (or I can't get it to anyway).

yeah x360ce is a api wrapper, xinput > dinput

VBA-M

Modified first post. Better ?

I don't see anything wrong with this topic. Good work!