..:: PCSX2 Forums ::..

@Eloris: cool, I'll add that change in for next version. I'll also look into adding an option to disable the LEDs.

That would be awesome, thanks!

@Ashnal:
@Ge-Force:

I've had a look at what would be required to separate the triggers from being a shared axis in DInput. Mapping L2 -> Z axis, R2 -> Rz would not be able re-use the X360 HID Descriptor, I would have to create a new descriptor and new virtual device type, which would not be XInput compatible.

The scope of the changes required would be outside what is desirable at this stage of the development cycle. I intend the next version to be the release candidate, for which I'm looking to only implement bug fixes, minor optimisations and minor feature enhancements. I will look at it again after a 1.0 release.

@Ashnal: I have been unable to reproduce a BSOD on disabling a virtual controller (or any of the other devices Virtual Bus, USB DS3, BTH DS3). When I disable in Device Manager the pop up below is displayed. Pressing Yes, system reboots cleanly and the device is disabled. Pressing No, device stays active until next reboot (which is clean) and the device is disabled.

I tested on Win 7 x64 and Win 8 x64, on which OS were you experiencing the BSOD?

When I try to "Add Force Feedback Effect" the drop down menu only shows "[Detached] XInput Pad 0]" the controller (D3) is plugged in and i'm using the last release(I'm pretty sure the detached xinput if from MIJ witch I uninstalled).

Everything else seams fine, Nice work!

Scarlet Crush, it appears you will have to make it painfully obvious that your SCP Filter and Virtual HID implementation will not provide a physical Xbox device string to the system and allow some sort of sorcery that allows XBCD to be installed on a PS3 pad.

It seems Ashnal has gotten all confused since he seems to think that he can utilise the SCP filter to allow him to install XBCD on the ps3 pad.

Since both utilise a virtual HID descriptor (yours to simulate a wired 360 pad it seems). its just not possible... not to mention that even trying to force xbcd on a ps3 pad will likely introduce bsods because of the eletronic differences between the two.

hello love the drivers but would love it even more if you would add this bluetooth id to the mix :
USB\VID_0B05&PID_17B5&REV_0112
USB\VID_0B05&PID_17B5

@ragingmonkey: added your hardware id, see Post #301.

@Squall: yes, the SCP Filter Driver does not provide a physical X360 device string since it is purely a filter driver.

The replacement for the filter driver is entirely different. See attachment for architecture.

The DS3 and Bluetooth Dongle drivers use WinUSB, they are not exposed as USB/HID devices directly. They are controlled by ScpService, which is a user space Windows Service.

The Virtual X360 Controller Bus, kernel space driver, provides what is essentially a software Root USB Hub into which 1 - 4 Virtual X360 Wired Controllers can be plugged. The bus is controlled by ScpService via DeviceIoControl() calls on a sideband interface.

Each Virtual X360 Wired Controller is enumerated exactly the same as a real X360 Wired Controller (hardware ids, compatible ids, HID descriptor, configurations, interfaces, pipes, etc). The bus driver was written to make a Virtual controller indistinguishable from the real thing as far as the XUsb21.sys driver is concerned.

The only reason for XBCD not working or having issues would be it has usage requirements different from those of XUsb21. There are no issues with electronic differences since the DS3/BTH hardware is isolated by the WinUSB drivers, and there are no power requirements for the Virtual X360 since it is software only.

It appears that XBCD is installable onto the VirtualBus, however the virtualbux is not simulating the subclass and interface protocols of a 360 pad which are required for the controller to be detected by other parts of the driver (the XBCD Setup utility for instance)


- I could be wrong though, but if either or both of these aren't implemented properly, it would be why Ashnal can install the driver but the gamepad is not recognised by the setup utility.

Either way, I'm sorry Ashnal, but i can't support using xbcd on a virtual interface.

(02-27-2013, 04:04 AM)Squall Leonhart Wrote: [ -> ]It appears that XBCD is installable onto the VirtualBus, however the virtualbux is not simulating the subclass and interface protocols of a 360 pad which are required for the controller to be detected by other parts of the driver (the XBCD Setup utility for instance)

Code:

    // Check for Xbox 360 gamepad
    if(pid->bInterfaceClass == 0xFF
        && pid->bInterfaceSubClass == 0x5D
        && pid->bInterfaceProtocol == 0x01)
    {
        pDevExt->is360 = TRUE;
        KdPrint(("XBCDStartDevice - Detected Xbox 360 gamepad"));
    }

- I could be wrong though, but if either or both of these aren't implemented properly, it would be why Ashnal can install the driver but the gamepad is not recognised by the setup utility.

Either way, I'm sorry Ashnal, but i can't support using xbcd on a virtual interface.

Damn, I'll find some way to separate the triggers eventually.

@Scarlet.Crush
I think the BSOD may have been a cause of trying to use this and XBCD together, I'm on Win7 x64.

I really wanted to play Trackmania with analog brake and throttle too >_>

@Squall: the driver detects it as an X360 controller, and all the inputs display correctly in Game Controllers ... just the setup/config utility doesn't work.