Skip to content
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

Nav Monitor Ship Route reports the wrong next jump distance #2591

Closed
richardbuckle opened this issue Jan 23, 2024 · 1 comment
Closed

Nav Monitor Ship Route reports the wrong next jump distance #2591

richardbuckle opened this issue Jan 23, 2024 · 1 comment
Assignees
Labels
6. not up to spec The expected behaviour per the spec doesn’t match the observed behaviour.

Comments

@richardbuckle
Copy link
Member

What's Wrong

When you create a ship route in the Nav monitor, after each jump it wrongly reports the next jump distance as being that for item 1 in the list

Expected

Please see this route
image
I expected the voice report on each jump to show the next jump distance as per the table.

Observed

The voice report on each jump always says that the next jump will be 20.4 Ly away, the value from item 1 of the table. Excerpts from speechresponder.out:

Pulsar route calculated. Freebie will reach Eol Prou AK-A e137 in 7 jumps. Total route distance is 457.0 lightyears. First destination is Eol Prou P X dash T d 3 dash 1133, 20 lightyears away.  Clipboard set.
Guidance enabled.
Course locked in.
Next system is Eol Prou R S dash T d 3 dash 287, 20.4 lightyears away.  Clipboard set.
Next destination is Eol Prou K R dash W e 1 dash 1060, 20.4 lightyears away.  Clipboard set.
Next waypoint is Eol Prou P H dash V d 2 dash 832, 20.4 lightyears away.  Clipboard set.

Steps to reproduce

  1. Plot any pulsar route using the Nav monitor.
  2. Fly it and observe the above issue.

Configuration

  • Version [Please give full version numbers here, not just "latest" or "current"]
    • EDDI Version: 4.0.3
    • VoiceAttack Version: none
  • Localization en
    • EDDI's language: en
    • Voice: IVONA 2 Amy
@richardbuckle richardbuckle added the 6. not up to spec The expected behaviour per the spec doesn’t match the observed behaviour. label Jan 23, 2024
@Darkcyde13
Copy link

Darkcyde13 commented Jan 27, 2024

My additional comment on #2586 mentions this too. Mine was for missions routes.

@Tkael Tkael closed this as completed in ca9171a Mar 17, 2024
bcthund pushed a commit to bcthund/EDDI that referenced this issue Jun 26, 2024
Resolves EDCD#2591
Bring route tracking inside NavWaypointCollection so that each collection can independently track route progress.
bcthund pushed a commit to bcthund/EDDI that referenced this issue Jun 26, 2024
Resolves EDCD#2591
Bring route tracking inside NavWaypointCollection so that each collection can independently track route progress.
bcthund pushed a commit to bcthund/EDDI that referenced this issue Jun 26, 2024
Resolves EDCD#2591
Bring route tracking inside NavWaypointCollection so that each collection can independently track route progress.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6. not up to spec The expected behaviour per the spec doesn’t match the observed behaviour.
Projects
None yet
Development

No branches or pull requests

3 participants