goksanisil

Hi, Thank you for the insight. I've tried with 0.005sec step instead of the default 0.0167 sec, as well as increasing the velocity and position solver iterations to 10x of...

Similarly, I have applied the above suggestions (increasing solver resolution, decreasing impact velocity) on a different heightfield where I've also seen the tunneling effect. In that case, sufficiently increasing solver...

I wanted to give one more input. I've generated a rectangular environment with walls in Blender and using it as a static concave mesh collider. In the 1st video below,...

Hi, Completely on board with @jjw2 I haven't checked 0.9.11 but as of 0.9.10, tf relation for sensors are still w.r.t. "map" frame. Is there a plan to change this?

Thank you @fpasch !

I'm coincidentally facing the same problem, and the main issue is that the translation values between the sensor and laser/imu frames are omitted in ROS2 drivers (as it can be...

I have tracked the problem to https://github.com/ros-drivers/ros2_ouster_drivers/blob/593dc2bbde252e14658b1ae405f536fab0dd9ffa/ros2_ouster/include/ros2_ouster/conversions.hpp#L107 I believe the lines should be changed as the following:  @SteveMacenski do you agree?

hi, you can generate the proto files yourself if you just delete the .cc and .h files inside the proto folder.

member variables of the visualizer class: ``` open3d::visualization::Visualizer gridViz_; std::shared_ptr voxelGrid_; ``` initializing the visualizer: ``` gridViz_.CreateVisualizerWindow("Grid", 960, 540, 480, 270); gridViz_.GetRenderOption().background_color_ = {0.05, 0.05, 0.05}; gridViz_.GetRenderOption().point_size_ = 1; gridViz_.GetRenderOption().show_coordinate_frame_...