..:: PCSX2 Forums ::..

Full Version: XInput Wrapper for DS3 and Play.com USB Dual DS2 Controller
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510
(05-25-2013, 01:08 PM)kimec Wrote: [ -> ]I have the same dongle.
The hardware id is already included in SCP DS3 driver package (see the 1st post).

I also thought that it didn't support EDR (it didn't work with MotionInJoy), until I saw "Enhanced Data Rate" on the package label (http://www.cyberguys.com/images/detail_i...558a-3.jpg
) It makes sense that v4.0 should not be worse than v2.1, right?

Turned out the author of MiJ hasn't added the hardware id to the inf file although some people already requested it. The last version was released like 1 year ago, and there hasn't been any activity since...

So I switched to SCP DS3, and it works great with my PS move navigation controller.

wat's the point of having PS Move to work on pc I wonder?
(05-25-2013, 01:14 PM)feimeng Wrote: [ -> ]wat's the point of having PS Move to work on pc I wonder?

It feels great with the navigation controller (as this guy in this video), or this)

The motion controller works with native BT stack. Use JoyEmu + PPJoy you can control it in any games. It doesn't have lags like the Kinect (always use more than 70% CPU), and its motion is more precise than the wiimote (which doesn't have use built-in rechargeable battery like ps move).
(05-25-2013, 01:35 PM)kimec Wrote: [ -> ]It feels great with the navigation controller (as this guy in this video), or this)

The motion controller works with native BT stack. Use JoyEmu + PPJoy you can control it in any games. It doesn't have lags like the Kinect (always use more than 70% CPU), and its motion is more precise than the wiimote (which doesn't have use built-in rechargeable battery like ps move).

well, I dun play fps game, tat's y I dun see any point of using ps move on pc but the 2nd vid does giv me some concepts, wat a talented guy he is dLaughb
(05-25-2013, 01:08 PM)kimec Wrote: [ -> ]I have the same dongle.
The hardware id is already included in SCP DS3 driver package (I see it in the INF file).

I also thought that it didn't support EDR (it didn't work with MotionInJoy), until I saw "Enhanced Data Rate" on the package label It makes sense that bluetooth 4.0 should not be worse than 2.1, right?

Turned out the author of MiJ hasn't added the hardware id to the inf file although some people already requested it. The last version was released like 1 year ago, and there hasn't been any activity since...

So I switched to SCP DS3, and it works great with my PS move navigation controller.

Interesting because the tech that I spoke to said that it didn't support EDR. Oh well I already ordered another dongle anyway I guess now I have 2, one strictly for the ps3 control and one for other things that I never use LOL
@Sekuroon:
@GeminiFyre:

The USB\VID_0A5C&PID_21E8 hardware id is supported, it's a Broadcom BCM20702 Bluetooth 4.0 device. I have one of these, branded by Belkin - and have used it for testing.

Windows decides which driver to install by ranking, the Broadcom driver will be picked by default as it has a higher ranking. To override this click Force Install when running ScpDriver.

The Bluetooth 4.0 spec is backward compatible with all previous versions, so it does support Bluetooth 2.0+EDR.

@phly95: writing a complete BTH stack would go beyond the scope of the project.

@G-Man: the X360 DInput driver maps the D-Pad to a Hat-Switch, sounds like TF2 has limited support for this.

@Muguetsu: sorry, I missed your post about the ScpServer screenshot. I'm kind of at a loss as to what is happening with your machine. The behaviour is bizarre at best, tbh it sounds like you have a virus / malware which is preventing the ScpControl.dll from being loaded. are you seeing any other strange behaviour on your PC?

@bluejeans: yeah, as MaJor replied - did the same thing on my HTPC.

@azkrath: added an update for your hardware id, see Post #1.

@mintos5: I don't think I can support the Gasia gamepad - I don't own one so testing and support of it would not be possible, there is no way to distinguish it at runtime other than it fails Service Discovery.

@Ba'al: I'll look into adding it.

@justwow: did you read and follow the install instructions? namely around the Microsoft Xbox 360 Controller drivers.

@kimec: The Navigation Controller has the same USB/HID messaging as a DS3 - only the hardware id and BTH name are different. The Motion controller has nothing in common, messaging wise, with a DS3. Consequently adding support for it would be non-trivial.
(05-25-2013, 08:54 PM)Scarlet.Crush Wrote: [ -> ]@kimec: The Navigation Controller has the same USB/HID messaging as a DS3 - only the hardware id and BTH name are different. The Motion controller has nothing in common, messaging wise, with a DS3. Consequently adding support for it would be non-trivial.

Thanks for your answer. So if I understand it correctly, even if you add the hardware id and sign the driver again, you still have to do some more coding, right? (even just to make it work with the buttons, skipping the motion sensing stuff...)

With the native BT stack, my dongle can be paired with the motion controller, but not the navigation controller. The motion controller is paired using the CalibrationTool of the open-source moveframework.

So my questions are:
How does your BlueTooth driver take over the native BT stack?
Is it possible for the driver to let certain hardware devices (i.e the motion controller) to pass-through, that is, talk directly to the native BT stack. If it can work that way, then it'll be the least amount of work as you don't need to implement full support for the motion controller.

Thanks a lot!!
Is it possible to switch a couple buttons? Like, R2 with R1, L2 with L1?
@kimec: yes, it's not just a case of adding the hardware and signing the driver. The HID Descriptor, which defines the format of input/output reports, is identical for DS3 and Navigation Controller [the code does not need to do anything different between the two]. The Motion Controller has a completely different HID Descriptor - Report IDs / format / length / usage pattern, would require code to handle it specifically.

The driver package attaches a custom Bluetooth stack to a dongle, the Windows Bluetooth stack is no longer aware that it is a Bluetooth device. The stacks are independent, so pass-through is not possible.

You can have two dongles installed and running, one for DS3/Nav, the other for native Windows Bluetooth use [which could include a Motion Controller].

@olverine: the driver package does not currently support button mapping directly [other than when used by PCSX2 + Lilypad]. This will probably be available in the next release of the package. [see Post #941].
I don't want to seem like an idiot, but I also don't feel like reading this whole thread.
I have 2 Xbox 360 controllers as well as a DS3 controller. I use one of the X360 controllers to play most of my games. Certain games only use the controller which is considered controller 1 or 0. When I use the drivers here it makes the DS3 controller that controller. I still want to use the X360 controllers as my main controllers, and this gets really annoying after awhile having to uninstall the drivers and replug the controllers in every time I want to play a game that is like that.
If you want an example, Bastion. It only recognizes the DS3 controller.
It's rather odd too, as when I press the Xbox button on my main X360 controller, it says that it is controller one, yet when you look at the actual controller, it says it is controller 2.
I would like to know how to change what controller the DS3 is when configuring games(like Joy0 Joy1 Joy2 Joy3 etc).
I would appreciate a non argumentative reply.
I should probably add that I am using the controller wired and not using bluetooth.
Registered on this forum just for this thread alone, great work Scarlet Crush, this driver works great.

My plug in Belkin bluetooth dongle works OK, but the built in Bluetooth chip in my Sony laptop does not. I don't think the BT chip is supported.

The IDS is:

USB\VID_044E&PID_3010&REV_0056
USB\VID_044E&PID_3010

Please can you add support in the next release?

Is it just a matter of adding the IDS numbers to the list in the BthWinUsb ini file?

Thanks in advance
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510