Controller stops responding, then returns (win10 64bit.)

I don't appreciate this being moved to Resolved, when it has not been resolved. If you need more information please let me know.

.........Thanks

http://forum.square-enix.com/ffxiv/t...in10-64bit.%29

In the previous thread, where exactly did you check your power settings? The individual port settings are in an entirely different area compared to your normal sleep settings.

Just in case you haven't yet, here's the steps to try and test your USB port settings individually (just disregard if you've already tried this in the other thread):

Winkey or click on the Cortana search (if you have it)
- Type "Device Manager" and select that option that comes up.
- Under the "Human Interface Devices" area go through all of the items listed as "USB Input Device"
- Plug in your controller and find out which one gets added. If you're not sure right click on the items and select "Properties ---> Events" and find out which one has a timestamp that's the most recent.
-Once you find the right item go to "Properties ---> Power Management -----> Uncheck 'Allow the computer to turn off this device to save power'
- Click Ok

Try your controller for a bit then and see how things go. If it is a power management issue that should clear it up. If it's not we can keep working at it.

Edit: Also wanted to ask: Are you playing Fullscreen or one of the Windowed options? If you're using Fullscreen it's possible that the controller isn't being recognized as a constant process.

I'm pretty sure I have already done this as well, but I'll double check once I'm done with work.

The one I went to before was...advanced power settings > usb.

This has been an ongoing issue for my wife and I, for this game, and this game alone, and it happens at literally the same exact time on both of our machines which I find odd.

FFXIV seems to manage the keep-alive commands to hardware poorly. There have been numerous issues reported through various forums of not just usb devices, but the graphics cards as well going to sleep mid-game.

Ya, I just did a remote into my computer. They are all like this.

https://dl.dropboxusercontent.com/u/18215724/power.JPG

Oh I didn't catch your edit, no I use window mode.. specifically boarder-less window mode., as I'm generally playing with 3 monitors running.

Yeah, I'm stumped here. I tried out a few controllers on my PC today to see if I could replicate and I could not. Since you're doing PC...maybe learn KB+M? /shrug

Any other ideas?

Have you tried it in different ports? If you have it in a front port, try it in a rear port or vice versa. Depending on your computer it is entirely possible that the different ports have different amounts of power available to them to give to whatever is plugged in. Also if you have USB 3 ports (blue ones) try those as although your controller probably isn't USB 3, the ports themselves should be able to give more power than a standard USB 2 port (if it is a power issue...)

I've had this problem on 2 different machines both running Windows 10 (and previously 8.1). I was able to 'fix' it, but the solution was ugly and Windows updates sometimes undo it.

This is based on advice I eventually found in another thread. For that individual the specific process was different, but essentially to diagnose the problem open up device manager and show hidden items. You have to tediously wait for the problem to occur and then check to see if the device manager refreshed at the same time. If it did, then a process is starting/ stopping/ rebooting and interrupting the controller (this probably shouldn't actually cause a problem, but somehow with XIV it does).

For me it was always the Volume Shadow Copy service (VSS), which is a key component of the system restore feature in Windows. I personally never use this and don't anticipate ever using this, especially with nearly everything important being backed up to remote servers. Disabling this process (and preventing it from running on startup) solved the problem for me.

If you don't use system restore and want to skip the diagnostic phase and jump straight to the potential fix, you can just open task manager, click on the 'Services' tab, click 'Open Services' on the bottom of the window, find 'Volume Shadow Copy' (sorting by name helps), right click and select properties, and change startup type to 'Disabled'.

This should stop the process and prevent it from ever starting back up without specifically changing it yourself (though as I said a Windows update reset it on me at least once). Hope this works for you!

Quote:

---

Originally Posted by worldofneil

Have you tried it in different ports? If you have it in a front port, try it in a rear port or vice versa. Depending on your computer it is entirely possible that the different ports have different amounts of power available to them to give to whatever is plugged in. Also if you have USB 3 ports (blue ones) try those as although your controller probably isn't USB 3, the ports themselves should be able to give more power than a standard USB 2 port (if it is a power issue...)

---

Thanks, ya I have tried multiple ports and multiple devices. Right now I'm just using the ps4 controller, since it is supposed to be supported by ffxiv now, no ds4 or anything like that running.

Quote:

---

Originally Posted by Nutz

I've had this problem on 2 different machines both running Windows 10 (and previously 8.1). I was able to 'fix' it, but the solution was ugly and Windows updates sometimes undo it.

This is based on advice I eventually found in another thread. For that individual the specific process was different, but essentially to diagnose the problem open up device manager and show hidden items. You have to tediously wait for the problem to occur and then check to see if the device manager refreshed at the same time. If it did, then a process is starting/ stopping/ rebooting and interrupting the controller (this probably shouldn't actually cause a problem, but somehow with XIV it does).

For me it was always the Volume Shadow Copy service (VSS), which is a key component of the system restore feature in Windows. I personally never use this and don't anticipate ever using this, especially with nearly everything important being backed up to remote servers. Disabling this process (and preventing it from running on startup) solved the problem for me.

If you don't use system restore and want to skip the diagnostic phase and jump straight to the potential fix, you can just open task manager, click on the 'Services' tab, click 'Open Services' on the bottom of the window, find 'Volume Shadow Copy' (sorting by name helps), right click and select properties, and change startup type to 'Disabled'.

This should stop the process and prevent it from ever starting back up without specifically changing it yourself (though as I said a Windows update reset it on me at least once). Hope this works for you!

---

I'll have to try this out, this weekend. My windows 10 was an upgrade from my 7pro, I didn't do a fresh install.

----------------------------------------------------

Please don't move this thread till I'm able to try this.

Before you do a fresh install. Try heading to device manager and disabling the "Microsoft Device Association Root Enumerator"

This fixed the issue for me.

http://i.imgur.com/g6CnlcR.png

Quote:

---

Originally Posted by Jekyll

snip

---

Giving this a whirl today, before I try the other thing.

Still trying this, but so far it kind of seems like disabling the Root Enumerator is working... I'll post again in a few days, since If I am afk when the issue occurs, I won't notice it, so takes a bit longer to test.

Just curious what controller you are using and if your using any applications for it?

Quote:

---

Originally Posted by Genaxx

Just curious what controller you are using and if your using any applications for it?

---

Quote:

---

Originally Posted by Imoen

Right now I'm just using the ps4 controller, since it is supposed to be supported by ffxiv now, no ds4 or anything like that running.

---

Just base PS4 controller. Wife is using a Logitech, no software.

That might be the cause then since the DS4 doesn't work well on windows without an emulator.

I've know them to have disconnection issues when using bluetooth and wired at the same time eg. Your using bluetooth but the battery is low, so you plug in the usb cable and play. It will then randomly disconnect. Sp id your battery starts dying you need to close FFXIV, disconnect the controller by pressing PS & Options, then plug in the usb. Or just use wired the whole time.

I wiuld recommend installing either DS4windows or Input Mapper.

Quote:

---

Originally Posted by Genaxx

snip

---

Nah, I tried DS4 before, I thought maybe that would help, it didn't. Nice thought though.

Trust me when I say It's not the controller, or how it is connected. This is literally the only game that has the issue. I could use any of the controllers , with software or not, with any other controller supported game I have installed and its no problem.

It is happening on multiple machines, my machine, my wifes machine, both my work machines. Same game, Same problem, Same timing, different hardware, different controllers, different configs, the only similarity between all the machines is windows 10 64 bit Pro ,this game, nvidia cards, and intel. The game is still playable, its a minor yet highly annoying issue.

I actually find it a bit annoying that I even have to open device manager to attempt to solve an issue that is related to a video game, in my long years in playing games, I have never had to jump through so many hoops for something as simple as using a direct input or xinput controller. (Well ok, maybe networking in win 95 for diablo)

They really didnt help at all? Maybe its an issue with win 10 then. Have you tested on 8?

Quote:

---

Originally Posted by Genaxx

They really didnt help at all? Maybe its an issue with win 10 then. Have you tested on 8?

---

Nope only windows 10 64bit pro. Don't really have a way to test it on another OS. I don't recall having the issue pre heavensward on windows 7.

After doing some googling, seems that win 10 has a controller driver error so your not the only one.

Take a look at this and see if it helps: http://forum.halomaps.org/index.cfm?...&topicID=49128

I had this exact issue on a laptop running Windows 10 Home x64 with an Xbox One controller, suddenly started happening after having been fine for weeks of playing on that computer. Disabling the enumerator in Device Manager fixed it for me.

Ya I haven't got to fully test the Enumerator thing yet, since I've been crunching at work, however my task is done so I'll be able to try this out in more length of time.

So day one, full day, not exactly the best experiment as I was grinding gathering items with waits in between (in other words a a lot of AFK time) Tomorrow I plan on rolling more battle content, which will give me a better idea of if the enumerator thing is working, now with that said, on our network so far my wife hasn't reported any issue since we changed one machine on our network to off... which I think is strange, In other words we only changed my machine to enumerator being off, on the same network and suddenly she hasn't had problems.. but again, ill try it in more battle content tomorrow and sunday, I'm expecting at least a 16 hour play period minimum as I wind down from crunch, so that will give me a better idea of if it is working, thanks for all the responses here, I will get back Monday night or Tue Morning CDT to verify or not.

If a GM or Forum Moderator reads this thing, I would like to note that I only disabled "Microsoft Device Association Root Enumerator" (device manager> software devices) for one of my machines on the network/homegroup. We haven't noticed it on any of the machines since the change on the one device. So I don't know if it was the latest patch or my change, nothing has changed locally as far as network configuration, hardware, or software... so ya anyway I don't get it, but this seems to have worked. Anyway Maybe that information could help.

We could very well, just be AFK while it is happening, but after extensive playing on both and not noticing it for an almost solid 3 days, I'm just going to call this solved. If it pops up again with this configuration, I'll make a new thread with a link to this one. Thanks to everyone that responded.