GUI and visualization options
--------------------------------------------
Available parameters under the global `` ... `` tag (all are optional).
- ``800`` and ``600``. Size of the main GUI window, in pixels.
- ``true``. Whether to start maximized.
- ``20``. GUI refresh rate (in FPS or Hz). Faster will
lead to smoother graphics and animations of the vehicle motion, at a higher CPU/GPU
cost. Publication of sensor readings, odometry, etc. is not affected at all by this parameter.
- ``true``. If enabled (default),
obstacle readings (RGBD cameras, 2D or 3D Lidars, etc.) will be visible as point clouds.
This option can be also dynamically switched from the UI:
.. raw:: html
- ``false``. If enabled, MVSim will run without
any interactive GUI. Useful to save some CPU/GPU usage or to run
MVSim inside docker containers.
- ``0 0 0``. Defines the (x,y,z) coordinates
of the point the camera should look at upon start.
- ``false`` and ``0.01``. If
``show_forces`` is set to ``true``, reaction forces will be visible as thin lines, using
the given scale in meters/Newton. This option can be also dynamically switched from the UI:
.. raw:: html
- ``false``. If set to ``true``, the GUI will show an orthographic view
of the world. Otherwise, it will use a standard perspective camera.
- ``60.0``. If ``ortho`` is ``false``, this defines
the GUI camera vertical field of view, in degrees.
- ``80.0``. The initial distance from the camera
point-to location and the camera focal point.
- ``0 0 0``: The initial camera will be pointing to this XYZ location.
- ``45.0`` and ``40.0``.
The initial elevation and azimuth of the orbit model to define
the camera placement and pose.
- ``r1``. If not empty, the GUI camera will accept rotations made
by the user, but it will always exactly follow the robot given by its ``name``.
- ``0.05`` and ``10e3``.
The shortest and farthest distances that are visible in the GUI
camera `view frustrum `_.
.. code-block:: xml
:caption: GUI and visualization options
...
falsefalse3560
...