Hello,
As you suspected, your map's image size is probably too big for the hardware you are running ROS on. The issue is not RViz but the navigation stack and processing the costmap on that many pixels (2048 x 2048). The typical solution is to bring your map up in an editor and reduce its size. At the same time, you will reduce the resolution value in the corresponding .yaml file for your map.
For example, if your 2048x2048 map has a resolution of 0.01 (one centimeter per pixel), in the .yaml file, try scaling the .png file to 512 x 512 pixels and setting the resolution to 0.04 in the .yaml file.
--patrick
The Pi Robot Project http://www.pirobot.org/wordpress
Here is a question I post on ROS wiki: rviz,can it be solved?
--
Hello,
Changing the robot_radius parameter in the costmap_common_params.yaml file will not change how the robot appears in RViz. The robot_radius parameter simply changes the value that move_base uses in its costmap calculations. To change the actual appearance of the Turtlebot in RViz, you have to edit the Turtlebot's URDF/Xacro file and since the Turtlebot model uses a mesh for the body, you would have to scale the mesh in a program like Meshlab.
If you just want to see the effective radius in RViz, add a Polygon display and subscribe to either the local or global footprint topic.
--patrick
-- The Pi Robot Project http://www.pirobot.org/wordpress