FhSim  3.1.0
Marine systems simulation
Loading...
Searching...
No Matches
Troubleshooting

Troubleshooting is split across two pages: this page covers build/setup problems and is an index with a general diagnostic checklist, while the runtime error catalogue — specific error messages, their causes and resolutions — lives in Runtime errors and diagnostics.

Build and setup issues

Conan/CMake configuration fails

  • Verify toolchain prerequisites in Setup developer environment.
  • Re-run profile detection (conan profile detect --force) if compiler config changed.
  • Reinstall dependencies with --build=missing.

Missing package or remote access errors

  • Verify you are using the correct Conan remotes and credentials.
  • Confirm access rights to private package repositories (if applicable).

Runtime issues

Each entry is described in Runtime errors and diagnostics.

  • Simobject library file not found in one of: ... — wrong working directory, LibName or build type; and Could not load library for a file that is found but cannot be loaded. See "Model loading errors".
  • Simulation exits before visualization starts — see "Visualization errors".
  • Visualization startup issues (Ogre, GPU driver, ogre.cfg) — see "Visualization errors". For a pure Wayland session see Running under Wayland.
  • An input value is rejected, or TEnd="$Duration" stops the run — see "XML and configuration errors" and Where substitution applies.
  • License errors — set SFH_LICENSE_FILE to a valid license file path, or place license.lic in the working directory, and confirm that the license matches your product and build.
  • FMU export and co-simulation problems — collected in FMU export and co-simulation; the tool itself is documented in FMU tools.
  • Simulation is slow, unstable, or produces NaN/Inf — enable the <Diagnostics> element and follow the recipes in Diagnostics cookbook. For making a correct run faster, see Performance tuning.

Diagnostic checklist

  1. Run <Executable> --help to verify executable availability.
  2. Run with a known-good example input file.
  3. Increase console/file verbosity to capture detailed diagnostics.
  4. Reduce scenario complexity to isolate failing object/connection.