Netplay Guide: Difference between revisions

Netplay is a defining feature of Dolphin: it allows you to set up online sessions for any GameCube or Wii title with a local multiplayer mode, without the problems or limitations of the [[Wii Network Guide|Nintendo Wi-Fi Connection]] or hassle of the [[Broadband Adapter|BBA]]. It is improving regularly, and GameCube Netplay should be painless. Wii Netplay is much more temperamental and should be treated as an experimental feature for advanced users.

*The game you want to play <b>MUST</b> be in all player's gamelist.

Your Netplay Experience will greatly vary depending on what version of Dolphin that you are using.  Because Dolphin 5.0 is lacking so many netplay features, we highly recommend to use either the latest available beta or dev build.  Dolphin 5.0 won't have have Wii Save Synchronization ({{revision|5.0-8478}}), Automated Settings Synchronization ({{revision|5.0-8502}}), Cheat Code Synchronization ({{revision|5.0-9032}}), Synchronize All Wii Saves ({{revision|5.0-9037}}) as well as protections for recovering saves if Netplay crashes.  Dolphin 5.0 also lacks experimental Wii Remote Netplay, and while that feature is considered to be for advanced users, it is possible to use on the latest builds.

*<b>Buffer</b>:  At the bottom of the screen is the buffer option.  Buffer is the amount of latency added to inputs.  If you're noticing slowdown and stuttering <i>even</i> on very low impact scenes like a game's splash screens, odds are the buffer is too low and you might need to increase it.  A simple formula that is accurate for most titles is 1 pad buffer per 15 ms of latency per client. Two players at 50 ms latency would be roughly 3 - 4 buffer, where as three players at 50 and 65 ms would be roughly 7 buffer.  Depending on your computer's performance (higher performance computers finish frames sooner, meaning slightly less buffer may be needed) and the quality of your internet, you may need to adjust this.  Sometimes poll more/less than others, which may result in the formula not working at all.

*<b>Write Save Data</b>: If Write Save Data is enabled, this means that progress made on netplay will be saved to the <b>host's</b> Memory Card or Wii NAND, depending on which is applicable, and the data will be kept even after the netplay session is over.  This is good for longer games that will take many sessions, like playing through Tales of Symphonia with multiple players. Note that if netplay crashes, Wii saves may not be properly copied into the host's NAND and may need to recovered manually from the Wii backup folder within the user directory.

*<b>Load Wii Save</b>:  This settings determines whether a Wii Save file is loaded for the <i>initial</i> title selected.  It only loads a single Wii Save if the hosted netplay game is a Wii game.

*<b>Sync Saves</b>: This synchronizes savedata for the netplay session.  It will only sync whatever saves are loaded, and these saves are only synchronized temporarily for the current netplay session.  Your original saves will not be overwritten.

*<b>Sync AR/Gecko Codes</b>: This option synchronizes which Action Replay and Gecko Codes are enabled between players.  The codes enabled on the host's computer will automatically be enabled on clients when the netplay game starts.  Note that it only synchronizes which codes are enabled, it will not transfer new codes between players.  If this feature causes problems, it may be because the codes differ in each player's GameINI.

*<b>Sync All Wii Saves</b>: This synchronizes all Wii Save Data for a netplay session.  Useful if you're booting a romhack that uses different savedata than the actual file you're loading.  Example: Project M uses a .elf, but loads savedata from the NAND under a different title name.

Setting up netplay controllers is a very simple system that is confusing because Wii Remotes have to be configured a bit differently.  We'll first go through how to setup every other controller, and then talk about the differences for Emulated Wii Remotes at the end.

Everything we've discussed in terms of how ports, profiles, and configurations are loaded need to be thrown out the window for Wii Remote netplay.  Emulated Wii Remotes and their extensions <b>can</b> be used on netplay.  If you would prefer to use Real Wii Remotes on netplay, you must do that through Emulated Wii Remotes via the <i>Connect Wii Remotes for Emulated Controllers</i>.  Your Wii Remote will now show up as an emulated controller that can be assigned buttons, and with Dolphin's stock profile, you can automatically assign everything exactly how it would be if you were using it directly as a real Wii Remote.  The "Real Wii Remote" controller option itself is not supported.

Unlike when using GameCube Controllers and GBAs, each player must set a configuration profile to the <b>Wii Remote Slot they will be using on netplay.</b>  That means if you are the host and using Wii Remote 1, you must have the first Emulated Wii Remote configured to your controller on your computer.  If you are a client joining and you are assigned to Wii Remote 2, you must have Emulated Wii Remote 2 configured with your controls.  In order to prevent desyncs, all players should configure the correct attachments to all controllers.  Though Dolphin <i>should</i> attempt to synchronize attachments, it has been known to have issues.  If you are using a physical Wii Remote connected as an emulated controller you do not have to set the attachment ahead of time as the stock profile automatically configures it.