(11-14-2013, 06:20 AM)Wigginns Wrote: [ -> ]Are you certain that their aren't any issues with the cord or USB port? That sounds like what might cause that issue.
(11-14-2013, 06:48 AM)Huesoman Wrote: [ -> ]In page 126 (posts #1252 y #1257) other people have issues with your BT dongle (USB\VID_054C&PID_0268&REV_0100) maybe it could help you. BTW,
it is possible that your Bluetooth doesn't support EDR so it can't work properly, you can check it by running the "SCPUser" application at: C:\Program Files\Scarlet.Crush Productions\Win64 (or win32)
if the rumble function works (I mean the vibration function) without the usb cable (I mean wirelessly) then your BT dongle doesn't support EDR; it rumble doesn't work then I don't know what could be the problem.
Im connecting the PS3 device via a wired connection and the cable works absolutely fine for my PS3.
(11-14-2013, 12:54 PM)rich9119 Wrote: [ -> ]Im connecting the PS3 device via a wired connection and the cable works absolutely fine for my PS3.
Good, I was refering to the Bluetooth issue, if it doesn't register any buttons presses but the vibration function works fine then the problem is the BT doesn't support EDR which is needed to play wirelessly.
(11-14-2013, 04:50 AM)RetroGaming Wrote: [ -> ]Hello!
So my dongle (recommended by people already successful so it should be compatible) finally came and I started going through the process set up by Scarlett.Crush on page one of this thread.
After a while I was able to get the ps3 controller working fine via USB, but have not yet had success via bluetooth.
If anyone can help me out I'd greatly appreciate it. You'll have to tell me exactly what you need either from me or for me to do (even through PM is fine to no clutter the board). I'm tech savvy so hopefully it shouldn't take too much troubleshooting!
Thanks ~
Chris
See if I can give some info...
Here is the dongle I'm using:
http://www.amazon.com/Asus-Mini-Bluetoot...oth+dongle
I'm using Win 8. I've got it working fine via USB. It looks like the bluetooth isn't being picked up when I run the SCP tool. When I check the SCP monitor there is no address on the left.
I do have onboard bluetooth so I don't know if that needs to be somehow cutoff or if that doesn't matter.
Maybe it is some kind of initial driver issue when the dongle goes into the USB the first time, or maybe something to do with the .inf idea i saw somewhere in the thread?
Any help appreciated!
(11-14-2013, 07:09 PM)RetroGaming Wrote: [ -> ]I do have onboard bluetooth so I don't know if that needs to be somehow cutoff or if that doesn't matter.
Wait, your bluetooth is still working for other devices?
(11-14-2013, 07:17 PM)tolstoy635 Wrote: [ -> ]Wait, your bluetooth is still working for other devices?
Ya why wouldn't it? I bought the dongle for the strict pairing with the ps3 remote.
(11-14-2013, 07:32 PM)RetroGaming Wrote: [ -> ]Ya why wouldn't it? I bought the dongle for the strict pairing with the ps3 remote.
Okay, if you only have one BT dongle, once the drivers were correctly installed , it won't be able to pair with anything except the ps3 remote. If you have two dongles, one can be made for your ps3 controller, and the other for your keyboard mouse etc.
So if u have one dongle and it is still pairing with other devices the driver didn't install, in that case I would suggest starting your PC (Google starting windows ____ <-- your OS in advanced startup no driver signature enforcement ), do that and install the Bluetooth driver and try again. OK if it installs correctly, in the device manager the Bluetooth should show up right above your controllers with a funny name that's NOT the name of your dongle brand (eg, asusm iogear etc)
Edit: are you using the Asus BT 211? read a lot of the thread so ce I am using the Asus BT 400, try unplugging and replugging once the drover is installed and check the host address, may pop up, one user also claimed his bt211 worked after plugging it into his USB 3.0 port....
(11-14-2013, 07:53 PM)tolstoy635 Wrote: [ -> ]Okay, if you only have one BT dongle, once the drivers were correctly installed , it won't be able to pair with anything except the ps3 remote. If you have two dongles, one can be made for your ps3 controller, and the other for your keyboard mouse etc.
So if u have one dongle and it is still pairing with other devices the driver didn't install, in that case I would suggest starting your PC (Google starting windows ____ <-- your OS in advanced startup no driver signature enforcement ), do that and install the Bluetooth driver and try again. OK if it installs correctly, in the device manager the Bluetooth should show up right above your controllers with a funny name that's NOT the name of your dongle brand (eg, asusm iogear etc)
My desktop PC came with onboard bluetooth. I bought this dongle because a) my understanding was that the onboard might not work well and b) so that I could keep pc for pairing with other devices. Dongle came with driver disc but it was bent and won't work. Can't get the ones off Asus website to work either. Not sure if Windows is properly installing what it needs on its own when i plug the usb dongle in from fresh.
Not familiar with "(Google starting windows ____ <-- your OS in advanced startup no driver signature enforcement )". How exactly do I need to do this?
Thanks for the help btw!
(11-14-2013, 08:06 PM)RetroGaming Wrote: [ -> ]My desktop PC came with onboard bluetooth. I bought this dongle because a) my understanding was that the onboard might not work well and b) so that I could keep pc for pairing with other devices. Dongle came with driver disc but it was bent and won't work. Can't get the ones off Asus website to work either. Not sure if Windows is properly installing what it needs on its own when i plug the usb dongle in from fresh.
Not familiar with "(Google starting windows ____ <-- your OS in advanced startup no driver signature enforcement )". How exactly do I need to do this?
Thanks for the help btw!
Hey, so I'm no expert, only got mine working a couple days ago, but since nobody is replying, i am trying my best to help. That being said ....
you will need to take a look at the device manager to see if windows is installing the asus bT properly, look for the big blue bluetooth symbol, if it is there, that should be the original driver, and thus not the correct scarletcrush driver.
In my case, I had to start windows with driver signature enforcement turned off. How to do that will depend on your operating system. for example if you have windows 7 - look here
LINK
Once you have windows started with DSE turned off, you can try to install the ps3 bluetooth driver again.
After thats done, take a look at your device manager, my bluetooth dongle now reads "BCM20702a0" rather than "ASUS BT400". It actually reverts back to its original driver sometimes, so I have to click ROLL BACK DRIVER in the properties menu.
Assuming the driver is now installed, start the SCP service and see if you have a host address. Try to connect via USB, then unplug, and reset the PS3 controller with a paperclip (tiny button at the bottom of the controller). Hold it a few seconds and let go, see if it connects. If it does not connect, you can attempt using the BT pair tool, it can be found on this page -
http://forums.pcsx2.net/Thread-XInput-Wr...er?page=56
Read the last few pages of this thread p 172-174 where I explained to other users how to use it. too lazy to write more
(11-14-2013, 09:01 PM)tolstoy635 Wrote: [ -> ]Hey, so I'm no expert, only got mine working a couple days ago, but since nobody is replying, i am trying my best to help. That being said ....
you will need to take a look at the device manager to see if windows is installing the asus bT properly, look for the big blue bluetooth symbol, if it is there, that should be the original driver, and thus not the correct scarletcrush driver.
In my case, I had to start windows with driver signature enforcement turned off. How to do that will depend on your operating system. for example if you have windows 7 - look here LINK
Once you have windows started with DSE turned off, you can try to install the ps3 bluetooth driver again.
After thats done, take a look at your device manager, my bluetooth dongle now reads "BCM20702a0" rather than "ASUS BT400". It actually reverts back to its original driver sometimes, so I have to click ROLL BACK DRIVER in the properties menu.
Assuming the driver is now installed, start the SCP service and see if you have a host address. Try to connect via USB, then unplug, and reset the PS3 controller with a paperclip (tiny button at the bottom of the controller). Hold it a few seconds and let go, see if it connects. If it does not connect, you can attempt using the BT pair tool, it can be found on this page - http://forums.pcsx2.net/Thread-XInput-Wr...er?page=56
Read the last few pages of this thread p 172-174 where I explained to other users how to use it. too lazy to write more
Ok I'll give it all a runthrough and get back to you.
Thanks!
(11-14-2013, 09:30 PM)RetroGaming Wrote: [ -> ]Ok I'll give it all a runthrough and get back to you.
Thanks!
Well unfortunately no luck. I do see still that I get "Unknown blue tooth devices peripheral" listings in the Device manager. Guess I'm not sure what to do here. Couldn't even get the pairing tool to work and function like it should (had an unpassable error screen).
Hmmmm.... Bet it is something simple. I've gutted it and tried redoing it so many diff ways / times though not sure where to go from here. Sadly maybe I'll have to try and have someone walk me through it step by step or something of that nature..