Revision history [back]

You should check to see if your simulated sensors report a value greater than max range, or exactly max range when there is no obstacle within range, and compare that behavior to the code which handles maximum range: https://github.com/DLu/navigation_layers/blob/de3f6706e50c7a37e68b3abfd51a36323c35e726/range_sensor_layer/src/range_sensor_layer.cpp#L224-L235

Ideally, if your sensor is reporting that there is no obstacle within range, there shouldn't be a costmap update for that sensor at all.