INI files: reading and precedence
Understand where an OpenSimulator setting originates and how to change it safely.
Recognizing a section
A bracketed name opens a section. Following settings belong to that section until the next section header. Different sections may use the same setting name for different purposes.
Example: adapt paths and values for your installation.
[Startup] physics = ubODE [Const] BaseHostname = "127.0.0.1"
Comments and active values
In supplied examples, semicolons comment out lines. An option preceded by ; is not active. To enable an example setting, remove the semicolon from the relevant line.
Example: adapt paths and values for your installation.
; physics = BulletSim physics = ubODE
OpenSimDefaults.ini
This file supplies base defaults. Avoid keeping site-specific changes inside it because updates may overwrite them. Prefer a designated override configuration file.
OpenSim.ini.example and OpenSim.ini
The .example suffix denotes a template. For a source installation, copy the OpenSim.ini.example template to OpenSim.ini, then adapt [Const] and [Architecture] for the chosen deployment.
[Const] and substitutions
[Const] defines reusable hostnames and URLs referenced by other settings using ${Const|Name}. This simplifies maintenance, but an incorrect value can affect multiple services.
Example: adapt paths and values for your installation.
[Const]
BaseHostname = "127.0.0.1"
BaseURL = "http://${Const|BaseHostname}"[Architecture] and included files
The simulator deployment model depends on architecture configuration. GridCommon.ini and StandaloneCommon.ini apply to different architectures: verify service connectors and ports before copying them.
Personal overrides under bin/config/
The extra INI directory may contain local overrides. A key can appear in multiple files; final precedence depends on the actual loading order, not merely the apparent folder location.
Verify with config show
The config show console command displays merged settings. It can show whether the intended value was loaded and help locate a forgotten override.
Example: adapt paths and values for your installation.
config show
ROBUST is not a simulator
ROBUST has separate configuration, commonly Robust.ini or Robust.HG.ini, and its own configurable modular file directory. Do not blindly copy region settings into ROBUST.
Sensitive settings
SQL passwords, service keys, internal URLs and tokens must never appear in a public repository or screenshot. Examples on this site are illustrative, not production values.
Safe change procedure
1. Back up the file. 2. Record section and current value. 3. Check overrides. 4. Change one setting. 5. Restart only if needed. 6. Inspect logs and config show. 7. Revert if the result differs from expectations.