among-usnintendo-switch
When I try to join a private room in Among Us on Switch, I get this error:
I opened the profile section in the menue, and clicked "sign in", yet the error persists. Any way to fix this? I've tried uninstalling the game, removing my savegame data, reinstalling the game, signing in again, and yet the error persists.
This is a known design flaw which is only effecting early models of the Switch.
It's something to do with electrical shielding (or something technical).
First try these steps to make sure you are using the Joy Con correctly
Joy Con Not Responding or Responding Incorrectly When Used Wirelessly
If that didn't work, talk to Nintendo and they will "fix your problem for free" - which means you send in your joy con and they fix it and send it back. This can take up to 2 weeks.
Here are some helpful links for support:
Contact Nintendo Support in America
I get the same feeling when playing Rocket League on PS4. It's because the input latency (time for your button presses to be reflected on screen) is generally much higher on console. This is because:
TVs generally have much higher latency than monitors, especially ones that have fancy effects like motion interpolation or noise reduction. Many TVs have a "gaming mode" that disables those effects and decreases latency - make sure Gaming Mode is on! However, even then, their latency still tends to be much higher than monitors.
You can check your TV's input latency here. My TV is on the better end of things, and it still has 34ms = 2 frames of latency in gaming mode!
Consoles usually use wireless controllers whereas many gamers use wired on their PCs. This generally adds an extra frame or two of latency. There's nothing you can do about that on Switch, but on PS4 the newer DS4s support wired-mode. I'm not sure about XBox.
Lower framerates will increase latency compared to PC by increasing the time between frames. Rocket League on Switch runs at 60fps, so that shouldn't be an issue unless you're used to >60fps on PC.
Best Answer
Based on this document created by innersloth, it looks like it's a server side/traffic issue...