Gazebo | Ignition | Community
Ask Your Question

Revision history [back]

In general Gazebo is non-deterministic, as there are multiple threads running concurrently and some components (e.g.: physics engines) with a non-deterministic nature. In your particular example, it's probably the physics engine (ODE by default) the one that potentially has some non-determinism. My two suggestions are:

  1. Launch Gazebo with the --seed <value> argument using the same VALUE in both instances.

  1. If that doesn't work try using a different physics engine (Gazebo supports multiple ones). Maybe for your example that physics engine is deterministic.