<!-- For general questions, please ask on Robotics Stack Exchange: https://robotics.stackexchange.com/, make sure to include at least the `ros2` and `nav2` tags and the rosdistro version you are running, e.g. `ardent`. For general design discussions, please post on discourse: https://discourse.ros.org/c/ng-ros Not sure if this is the right repository? Open an issue on https://github.com/ros-navigation/navigation2 For Bug report or feature requests, please fill out the relevant category below --> ## Bug report **Required Info:** - Operating System: - Ubuntu 24.04 - Computer: - All Computers - ROS2 Version: - ROS2 Rolling - Version or commit hash: - [719d711](https://github.com/ros-navigation/navigation2/pull/5003/commits/719d711a82f906eee45887dfba816822aac346a3) - DDS implementation: - All DDS Implementation #### Steps to reproduce issue 1. Enable Graceful Controller Plugin 2. Perform any Navigation Workflow More details here: https://github.com/ros-navigation/navigation2/pull/5003#issuecomment-3269178643 #### Expected behavior The motion target heading for the controller generated path should be in the direction of robot motion. #### Actual behavior The motion target path comes out to be opposite. <img width="787" height="595" alt="Image" src="https://github.com/user-attachments/assets/67c11d14-57e3-4047-a45a-2502b010a523" /> #### Reproduction instructions #### Additional information