pSX Analog+rumble problem

[NexXxus]

when i configure my Dualshock 2 i plugged in with a ps2toUSB converter and chose SCPH-1150: Analog+rumble i get an error:

.\src\win\joystick.cpp.684: 'hres' returned DIERR_NOTEXCLUSIVEACQUIRED: The oper

and the controlls won't work unless i use SCPH-1010: Normal Pad.


i configured everything correct but where is the problem?

pcsx2 works fine with analog and rumble btw

edit: when i select SCPH-1200: Dualshock i get those errors too, but it works at least.

[Gamesoul Master]

Well... SCPH-1150 is the prototype pad for the SCPH-1200 that never quite made it, so it may not always work quite as well, and certainly it never seems to be useful over choosing SCPH-1200. So that part is at least answered for you... stay away from SCPH-1150...

As for the main problem... have you tried updating your adapter drivers, or at least using different ones (if you're using Microsoft drivers, try the manufacturer's drivers, and vice-versa). Is your DirectX installation up to date? Also, if you have rumble enabled, disabling may fix the problem too (pSX is still a little touchy about some controllers/adapters and rumble).

[patrickp]

Quite simply, SCPH-1150: Analog+rumble doesn't work for most pads, NexXxus. You need to use SCPH-1200: Dualshock for games that support analog controllers and rumble, or SCPH-1010: Normal pad for games that don't.

And, as GM says, your error message most likely indicates a problem with your controller driver or your DirectX 9.0c installation (AFAIK DIERR is a Direct Input - part of DirectX - error). Have you checked that your controller is properly configured in Gaming Options (or whatever it's called) in Control Panel?

[Gamesoul Master]

Well, I looked around for information on that problem. Seems most people (when coding their apps) encounter that problem when trying to use Force Feedback in their games. Meaning... the solution is probably one of the three I mentioned before. Most of the responses I found were the type that would probably interest pSX Author more, since they were solutions involving changes to the coding...

On your end of things... it seems updating/changing your gamepad drivers or disabling rumble one way or another are your two best chances of fixing/bypassing the problem.

[NexXxus]

directX is up2date of course.

for the adapter: i installed the driver from the mini-CD wich was contain in the package.
or does someone find drivers for "Twin USB Vibration Gamepad" in the internet ??
its just a adapter to connect 2x PS2 Dualshock Controllers to USB.
The microsoft driver doesn't support rumble.

currently installed driver is:

Twin USB Vibration Gamepad
3.39B (2005.08)
Copyright (C) 1999-2006
All right reserved

no manufacturer named :\

[patrickp]

Do you mean DirectX 9.0c is up to date, NexXxus - and by that, I mean updated in the last few months?

Microsoft actually update it every couple of months or so, and pSX won't even run on the original release of DirectX 9.0c.

What happens if you uninstall the adapter driver - I know you won't get rumble without it, but does it fix the problems?

Funny, isn't it? I've had a few adapters and controllers that don't get identified by name and manufacturer in Windows, but do in Linux...

[Gamesoul Master]

I've searched around and couldn't really find any information on it, except for a couple other people with, seemingly, the same adapter, trying also to find updated drivers for it. This is one of those occasions where you'd pretty much have to read the box it came in to get any more information. There has to be some kind of part number or something on that box to identify the controller.

Try following my recommendations (one of which patrickp echoed above, and is probably the easiest and possibly most effective one to try).