@Scarlet.Crush
I finally got around to testing your bus driver fix for XBCD. Works great. Now I can map the controls however I need them
Been playing Dark Souls: Prepare to Die edition with this setup with minor issues. Game didn't seem to work right away with Xinput, so I had to fiddle around with the XBCD utility until I got the button assignments correctly mapped. After that I haven't had any issues. Only annoyance is the need to flip the triggers between analog and digital when I want to play a driving game, but that's not that bad.
Installed bt driver and it failed to install driver for virtual x360pad. Am I missing something? I use Vista SP2, wired driver works fine.
Alien, can you give some details on HOW it failed, what it said when it failed, etc?
I probably messed something up during a previous uninstall. When I attempt to run ScpDriver.exe, it gives me this message "Could not find a valid configuration." and the only option is to exit. Is there a way to force it to start a fresh installation?
MaJoR, I got "Install Succeeded" with no errors during ScpServer istallation, but my dualshock doesn't work without a cable and in Device Manager "XBOX360 Controller" has an error "This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)".
(03-27-2013, 05:03 AM)Alien Wrote: [ -> ]I think you should just pair up your ds3 with bluetooth dongle. At least it worked that way with MotionInJoy.
I want my DS3 to remain paired up with my PS3 though. I remember MotionInJoy had a "Disconnect" button that allowed you to unplug your DS3 without turning on the paired PS3.
Hey guys, I'm currently away from home with limited internet access. I'll be back home sometime Sunday and will look into issues and Bluetooth updates as soon as possible.
A few people have now reported a "Could not find a valid configuration." problem while running ScpDriver. The code used for OS detection has not changed, so don't know why this is occurring. If you are experiencing it can you verify that the System panel is displaying the version correctly (see screenshots in Post
#601), and also if PCSX2 is displaying the correct OS version in it's log.
Thanks Scarlet.Crush for this. I just got Dirt 3 on sale off steam. I have used motioninjoy in the past without issues (although I always hated there online tool) this time around I installed the latest drivers from them and played the game only to get a very random rapid camera shaking (left to right). After doing some digging I found out it was from the motioninjoy driver seemingly giving random readings from the joystick. I started to dig around for another solution and found this thread. After installing the latest RC drivers (using USB) and testing that the joystick was working with your tool I went to try out Dirt 3 and you know what.....it worked f*cking perfectly in fact better than I ever remembered motioninjoy ever working. It seemed like it was more responsive. I used to have to calibrate the MiJ driver every time I would disconnect and reconnect the controller and with yours I never had to calibrate it.
Very nice job, thanks for this.
(03-28-2013, 03:18 AM)Scarlet.Crush Wrote: [ -> ]Hey guys, I'm currently away from home with limited internet access. I'll be back home sometime Sunday and will look into issues and Bluetooth updates as soon as possible.
A few people have now reported a "Could not find a valid configuration." problem while running ScpDriver. The code used for OS detection has not changed, so don't know why this is occurring. If you are experiencing it can you verify that the System panel is displaying the version correctly (see screenshots in Post #601), and also if PCSX2 is displaying the correct OS version in it's log.
The System control panel and PCSX2's emuLog.txt correctly display my 64-bit version:
Microsoft Windows 7 Home Premium Edition Service Pack 1 (build 7601), 64-bit
But ScpDriver displays it as a 32-bit version:
SCP Bluetooth Driver Installer 0.8.0.100 [3/28/2013 12:22:27 AM]
Detected - Microsoft Windows 7 Home Premium Service Pack 1 (6.1.7601.65536 x86)
Could not find a valid configuration.