Re: It Takes Two Nintendo Switch Error - 105-80190000
Hi All!
Recently, my partner and I purchased the Nintendo Switch version of "It Takes Two." Like many others, unfortunately, we immediately encountered the dreaded "Your account settings have changed" error on start and were unable to play the game at all.
Pretty frustrated with the fact that the game could not be returned, I took to the forums and found this incredible post made by Patient_Poetry :
It Takes Two Nintendo Switch Error - 105-80190000 | EA Forums - 13181754
They determined that this error is the result of a weird timing dependency bug on the EA side. Essentially, Nintendo Switch sign-on and authentication occurs faster than the EA server can prepare a game session, resulting in the bug. They found that by adding artificial latency to their Switch's connection, they were able to successfully play the game.
This is why some folks have been able to play via hotspot. The hotspot connections provide enough "natural latency" to give the EA servers time to finish session creation, while wifi does not.
WORKAROUND FOR WINDOWS
I have found and tested a temporary workaround if you have a Windows computer. Essentially, it uses the same logic that Patient_Poetry used in their testing, only we will use a Windows system instead of a Linux system as a network throttling bridge.
You only need this program (it does require you to compile via Zig):
https://github.com/abaza121/clumsy-hotspot
This is a fork of Clumsy, a Windows program that allows you to artificially reduce the quality of your connection. This fork is unique in that it allows you to specifically target the hotspot connections of your Windows device. YOU MUST USE THIS FORK. THE ORIGINAL REPOSITORY DOES NOT TARGET HOTSPOT.
These are my settings. Simply put "true" in the filtering box, and enable lag on outbound requests. I found that 40ms delay gave me a 100% success rate but you may need to tinker with this.
After this program is running, all you need to do is enable the built-in "Mobile Hotspot" feature on Windows and connect. Then you should be off to the races.
All in all, it's definitely not the most elegant or ideal solution and it should be up to EA to fix their backend. But I can attest that for the time being, this fix works for us. Please let me know if anyone else has any luck!
