nakai-omer

it should be merged into a `humble` branch to match ros guidelines

@ryanpennings Thanks for the feedback. In our implementation we use the `transformLaserScanToPointCloud` override which doesn't include the range_cutoff param at all. This to my understanding, should cause the range_max from...

@samiamlabs Can you please check what is the max_range param from your laser scan message, and whether is matches your configured range_max in this package? I will merge this line...

@samiamlabs Thanks for the update. I have added @ryanpennings fix to this PR.

I know this is an old question, but just in case someone also runs into this. This lib by default fills in the data with your `range_max` value + 1....

We created a PR to support latest ros2: https://github.com/iralabdisco/ira_laser_tools/pull/47

I will update the readme as well, if this fix is acceptable.

@Myzhar Sorry about that, fixed.

> Thank you for the fixes. I'm not merging your PR directly, but I'm going to create a `ros2_humble` branch before. If you would like to follow ros2 conventions, branch...

This also occurs in ROS2 Humble > @weitung @Myzhar I had this same problem working with galactic. I moved [this line](https://github.com/stereolabs/zed-ros2-wrapper/blob/55a4302c6365ab2742e61f4cbfbd34960d3955b2/zed_components/src/zed_camera/src/zed_camera_component.cpp#L264) to the very end of the constructor to allow...