Controller becoming unresponsive periodically

[Delta-Nom]

I am still having these issues - though strangely only when I am at home. I play at school and at a local coffee shop with no issues whatsoever. Delta, when it happened to you were you simply unable to enter any inputs at all for a given amount of time and then it started working again?

It's hard to explain...like it remembered my last input, then didn't respond to anything else I tried to input for about 3 seconds, which ultimately led to me running off of the edge in titan extreme the other day...and by the time it read new inputs (something like even re-positioning the camera, since it was spinning out of control from my last input) it was too late.

I hope that made a little more sense, I'm struggling to describe what exactly happens, sorry for any confusion.

[Raist]

Stumbled on this problem today when setting up a new Snakebyte PS3 wired controller on my laptop and may have found something that may help some of you guys out. The thing was only $15 at Walmart, so I had to try it... and sure enough it works without having to use MotionJoy or any other modded XB drivers in Win8... but did run into one glitch.

When trying to calibrate the analog joysticks in the Devices and Printers control panel (right click game pad icon, click game controller settings, go to properties for the controller, Settings Tab, and start calibration), it would stop tracking the movement periodically while spinning the left stick. The crosshairs would sometimes just stall for a second here and there. The same thing happened on the Z axis and Rotation phase--one time it didn't even track a button press. It did this on all but ONE USB port--the one with the quick-charge option. 4 USB 3.0 ports on this beast, and the only one it would work properly on was the one that provides quick-charge support, and has a BIOS option to keep that one port powered on even when the system is suspended. It seems this one port sort of plays by it's own rules when it comes to it's power management... which brought me to test something I've run into in the past:

The Windoze Selective Suspend Service may be interfering with the polling of the controller input somehow. Not sure where the responsibility for this glitchiness would fall to... the vendors or Microsoft. But, is a common issue with mouse lockups that shows up on different forums. The work arounds that always come up is to disable the option to power down the inactive USB ports by going into Device Manager, expanding down to each of the USB hubs and going to their Power Management tabs. There is a regedit that can be made under the USB services section to disable the Selective Suspend Service, but in Win8 I don't see one single USB service, so not sure if that can be applied so simply.

Unfortunately, disabling the power save option for each USB entry in Device Manager didn't fix it... had to go one step further. Had to do it for the detected HID entry for the controller as well. Up near the top of the list in Device Manager, expand the Human Interface Devices and check for an entry for your game controller--disable the power save option there. In my case, it was simply listed as a USB Input Device. Note that you will need to do this for each port you routinely plug the controller into. It is possible it may loose the setting after a power down as well, so you may want to double check it if doing this resolves the issue and then it comes back.

Hope it helps some of you guys out. It seemed to be the fix for this controller at least.

[Zor]

I'm using a Microsoft Xbox 360 wired controller.

So yeah, any support person every actually read these forums, or...?

Does anyone ever read the EULA...

If you look into it any mircosoft control pad made b4 a certian date doesnt have the same firmware in it. Thus when mircosoft update thete systems old tech is suddenly ancient tech


This is like gta5 all over again, there is a life for everything even if its still good after that used by date doesnt mean its correctly supported.... Ps3 users do no have this issue, ever! So it is probally the usb turning off functions, like the guy sad above me... But then no one reads a user manual either, a plug in and play device has defualt setting for USBs.. Ps3 controller when plugged into a usb Charger (lets say iphone charger plug) it doesnt charge... Now why is that? Bcus the thing its plugged into doesnt know how to charge it.. Yes shocking it has some type of brain..... Now take mircosoft and there EULA they do not.. I repeat Don't support 3rd party (logitech etc) or Sony control pads... Why, thats another story... FF14 is only on the Playstations, microsoft didnt want to give console infomatiom to another company...

3/4 of the posts in this thread are people complaining that there cheap 15 dollar 3rd party controller doesnt wprk... Well they shpuld of googled about control pads and PCs

And the people complaing for real probally have a USB issue where its getting turn off by the pc bcus ots full charge or not used for some time...

So yea, this is nothing tp do with SE, other than the fact that PS4 testing has started (for Se) so that might be why other 3rd party controllers are not handling it well... They are testing a lot bcus even tho its basically a ps3 to 4 copy an xbox1 or ps4 controller has an uptodate brain ypu could say, and just like most of the world we use digital tv, tho the analog we used too use is still there but the tech we have today cannot do anything with it bcus we have advanced past that stage





Oh gta5 problem I mean is ppl saying the game randomly restarts and crap... Its the CD drive and the only thing they can do is buy a new console or get thetes replaced.. But still to this day ppl are like, nar its fine its just that game... Its just that game bcus its a NEW GEN game

[crc0427]

Find the thread with the port forwards. That fixed the controller issues for me.

[Target808]

I am also having this issue, although it only started appearing its ugly head just recently after the latest major patch. The peculiar thing is that it happens to my PC as well as my wifes PC at the exact same time. Have tried the port forwarding indicated in the earlier posts for one of our machines, tried going off router and a single machine direct to modem, same problem exists. Because it happens to both of our PCs at the exact same moments, I would imagine that it must be on the SE side. We had wireless previously, but switched to Wired controllers since we thought it may have been an interference issue. No dice, wired controller has the same problem. This is a major issue for us. Hopefully they can address it soon.

[Raist]

I found that if I unplug and then replug that same Snakebyte controller, it starts behaving again, so I stopped resetting the power options in Device Manager (even though that worked for me). Was a lot faster to just pull it, wait for the disconnect sound from Winblows, then plug it right back in. YMMV though.

[Julonious]

Is anybody still having this problem? I've tried updating gamepad, as well as the rest of the drivers on my PC, rebooting, changing to windowed from fullscreen, making sure contacts are clean, changing controllers and making sure they work in other games and on the xbox. FFXIV is the only game that the controller becomes unresponsive. Is there something I haven't tried yet? I've noticed that some updates make this problem worse for a while.

[Kajidourden]

It's because you aren't using a ps3 controller.....sony knows....they see all!

[JusteBelmont]

I am also having this problem I have opened the ports that were talked about earlier and have changed my usb power save options however i am still having an issue while using a game pad but never while using a keyboard+mouse has anyone found a fix for sure 100% fix yet?

[nexen]

Hi Guys,

I had this issue about the same time all you guys did. I did some research and my findings are below.

For those who have this issue, open "Device Manager" and let it sit there. Next open the game and go into windowed mode so that you have the game and device manager next to each other.

Now, play the game for a bit and if you notice, every time the controller goes crazy, device manager should "blink" or refresh. If this doesn't happen to you, then no need to continue from here, your issue isn't my issue that caused this.

If you did notice the "blink", then we're having the same issue, such that every time the device manager refreshes, we lose controller responsiveness, but our characters keep moving, or buttons don't respond and yes... if you were tanking Titan Ex, you just ran of the edge. So let's fix this issue (and I must say, I still think there is some code issues in the game that need to address this, so consider this a "workaround").

The thing you need to now do is track down what is causing your "Device Manager" to refresh. To do this, is a long and lengthy process, but to get rid of the "obvious" go a head and update all your drivers to make sure you have latest. Once that is done, if you are still blinking, then you need to expand each tree element and note down the devices that are there. The "Blink" should add or remove one of these every time it "Blinks". You must keep going through all the items here and wait for the "blink" to occur and make sure that the item you looked at didn't disappear or reappear. Once you track this down, you need to figure out a way to disable it.

For me, it was actually because I was running "PlayOn" which is a DLNA streaming service and located under "Software devices" in device manager. At some point in time, Microsoft pushed an update that "PlayOn" wasn't happy with causing it to constantly crash and refresh my device manager. Stopping the PlayOn service fixed my issue. Now, there are a lot of other ones out that that behave the same way, so your PC is most likely different.

NOTE: There may be more than 1 issue in your device manager, so if you know what all the items are, you can disable everything until it doesn't refresh, then re-enable and see what is causing the problem also.

The real problem... (hopefully SE reads)
I think FFXIV has a device enumerator such that every time a device is connected it triggers the controller code to see if FFXIV has to change controllers. Somewhere in that code, it stops responding to the currently connected controller while it determines if it has to switch controllers. Not sure how to log a bug, but being familiar with how software is built, I am fairly sure this is what is "truly" happening.

Anyways, this resolved the issue for me and I hope it helps all of you. It answers all the basic questions like why it was so sporadic.

Good Luck!