Generally the third party controllers don't work over bluetooth with these drivers.
(10-29-2014, 12:12 AM)Blyss Sarania Wrote: [ -> ]Generally the third party controllers don't work over bluetooth with these drivers.
Alright that's what I expected, thanks for the feedback. Do you know of any alternatives that may work?[/align]
Motioninjoy MAY work, but motionijoy is spy/adware. However you can install the MiJ driver and use it with Better DS3 which is not spyware. That's about all I know of.
Yeah I've had mixed results with motioninjoy but I will try it again. Thanks for your help!
huh dunno i have an ndivia with 3d vision and don't have problems. But as long is fixed is good
(10-29-2014, 09:48 AM)ultimategrayfox Wrote: [ -> ]huh dunno i have an ndivia with 3d vision and don't have problems. But as long is fixed is good
I have tried repluging all my dongles/wires and ended up with Bluetooth adapter connected via front USB2. Reinstalled all drivers, and yesterday I've had long session in Castlevania 2 with 3D Vision without any issue... Hope it's permanent
As far as I can tell, the controller is working fine and connected. It's a PS3 controller, and I keep it plugged into my PC with the standard USB cable.
However, what doesn't seem to be working fine is using this with PCSX2. For one thing, any attempt to configure plugins (even just to change to a different set of plugins) while the XInput1_3.dll is in the right directory (with the emulator's .exe) results in PCSX2 crashing immediately with no error message (not even in the log). I was able to at least set it to use the provided version of lillypad that I'm supposed to use with this by removing said dll, but while I can enter the configuration menu for it while it's like that, PCSX2 freezes or crashes (the former being distinguished by me needing to end it with the task manager, although I may be remembering it wrong and a mostly unrelated issue was the one that froze) upon trying to leave the configuration menu. My version of PCSX2 is the latest 'stable' version, but I don't know if I believe the 'stable' part anymore, especially with how often I see references to the developer versions when I look around here. (that is, I have revision 5875.)
Since there's no error in the logs, I can't really begin to figure out where the issue lies, so I figured I would start here. Some insight from others can help me narrow down what could be causing it.
I did see earlier something about removing MotionInJoy's drivers, but while I could find a driver with a hardware ID that roughly corresponded to what MIJ said my device was, there wasn't an option in the uninstall driver menu to 'delete software drivers'. I suppose they could be installed to the controller's new identity as a fake XBOX360 controller, but the driver details say it currently has a Microsoft driver.. though with SCP installed I would think that they should be showing up under a different developer name. I've checked a few other devices with generic names (it seems to like calling the DS3 'HID-compliant device' xor 'HID-compliant game controller' when it's not being called something else by another driver, and in fact it likes to do that for almost anything that doesn't have a driver from someone else), but none of them show up as having anyone else's drivers either. The game I'm trying to run has a sequence that requires pressure-sensitive buttons. I could jury-rig a solution with the right knowledge, but I'd rather use something that was designed for this sort of thing, even if I have to install something, realize it's crap, uninstall it, find a much better thing, install that, find out that the crappy one may have left something behind, uninstall the better thing and try to remove the drivers from the crappy thing if I can find them (though I did tell MIJ to remove its drivers from the controller and USB dongle and made sure they were gone -before- I actually uninstalled it, so I may have just been waving a dead chicken around for no reason), reinstall the better thing, find out there's a higher version (I didn't quite check), perform my version of the upgrade process (uninstall, replace the files, reinstall), then reboot a few times all among that. It's probably working fine besides this one little thing.
That went on a lot longer than I intended. Should I update my PCSX2 to the latest development version just in case? Or, alternatively, Abort, Retry, Fail?
EDIT: Latest dev version downloaded and placed in a clean folder (with the BIOS from the earlier installation, gathered carefully from my own PS2 of course). I put the Xinput dll and the modified lillypad plugin in the places they go and it crashed upon trying to configure too. It couldn't even get through its first-time configuration. It did have some error messages about a bunch of other plugins (DEV9ghzdrk.dll was both not found and not a valid dynamic library, GSdx32-AVX2.dll (error -1073741795: unknown error c000001d), xpad.dll (error 998: invalid access to memory location. tried admin access, it doesn't change that), and then it stopped), but as before nothing came up regarding the actual reason for the crash.
You shouldn't need to be moving around the xinputdll or using a modified lilypad for these to work with PCSX2. What are you trying to accomplish exactly?
I shouldn't? They came with the SCP files (they're in D:\Program Files\Scarlet.Crush Productions\Win32, although that could be part of the problem, I have a 64-bit version of Windows 7.. as for why the directory it's under just 'program files', it's because at one point I was installing a program of lesser importance and just switched the drive letter without touching the path, and it had no idea that it should be going under (x86). ) and I read.. somewhere, now I can't even remember.. that I should use them. Whether Lillypad accepts pressure input normally is something I'm getting mixed messages on. Then there's the fact that the latest version on the forum is .10 or something, but the one that comes with the stable release is .11. Which isn't really related but seriously what's up with that?
I'll put both of the files away (by which I mean remove them from the PCSX2 stuff) and see if Lillypad will take the pressure sensitive inputs right.
EDIT: Lillypad still doesn't seem to want to acknowledge the pressure sensitivity, and if I try to find it under 'dualshock 3 native mode', the controller doesn't show up (I thought it might). There are a couple of listed controllers that both seem to respond to the same input (just one controller somehow split into two), but only the L2 and R2 buttons are pressure sensitive, when what I need is at the very least the O button to be that way instead. Libsub is present, though I don't know if I need to do some additional steps beyond the installation instructions for it. EDIT 2: Poked into its inf-wizard program and decided to try going through it and see what would happen. I'll be back after another reboot. The initial installation instructions I found were for some form of linux distribution that resides on windows or something. I think it was, it had penguins in the logo and the title. So I suppose that since the last half wasn't relevant to my needs, I may have missed something that would have lead to me discovering the correct next step.