this post was submitted on 18 May 2024
16 points (94.4% liked)
Nintendo
18501 readers
15 users here now
A community for everything Nintendo. Games, news, discussions, stories etc.
Rules:
- No NSFW content.
- No hate speech or personal attacks.
- No ads / spamming / self-promotion / low effort posts / memes etc.
- No linking to, or sharing information about, hacks, ROMs or any illegal content. And no piracy talk. (Linking to emulators, or general mention / discussion of emulation topics is fine.)
- No console wars or PC elitism.
- Be a decent human (or a bot, we don't discriminate against bots... except in Point 7).
- All bots must have mod permission prior to implementation and must follow instance-wide rules. For lemmy.world bot rules click here
Upcoming First Party Games (NA):
Game | Date
|
Mario & Luigi: Brothership | Nov 7 Donkey Kong Country Returns HD | Jan 16, 2025 Xenoblade Chronicles X: Definitive Edition | Mar 20, 2025 Metroid Prime 4 | 2025
Other Gaming Communities
- Gaming @ lemmy.ml
- Games @ sh.itjust.works
- World of JRPG's @ lemmy.zip
- Linux Gaming @ lemmy.ml
- Linux Gaming @ lemmy.world
- Patient Gamer @ lemmy.ml
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Assuming the NAT type is one that supports peer to peer connectivity, you could try using Ethernet instead of wireless (of course this only helps when docked). This would alleviate issues with WiFi signal not being strong enough, potentially increase bandwidth, and reduce latency. Ethernet can't improve the connection beyond the incoming connection from the ISP, it only will improve issues that stem from wireless connectivity.
it could very well be this, when I visit my parents in the countryside the internet is sometimes not good enough, and other times it is adequate (satellite internet, so weather can impact it).