Login

This Months Donations

$363.05
of $500.00 goal
Server, CDN, Network, Licensing
Development Budget
Developers Beer Fund
Recent:
Trinitroglycerol
$5.00
ExiledXD
$2.00
Tim Rohbock
$2.00
winky650
$2.00
darkfall
$2.00
Number of donations
91
Highest donation
$100.00
Average donation
$4.21

Profile plug-in won't remember 2nd 3rd or 4th controller mapping!

8 months 2 weeks ago #1 by billy
So here my problem... I have 3 direct input controllers that I am attempting to use using the Scarlett crush plugin and then mapping out each individual button to the virtual Xbox controller, well it all works great until I unplug the controllers, what happens is every time I plug in my controllers and load my profile it only maps the first controller for me! Please help as it is EXTREMELY clutzy to have to map out all the buttons on the other 2 controllers...

Please Log in to join the conversation.

3 weeks 2 days ago #2 by SteveInputMapper
I've been trying to figure this out as well. The profile looks like this, (a very dumbed down version with one button.

[
{
"SourceChannel": {
"$ref": "DirectInputControllerInput.inGenericUSBJoystick.inButton1"
},
"InstanceGuid": "0ffef1fb-e383-428a-924d-529a904adf99",
"Mappings": [
{
"$ref": "ScarletCrush360VirtualBus.outController1.inA"
}
]
}
]

So I've been trying to add a second controller to this, but so far not having any luck. You can see the source channel is,

DirectInputControllerInput.inGenericUSBJoystick.inButton1

And I think the problem happens is because each generic usb device is also called inGenericUSBJoystick so the trick is how to distiguish one from another. The program itself certainly can, but the profile manager can't, as it ends up turning that field to "null" for any 2nd 3rd or 4th device plugged in. There has to be a trick here. I'll keep playing with it.

Please Log in to join the conversation.

Powered by Kunena Forum