Bridge Command - Configuration

Introduction

Bridge Command's settings are controlled in the file bc5.ini, found in the Bridge Command root directory. Note that Bridge Command will look first in the user directory for a settings file, and will use this in preference to the global bc5.ini file. This allows users to change their own settings. The user directory is %appdata%/Bridge Command/x.x on Windows, ~/.Bridge Command/x.x on Linux and ~/Library/Application Support/Bridge Command/x.x on OSX. For all of these, x.x is the Bridge Command short version number (e.g. 5.6)

The settings file can be edited with either a standard text editor (such as notepad), or with the program provided, which can be started by clicking on the 'Settings: Main' button on the Bridge Command launcher. For advanced users, Bridge Command can be run with the command line option '-c' to point to an alternative settings file. For example, 'bridgecommand-bc.exe -c c:\path\to\alternativeIniFile.ini'.

The settings control how Bridge Command runs on your screen, such as whether it runs full screen, or in a window, and at what resolution, as well as many other things.

Using the Settings Editor

When you run the Bridge Command launcher, click the button 'Settings: Main' towards the bottom of the list. This will load an editor, as shown below. This allows you to read about the different settings and change them. To change a value, double click on the line you want to change, then type the setting in the box that appears, and press enter to continue. When you have finished, clicking 'Save' at the bottom of the screen will save your changes and exit the editor.

Settings Editor

The bc5.ini technical specification

This file uses the general principles documented in the Ini File Format document, which should be referred to alongside this document.

Example bc5.ini file

[Graphics]
graphics_mode=2
graphics_width=800
graphics_height=600
graphics_depth=32
use_directX=0
disable_shaders=0
anti_alias=4
view_angle=90
look_angle=0
minimum_distance=0.5
maximum_distance=100000
[Joystick]
port_throttle_channel=1
stbd_throttle_channel=2
bow_thruster_channel=3
stern_thruster_channel=4
rudder_channel=3
joystick_no_port=0
joystick_no_stbd=0
joystick_no_rudder=0
joystick_no_bow_thruster=0
joystick_no_stern_thruster=0

joystick_map_points=12

joystick_map(1,1)=-1	
joystick_map(1,2)=-1

joystick_map(2,1)=-0.5	
joystick_map(2,2)=-0.5

joystick_map(3,1)=-0.25	
joystick_map(3,2)=-0.5

joystick_map(4,1)=-0.25
joystick_map(4,2)=-0.25

joystick_map(5,1)=-0.125	
joystick_map(5,2)=-0.25

joystick_map(6,1)=-0.125	
joystick_map(6,2)=0

joystick_map(7,1)=0.125	
joystick_map(7,2)=0
	
joystick_map(8,1)=0.125	
joystick_map(8,2)=0.25
	
joystick_map(9,1)=0.25	
joystick_map(9,2)=0.25
	
joystick_map(10,1)=0.25	
joystick_map(10,2)=0.5
	
joystick_map(11,1)=0.5	
joystick_map(11,2)=0.5
	
joystick_map(12,1)=1.0	
joystick_map(12,2)=1

[Network]
udp_send_port=18304
[NMEA over serial]
NMEA_ComPort=""

[Startup]
secondary_mode=0
hide_instruments=0
full_radar=0
arpa_on=0
radar_mode=0

Parameters and descriptions

The parameters set in the file are:

The map.ini technical specification

This file configures the Map Controller, and the other associated programs.

Example map.ini file

[General]
graphics_mode=2
graphics_width=800
graphics_height=600
graphics_depth=32
zoom_levels=10
udp_send_port=18304
[AIS over UDP]
ais_udp_port=0
[Language]
lang="en"

Parameters and descriptions

The parameters set in the file are: