-
Notifications
You must be signed in to change notification settings - Fork 19
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
predict crash location on GCS #24
Conversation
Since there is a crashItem for each drone, I would put it in the ACItemManager, which hold references to every objects linked to an AC. I would also make that optional, as I can imagine it could be a bit disturbing if this waypoint is not desired. I will try writing a bit of a doc to explain how to use it. |
Thanks for the tips @Fabien-B! I'll modify accordingly. |
@Fabien-B I added the prediction as an attribute of an AC and I added a checkbox to enable the display of the crash prediction. The thing I struggled with was to hide the the waypointItem. I now made it very small, but still visible... Maybe you know an easy way to do this? |
I did not anticipated the need to hide a waypoint, as I usually just remove it. |
I added the virtual method |
17fef3c
to
14eebfd
Compare
Thank you so much @Fabien-B, it works like a charm! I see your point that it makes sense to compute the crash prediction in the background to be able to display it even after losing the datalink. One could also replay the log and then enable the feature, but it would be less convenient. |
I made a GCS marker to predict the ballistic crash position.
I tried to follow this commit: b0e1641
I had to take some time to understand the code structure, but probably I still butchered it. Right now there is only one crashItem, which would be a problem if you have multiple drones. I guess it can be done like with DCSHOT with the QList?