Can anyone help me please. I' ve been searching the web for a week now and i cant find a solution to my problem. Thats why i registered here and asking for help. Im from the Netherlands so pardon my English if u see any grammar errors. Here is the problem:
I've got a ds3 original + 4.0 dongle + cable (not an original ds3 cable)+
os Windows 8.1
Everything used to work fine and after eacht windows update i would re-install the drivers and continue playing wireless. For charging i would use the cable.
Now i cant charge anymore. After a re-install i can still play it wirelles but not with the cable nor charge with the cable. I tried removing all drivers and installing again but the same effect. In device manager i can see a yellow mark by the usb. There is a explanation in dutch but translated it says" unknown usb device (request for devicediscriptor failed)". At he moment the battery is at medium so i can play but when its low i cant charge it anymore. WIndows should install the drivers automatically before installing xinput wrapper but it cant recognize the ds3. PLease help or im forced to buy a microsoft controller
update: problem solved. turns out that the cable was a problem. bought a new one
I've got a ds3 original + 4.0 dongle + cable (not an original ds3 cable)+
os Windows 8.1
Everything used to work fine and after eacht windows update i would re-install the drivers and continue playing wireless. For charging i would use the cable.
Now i cant charge anymore. After a re-install i can still play it wirelles but not with the cable nor charge with the cable. I tried removing all drivers and installing again but the same effect. In device manager i can see a yellow mark by the usb. There is a explanation in dutch but translated it says" unknown usb device (request for devicediscriptor failed)". At he moment the battery is at medium so i can play but when its low i cant charge it anymore. WIndows should install the drivers automatically before installing xinput wrapper but it cant recognize the ds3. PLease help or im forced to buy a microsoft controller
update: problem solved. turns out that the cable was a problem. bought a new one