-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to show a planned trajectory in the Simulator? #418
Comments
I'm not sure what you mean... Do you mean simply draw a line to the goal point from current point? The actual flight path is determined dynamically and is constantly corrected for any deviations. |
I apologize for replying so late on this thread. Well it could be as simple as drawing a line through the waypoints that are being set. What I really wanted to show was that once I had the planned trajectory I could visualize it on the AirSim directly, similar to the way one can in rviz. Nonetheless, I am using rviz for this now so it's not required. I would love to get to know when the ROS wrappers would be officially released for the AirSim. It would be handy to have those now. :) |
I want to draw a line to the goal point...how can I make it... |
Can you make it now ? I also want to do this on a drone trajectory. |
I think issue #1393 outlines what you are looking for, I added this to the API in a fork. I've broken things since then but the changes you need to make to the source code are here: https://github.com/DavidLSmyth/AirSim/commits?author=DavidLSmyth. If you don't need some of the newer functionality, you could clone/fork my repo from commit d41137d |
I am trying to implement a trajectory planning algorithm using the simulator. While I am interfacing with the simulator sing the ROS wrappers suggested in #269, and able to get a goal point, I would like to show the path that is being planned in the simulator itself; something similar to when you press
T
the pink line is made showing it's trajectory.Would love to know if there is a way to do this. Thank you!
The text was updated successfully, but these errors were encountered: