2 FAQ explained: DS4Windows(PS4 Controller) & 'Too many computers...'
Thought I would post a couple of possible fixes for y'all since the support chat wait time is currently at 3+ hours and I'm probably just going to wait til they roll out a patch.
'too many computers have accessed this accounts version of DisplayName field missing from registry. recently. Please try again later'
This is actually an easy one, you used a VPN or changed your Windows Date & Time settings and logged into your account multiple times which causes Origin to lock you out of whatever game you're trying to get into early. From my experience in the past, it's basically a 24 hour lock-out from the time you first logged in using a VPN or changed your timezone. Literally nothing you can do, regedit or otherwise to expedite this process.
DS4Windows(PS4 Controllers & Issues associated)
Happy to report that DS4Windows does work well, as long as all of the settings are correct. This can be a bit tricky though, gave me a headache trying to figure out what was wrong. So here's a list of potential troublemakers and what to do:
- open devmgmt in admin mode and look for HID-Compliant game controller. This should be enabled, it's the ds4Windows driver. If you have multiple, go into properties and disable any HID-based game controller. My issue was that I had a Xbox 360 wireless adapter previously installed and it was still showing up which caused the game to not recognize certain buttons, drift, etc. Disable anything to do with a xbox controller.
- In DS4Windows, there's no need to hide your DS4 controller in settings like you do in some other games, in fact it'll make it a bigger pain if you have it enabled. Keep everything else at default and MAKE SURE you start DS4windows before opening Origin and that it picks up your controller; if it doesn't and you see DS4Windows in 'Sharing mode' at the bottom left of the app, it's not going to work once you launch the game.
I'll try to assist others when possible, there's just a lot of issues and it's hard to find any info in the logs to troubleshoot our way through.