![]() | 1 | initial version |
Were you using the gazebo_ros_joint_pose_trajectory
plugin?
I found a bug in it today and it looks like it's been that way for years. The upshot is that all the time_from_starts were getting zerod regardless of the message sent to Gazebo.
If you're interested in seeing the cause, check out this pull request.