#SOLVED The in-game walkie-talkie voice chat for the Switch version of "WHH Together" is not working.
11 messages · Page 1 of 1 (latest)
Hey! We're sorry to hear that. Might be a bit of a straightforward question, but just making sure, did you press the right button to use the walkies? It's not an open-chat, you need to actively press and not talk at the same time as each other.
And maybe once you're both in-game, try unplugging and replugging the headset.
Also check if your privacy settings allow for voice-chatting and if you haven't accidentally pressed a button to mute each other, or muted each other on Switch
This might also contain useful info for you
Sorry for the late reply!!
I tried your advice again but it didn't work.
Addition! Sorry.
My friend was playing "WHH Together" on the Switch 2 with a headset that had a microphone, and when he started the game, the following pop-up message appeared.
(Sorry, we're playing in Japanese. 🥹)
I've double-checked the microphone settings and input test on the Switch 2 and there don't seem to be any issues. What do you think?
Hey! I've sent your issue to our dev, but he is out of the studio this week and will be back on Monday so it can take a bit of time before I get a reply 🥺
Thank you for your reply!! I'll wait patiently 🏖
Our dev said it sounds like a network issue where the network has trouble connecting to the Vivox servers. Our dev is working on patches for consoles for Too & Together, and he hopes to be able to put them live this week. These patches will contain a pop-up that shows your input device to make it a bit easier to see what the game is selecting, this might help for your issue.
Otherwise, to check or exclude if your network is the issue, you could try to temporarily connect to another network (for example your phone's hotspot) to see if this makes any difference.
Regarding the issue with voice chat between Switch and Switch 2, I checked yesterday and it has been resolved!
Thank you very much for your sincere response. 😭
Ahh we're happy to hear that! Not sure why this occured, but I'm glad it works now 🙂