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

[Imoen]

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

[Dracian]

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.

[Imoen]

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.

[Deathgiver]

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.

[Imoen]

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



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.

[Dracian]

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

[Imoen]

Any other ideas?

[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...)

[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!

[Imoen]

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.

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.