05-06-2013, 01:56 AM
@Excelsis: Now that 1.0.0.103 has been released I'm considering what to implement for future versions.
The biggest issue with X360 controllers is their handling of Triggers in DInput - they are both mapped to the Z axis (Z-,Z+) so only one can be active, and not usable as buttons in most DInput games.
What I'm thinking of doing is making the Virtual Bus capable of handling 3 device types, and being able to switch between them from ScpMonitor.
1. X360 Profile (current implementation).
2. DInput pad with Triggers mapped to separate axis (Z, Rz).
3. DInput pad with Triggers mapped to buttons.
I'm also going to be looking into supporting the PS3 BD Remote Control as a Keyboard/Mouse device. This will require a button mapping feature, which could be leveraged for use with pads (possibly including motion controls).
@Ocitda: right-click on the directory and select Properties, select the Security tab. In the list of users select SYSTEM, if the permissions list does not contain Full Control or has Write ticked in the Deny column - click Edit and change.
The biggest issue with X360 controllers is their handling of Triggers in DInput - they are both mapped to the Z axis (Z-,Z+) so only one can be active, and not usable as buttons in most DInput games.
What I'm thinking of doing is making the Virtual Bus capable of handling 3 device types, and being able to switch between them from ScpMonitor.
1. X360 Profile (current implementation).
2. DInput pad with Triggers mapped to separate axis (Z, Rz).
3. DInput pad with Triggers mapped to buttons.
I'm also going to be looking into supporting the PS3 BD Remote Control as a Keyboard/Mouse device. This will require a button mapping feature, which could be leveraged for use with pads (possibly including motion controls).
@Ocitda: right-click on the directory and select Properties, select the Security tab. In the list of users select SYSTEM, if the permissions list does not contain Full Control or has Write ticked in the Deny column - click Edit and change.