Nav2 zigzag navigation in a large road environment with Isaac Sim. RViz localization gradually diverges from the simulator

Hi everyone,

I’m new to Nav2 and I am currently using Isaac Sim as my simulation platform. The AMR is the official Nova Carter, equipped with a single front-mounted 2D LiDAR.

Navigation works well in a relatively small indoor factory environment. The AMR follows the planned path correctly and AMCL localization appears stable.

However, after switching to the larger road environment shown in the attached images, I started experiencing some unusual behavior:

  • The AMR moves in a zigzag pattern during navigation instead of driving smoothly along the center of the road.

  • As navigation continues, the robot in Isaac Sim gradually drift off the road and may even end up on the roadside. At the same time, RViz still shows the robot in the middle of the road, so the robot’s position in RViz is clearly inconsistent with its actual position in Isaac Sim.

I’d like to ask what kind of issue would typically cause this behavior?

Thanks in advance

RViz showing the robot centered while the sim robot drifts means your localization has stopped correcting odometry drift. AMCL thinks it knows where it is and it doesn’t. In a big road world with a single front 2D lidar, that’s very common:

  • not enough geometry in range. Small factory = walls and racks everywhere. Open road = a few curbs, maybe nothing within the lidar’s max range. When most beams return nothing, AMCL has nothing to match and just follows odom. Overlay /scan on the map in RViz (fixed frame = map): if the scan slides off the map edges while the pose stays put, this is it. Check the lidar’s max range against the distance to the nearest real features.
  • map vs. world mismatch. If the occupancy map for the big world was generated or scaled separately, a small resolution or origin error is invisible in a small room and obvious over 100 m. Drive to a known landmark and compare.
  • odometry quality. Compare /odom against Isaac Sim’s ground-truth pose over a long straight drive. If odom drifts and AMCL can’t fix it (see point 1), RViz will look fine while the real robot wanders.
  • sim time. Make sure use_sim_time is true on every Nav2 node and that Isaac Sim publishes /clock. In a heavier world the sim often runs slower than real time. With mixed clocks, the controller and TF get out of sync, and that can cause oscillation.

the zigzag is often a side effect: the pose estimate jumps a bit, and the controller keeps correcting toward a path it thinks it’s off. Fix localization first, then tune the controller (lower max angular accel, check the controller frequency against the sim’s real-time factor). If the road really has no features, 2D AMCL is the wrong tool: add a 3D lidar or GPS fusion with robot_localization, or test in a world with roadside structure.