PS3 Controller issue with Windows 8.1

[nprevail]

Has anyone experienced/fixed any issues with their PS3 controller in Windows 8.1?

From Windows 7 to Windows 8, I've had no issue of using a PS3 controller via (offline) Motion In Joy.

I updated to Windows 8.1, and Windows doesn't recognize the drivers and manufacturers when it's plugged in. "PS3 controller" shows up in "Devices and Printers" as well as Device Manager, but it doesn't connect. Also, Motion In Joy and Better DS3 were unable to recognize my Bluetooth USB receiver.

Again, the PS3 controller and bluetooth receiver worked perfectly before Windows 8.1 upgrade.

Any advice?

[Street666]

Yes, I'm also experiencing this problem with Windows 8.1
Let's wait for an update to correct this problem.

http://forums.mydigitallife.info/threads/48959-Windows-8-1-not-charging-PS3-Controllers

http://www.eightforums.com/drivers-hardware/33687-windows-8-1-does-not-charge-ps3-controller.html

(I'm using google translator)

[Baha]

So i guess it's better to stay on 7

[askel]

windows 7 or linux?

[1337]

kjk

[Johnny Rossi]

I want to test the Windows 8.1

[nprevail]

Yeah, my recommendation: stick to Windows 7.

I only jumped onto Windows 8 because there was a "loop-hole" deal to get it for only $15.

For anyone elses reference, PS3 controller works for Windows 7 and 8, but not 8.1.

[Satoru]

1) uninstall motion in joy
2) buy an xinput compatible controller

Easier solution and you have the added benefit of not having a Chinese Trojsn able to execute arbitrary code remotely on your system

[nprevail]

I use the offline version of Motion In Joy (so no viruses, ads, etc.). Also Better DS3 and SCP DS3.

None of them work.

[Street666]

The solution:

http://answers.microsoft.com/en-us/windows/forum/windows8_1_pr-hardware/playstation-3-controller-and-headset-charging/b48208f3-d7d6-4e33-9ac8-04836e4f1c4b

[nprevail]

I did this, it charges my controller, but it doesn't respond to any of the PS3 controller's buttons or D-pad movement.

On the second page of the link you sent, they concluded that it charges but still doesn't not respond/work on Windows 8.1.

[nprevail]

Okay, so this video pretty much solved the problem:

YouTube™ Video: Better DS3 & No Need For DS3 Tool: Manual Driver Installation in Windows 7 

Views: 399,044

PS3 controller 64-bit drivers: http://www.mediafire.com/download/wjgegko4y8eqyw6/PS3_x64.zip PS3 controller 32-bit drivers: http://tinyurl.com/lsweszj Note: When you install the drivers for a...

Be sure to read the description.

I guess what happened for my system, is that after I upgraded to 8.1, it must have deleted my previous PS3 drivers. You need the drivers in order for Windows 8.1 to detect it, so just reinstall them through that youtube post.

[Satoru]

Great so the solution for 'not charging' is to run unsigned drivers from mediafire huh?

Seriously are people so stupid these days that they NEED theri PS3 controllers.

[nprevail]

So what controller do you suggest? Especially if you play 4-player local co-ops and emulators?

[TheZemnian]

Here's how I fixed it-

Install motioninjoy ver. 0.6.005, then copy the contents of the motioninjoy driver folder to your HD and uninstall motioninjoy. Go to Device Manager after you've plugged in your bluetooth dongle and ps3 controller, and manually install the motioninjoy drivers. Download Better DS3 and you can use it without any trace of motioninjoy on your rig.

*edit*: I see now that nprevail posted the same fix.

[ampere51]

Thank You!
It is really works fine.
Do not forget install driver for BlueTooth as posted in video clip by nprevail.

Better DS3 is really Better.

Originally posted by Sensei-Musurugi:

Here's how I fixed it-

Install motioninjoy ver. 0.6.005, then copy the contents of the motioninjoy driver folder to your HD and uninstall motioninjoy. Go to Device Manager after you've plugged in your bluetooth dongle and ps3 controller, and manually install the motioninjoy drivers. Download Better DS3 and you can use it without any trace of motioninjoy on your rig.

*edit*: I see now that nprevail posted the same fix.