diff --git a/bin/Scenarios/MultiplayerTest_mp/environment.ini b/bin/Scenarios/MultiplayerTest_mp/environment.ini
index 951fcaf3..32cb9cf9 100644
--- a/bin/Scenarios/MultiplayerTest_mp/environment.ini
+++ b/bin/Scenarios/MultiplayerTest_mp/environment.ini
@@ -7,4 +7,6 @@ SunRise=6
 SunSet=18
 VisibilityRange=8
 Weather=1
+WindDirection=0
+WindSpeed=0
 Rain=0
diff --git a/bin/Scenarios/MultiplayerTest_mp/othership.ini b/bin/Scenarios/MultiplayerTest_mp/othership.ini
index a23805e1..fa4c28cb 100644
--- a/bin/Scenarios/MultiplayerTest_mp/othership.ini
+++ b/bin/Scenarios/MultiplayerTest_mp/othership.ini
@@ -1,15 +1,17 @@
 Number=2
 Type(1)="Waverley"
-InitLong(1)=-9.98135
-InitLat(1)=50.0358
+InitLong(1)=-9.9847202
+InitLat(1)=50.035011
+mmsi(1)=0
 Legs(1)=1
 Bearing(1,1)=180
 Speed(1,1)=10
 Distance(1,1)=0.1
-Type(2)="Waverley"
-InitLong(2)=-9.97881
-InitLat(2)=50.0345
+Type(2)="Protis"
+InitLong(2)=-9.9825144
+InitLat(2)=50.030331
+mmsi(2)=0
 Legs(2)=1
-Bearing(2,1)=180
-Speed(2,1)=8
+Bearing(2,1)=10
+Speed(2,1)=10
 Distance(2,1)=0.1
diff --git a/bin/Scenarios/MultiplayerTest_mp/ownship.ini b/bin/Scenarios/MultiplayerTest_mp/ownship.ini
index bd7c4067..d3f1ae99 100644
--- a/bin/Scenarios/MultiplayerTest_mp/ownship.ini
+++ b/bin/Scenarios/MultiplayerTest_mp/ownship.ini
@@ -1,5 +1,5 @@
 ShipName="Protis"
-InitialLong=-9.98486
-InitialLat=50.0371
+InitialLong=-9.9848604
+InitialLat=50.037102
 InitialBearing=180
 InitialSpeed=10
diff --git a/doc/images/multiplayer_1.png b/doc/images/multiplayer_1.png
new file mode 100644
index 00000000..a965fa1e
Binary files /dev/null and b/doc/images/multiplayer_1.png differ
diff --git a/doc/images/multiplayer_2.png b/doc/images/multiplayer_2.png
new file mode 100644
index 00000000..1de11864
Binary files /dev/null and b/doc/images/multiplayer_2.png differ
diff --git a/doc/index.html b/doc/index.html
index 8002c6e2..009007df 100755
--- a/doc/index.html
+++ b/doc/index.html
@@ -44,7 +44,7 @@ <h2>Other programmes</h2>
 <ul>
 <li><a href="writer.html">Using the scenario writer</a>: A guide to the scenario writer program</li>
 <li><a href="config.html">Configuration</a>: Setting Bridge Command's options (full screen/windowed etc)</li>
-<li><a href="multiplayer.html">Multiplayer</a>: EXPERIMENTAL</li>
+<li><a href="multiplayer.html">Multiplayer</a>: Using Bridge Command with multiple users in the same environment</li>
 </ul>
 
 <h2>File specifications</h2>
diff --git a/doc/multiplayer.html b/doc/multiplayer.html
index 651f785c..5e5d4d6c 100755
--- a/doc/multiplayer.html
+++ b/doc/multiplayer.html
@@ -27,28 +27,43 @@ <h2>Introduction</h2>
 <p>Bridge Command can be used in a multiplayer mode, where multiple users can control vessels in the same scenario, and interact. This mode is 
 intended for users on a single network (wired or wireless), but could be used over the internet.</p>
 
-<p>This feature is currently experimental. Please provide feedback and suggestions for developments.</p>
-
 <h2>Starting a multiplayer session</h2>
 
 <p>You will need to run one 'Multiplayer hub' for each session. This can run on a dedicated computer, or on the same computer as one of the 
 Bridge Command sessions.</p>
 
-<p>
-To start a multiplayer session, find out the hostname or IP addresses of all your users' computers, and ask them to start Bridge Command. 
-Instead of selecting a scenario, they should click the multiplayer option and click 'OK'.
-</p>
+<p><b>Important:</b> The Bridge Command sessions for all users must be started first. Each user should start Bridge Command on their computer, 
+and instead of selecting a scenario, the 'Multiplayer' checkbox should be selected.</p>
 
-<p>
-When all users have done this, then you can start the mulitplayer hub, and select a multiplayer scenario. Type in the hostnames or IP addresses 
-of the users' computers, separated by commas. The order you type these in will match the user to the ship in the scenario.
-</p>
+<img src="images/multiplayer_1.png" alt="Multiplayer mode selection in Bridge Command">
+
+<p>The Hostname input can normally be left blank. This is only needed if you are using secondary displays for a single ship in the multiplayer session.</p>
+
+<p>Then click OK, and you should see a screen like this:</p>
+
+<img src="images/multiplayer_2.png" alt="Multiplayer message when waiting to start">
+
+<p>This screen shows the hostname and port for data. By default, the port is 18304. When all users have started Bridge Command, and are on the 'waiting' 
+screen, then you can start the mulitplayer hub, and select a multiplayer scenario. In the hostnames list, type in the hostnames or IP addresses 
+of the users' computers, separated by commas. The order you type these in will match the user to the ship in the scenario. The hostnames are shown in the 'waiting'
+screen in the Bridge Command session. If you are using a non-standard port (the standard port is 18304), you can enter the hostname and port in the format <i>hostname:portNumber</i>.</p>
+
+<img src="images/multiplayer_host.png" alt="Multiplayer Host">
+
+<p>When the scenario is running, each user should see their own Bridge Command session, and the multiplayer hub will start. If required, the simulation can be paused for all users.</p>
+
+<h2>Making a new multiplayer scenario</h2>
 
 <p>
 If you want to make a new multiplayer scenario, you can use the scenario editor to do this, selecting the 'Multiplayer' option and reading the 
 instructions.
 </p>
 
+<p>The main points are that the 'own ship' entry in the simulation is ignored, and that the 'other ships' become the controlled vessels in the multiplayer scenario. The initial speed and heading
+of these ships is set by creating an initial 'leg' with the required speed and heading. If the scenario has more vessels than multiplayer users, the additional vessels will not appear in the scenario.</p>
+
+<p>The multiplayer scenario name must end with '_mp'.</p>
+
 <h2>Technical information</h2>
 
 <p>