The `update_rate` parameter of the gazebo camera sensor seems to be understood as the upper limit for the frame frequency and does not slow down the simulation time if the rate can not be provided.
For example, `update_rate = 300` yields a message frequency of ~200 on my system. The measurement has been conducted with `rostopic hz` with `update_rate = 0` for the ROS plugin (=> publish *every* frame).
How can I make sure that the sensor produces a fixed amount of frames per simulation time (without manually adapting the real time factor)?
**Background**
I am developing a custom sensor plugin which attempts to simulate a [Dynamic Vision Sensor](https://inilabs.com/products/dynamic-vision-sensors/). The DVS is an event-based sensor, effectively reporting pixel change events when the pixel-value change exceeds a certain threshold. One of the main advantages of this sensor is the very low delay between system state change and visual feedback. As my simulation relies on inter-frame differences, I need a very high frame-rate to produce these small delays.
↧