search

EDCD / EDDI

Companion application for Elite Dangerous
Other
445 stars 81 forks source link

Route destination is completely incorrect #1431

Closed arancaytar closed 5 years ago

arancaytar commented 5 years ago

EDDI version in which issue is found

v3.4.1.

VoiceAttack version in which issue is found (as applicable)

-

Steps to reproduce

  1. Plot a route in the Galaxy Map
  2. Jump to the next system along the way

Expected

EDDI announces "Distance to {route destination} is {distance}, with {jumps} jumps remaining"

Observed

The actual announcement names a completely different system that isn't the destination, and which I've never visited or plotted a course to. In this case it is stuck at the system LP 390-16. The distance also matches that system, rather than the actual destination.

The value of the {event.destination} variable is somehow set to this value instead of the actual route destination, and it doesn't change if a new route is plotted either.

Edit: The LP 390-16 destination is still announced even if the route is cleared entirely.

Tkael commented 5 years ago

Simply plotting a new route on the Galaxy Map will not change the route set in EDDI, nor can it (since no information is written to the journal about your route or destination when you plot a course in the Galaxy Map).

The route destination that EDDI is referencing is set via the RouteDetails() function (https://github.com/EDCD/EDDI/wiki/Help#routedetails) or the UI (using the buttons in the Mission Monitor, Crime Monitor, or Material Monitor) and is typically used for navigating to mission destinations efficiently.

If you'd simply like to clear the current route, there is a Clear Route button on the Mission Monitor tab.

Hoodathunk commented 5 years ago

To add to Tkael’s commentary, the destination set by EDDI comes from navigational aids built into EDDI for mission and misc services routing. With manual intervention, it can be made to match a plot in the galaxy map, but FDEV does not provide the necessary data to automate it.

Hoodathunk commented 5 years ago

Closing this issue. Be aware that any further comments/questions can still be posted and seen by the dev team.

arancaytar commented 5 years ago

Sorry, thanks for the info; I incorrectly assumed this was part of the data received through the Frontier API. :)