Bridge Command 5
Navigation
Return to Documentation Home or Bridge Command homepage.
Scenarios
Contents
Introduction
Bridge Command is built
around the
principle of 'Scenarios,' and loads one at the start of each session.
The scenario sets the scenery area loaded, the other vessels in the
simulation and the vessel simulated. It is essential to load a scenario
when starting Bridge Command, but the scenario itself can be extremely
simple or very complicated.
Bridge Command comes with a scenario writing programme, which automates the process
of scenario writing, so you don't need to worry about the technical details of each file if
you use this editor. This writer is documented here. Below is the
full technical specification of the scenario format.
Specification
The files that make up a scenario are text files. Each scenario is stored in its own folder under the Scenarios folder.
This folder is itself in the main Bridge Command installation folder. To allow users to edit and add scenarios, they are
then copied into the user's directory (which can be found using the button on the Bridge Command launcher). The scenario
files can be edited with a text editor (as distinct from a word processor), such as the Windows program
Notepad. This comes on all computers running Windows.
Each scenario is made up of three text files, named
- Environment.ini
- Othership.ini
- Ownship.ini
To get a feeling for how the scenarios work, it's probably best to
start of by experimenting with an existing scenario, and modifying it.
This should help you get to grips with what's involved than just
reading the specification below, though it will be useful to understand
the details of how things are defined.
To copy an existing scenario to experiment with, copy the entire folder
for that scenario, and rename it as something else. Then you can modify
the scenario as much as you want without losing the original.
Environment.ini
This defines the scenery loaded, along with its tidal
characteristics.
Example
Setting="SantaCatalina"
StartTime=7.25
StartDay=28
StartMonth=2
StartYear=2009
SunRise=8.817
SunSet=16.8
VisibilityRange=5
Weather=0.5
Rain=2
You will notice that textual settings, such as SantaCatalina are
enclosed in quotation marks, while numerical ones are not. This is the
general principle in all files.
Line
by line analysis
- Setting: This selects which world area to load. This is the
name of the folder containing the world model.
- StartTime: This is the time at which the scenario starts,
in decimal hours (24 hour clock). Therefore, the setting 7.25 above means
that the scenario starts at 0715h.
- StartDay: The day of the month the scenario starts. Therefore in the the example, the scenario will start
on the 28th of the month.
- StartMonth: The month of the year that the scenario starts. Therefore in the the example, the scenario will start
in February.
- StartYear: The year that the scenario starts. Therefore in the the example, the scenario will start
in 2009. The start year must be between 1970 and 2037.
- SunRise: The time of sunrise, again in decimal hours. Along
with SunSet, this can be omitted, giving a default sunrise at 6AM and
sunset at 6PM.
- SunSet: The time of sunset, in decimal hours. See SunRise
above.
- VisibilityRange: The maximum distance at which objects are visible through fog/haze, in nautical miles. If the map controller is used, the visibility set by the map controller will override this.
- Weather: How rough the sea is, from 0 (best) to 12 (worst). If the map controller is used, the weather set by the map controller will override this. The weather also determines how windy it is.
- WindDirection: The bearing the wind is blowing from at the start of the scenario.
- WindSpeed: The wind speed at the start of the scenario.
- Rain: The rain intensity, between 0 for no rain and 10 for maximum rain.
Othership.ini
Bridge Command allows you two ways to control other vessels in the simulation.
This file allows you to set up ships with a pre-planned track, which can have many legs
as required. These tracks can also be controlled as the scenario is run with the Map Controller,
a program which is distributed with Bridge Command, and is documented
here.
The first line sets the number of vessels that will be loaded, so if you want a
simple scenario with no other ships, this file just contains one line:
Number=0
However, if you want to load one or more other vessels with pre-planned tracks, the format is
as below
Example
Number=1
Type(1)="HMAS_Waller"
InitialLong(1)=-118.486
InitialLat(1)=33.385
Legs(1)=2
Bearing(1,1)=190
Speed(1,1)=10
Distance(1,1)=1.5
Bearing(1,2)=190
Speed(1,2)=0
Distance(1,2)=1
In this case, one vessel is being loaded, hence Number=1. For each
vessel loaded, the same setting are used, so the setting name is
followed by the vessel number in brackets, with no additional spaces.
Settings
- Type: The vessel to load. This must be an available 'other
ship' model, which are typically stored in C:\Program files (x86)\Bridge Command
5.x\Models\Othership, or in the user folder.
- InitialLong: The longitude where the vessel starts. This
is in decimal degrees, with east being positive. Therefore -118.486
corresponds to 118° 29.16' West
- InitialLat: As above, but for latitude with north as
positive. Therefore 33.385
corresponds to 33° 23.1' North.
- Legs: The number of legs making up the vessel's route (See
below)
To make the ship move, a route is set made out of one or more 'legs' of
set length, bearing and speed. As each can have many route legs, now a
double number is added to the end of the setting name in brackets, the
first number being the vessel number, and the second the leg number.
These are separated by a comma, and there is no space between them.
Therefore Bearing(1,2)
is the bearing of the second leg of the first
vessel, whereas Bearing(3,1)
is the bearing of the first leg of the third
vessel.
Route
For each leg, the following settings apply:
- Bearing: The course in degrees (true).
- Speed: The speed in knots (nautical miles per hour).
- Distance: The length of the leg in nautical miles.
Note that after the last leg, the vessel stops and faces north (i.e. goes
onto a course of 000° with a speed of zero. To keep the vessel
pointing in the required direction, you can add an extra leg onto the
end of the route, with the required course, a non-zero length but a
speed of zero. The vessel will remain stationary, facing in the
required direction indefinitely. Remember that this leg needs to be
counted in the number of legs set.
Ownship.ini
This sets what vessel to load as your own ship, and some of its
characteristics.
Example
ShipName="ORP_Jaskolka"
InitialLong=-118.49
InitialLat=33.38
InitialBearing=339
InitialSpeed=15
HasGPS=1
HasDepthSounder=1
MaxDepth=50
Settings
- ShipName: The vessel to load. This must be an available
'own ship' model, which are typically stored in C:\Program files (x86)\Bridge Command
5.x\Models\Ownship, or in the user folder.
- MMSI: (Optional) If set, this is used when Bridge Command is used with AIS data.
- InitialLong: The longitude where your vessel starts. This
is in decimal degrees, with east being positive. Therefore -118.49 corresponds
to 118° 29.4' West
- InitialLat: As above, but for latitude with north as
positive. Therefore 33.38
corresponds to 33° 22.8' North.
- InitialBearing: Your initial course in degrees (true)
- InitialSpeed: Your initial speed in knots (nautical miles
per hour)
- HasGPS: If your vessel has a GPS readout. Set HasGPS=1 for
a GPS display and HasGPS=0 for no readout
- HasDepthSounder: As above, but for a depth readout (Depth
under keel in metres)
- MaxDepth: The maximum depth in metres for which the depth sounder will give a reading. If not set, this defaults to 100m.
Conclusion
If you have any questions, please ask the author - send
me an email.