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

EDDI ship loadout not responding #1870

Closed
Labanden opened this issue Jul 2, 2020 · 10 comments · Fixed by #1874
Closed

EDDI ship loadout not responding #1870

Labanden opened this issue Jul 2, 2020 · 10 comments · Fixed by #1874
Assignees
Labels
6. not up to spec The expected behaviour per the spec doesn’t match the observed behaviour. PR submitted A PR has been submitted, but not accepted yet.

Comments

@Labanden
Copy link

Labanden commented Jul 2, 2020

EDDI version in which issue is found

3.5.3-b7, but may show in earlier versions

VoiceAttack version in which issue is found (as applicable)

1.8.5

Steps to reproduce

  1. See below
  2. See below

Observed

When logged in to Elite Dangerous with second account, using same logon to computer. EDDI and Voice attack do not recognise the ((EDDI ship location)) event. When logged on to EDDI with First account it does. No API is enabled in EDDI. Install of ED is the same and Voice attack and EDDI are also same install. Voice attack profile is the same.

Investigation

Have regressed EDDI to 3.5.2, uninstalled both VA and EDDI.

To be honest not sure if this is ED, EDDI or VA. Just need help to resolve the issue.

@Tkael
Copy link
Member

Tkael commented Jul 2, 2020

I'm not sure I follow exactly what you are describing but EDDI's configuration settings are stored per Windows account and using multiple commanders with the same Windows account is not currently supported (see #505). If you are attempting to use EDDI with multiple ED accounts from a single Windows login then your config files have likely become a corrupt mixture of data from both ED accounts. This could cause various events to fail or to not behave as expected.

@Labanden
Copy link
Author

Labanden commented Jul 2, 2020 via email

@Tkael
Copy link
Member

Tkael commented Jul 2, 2020

If the issue occurs with two separate ED accounts each on a different PC then please clarify further what exactly is wrong / not working as expected. Please provide a complete description, including screenshots if possible, to show what you have set up in your profile and what you expect to happen.

@Labanden
Copy link
Author

Labanden commented Jul 3, 2020 via email

@Tkael
Copy link
Member

Tkael commented Jul 3, 2020

The title of the ticket says ((EDDI ship loadout)) but twice now you've described the event that you're trying to capture as ((EDDI ship location)). ((EDDI ship location)) does not exist / is not a valid command name. Please clarify which event you are trying to trigger and double check that your VoiceAttack commands are referencing the desired event correctly. It should be either:

If the command name in your VoiceAttack profiles are correct, please provide log files so that we can check for logged exceptions / errors. The log files will be located at %appdata%/EDDI and end with the .log suffix. Please add them to a .zip file and attach the .zip file to this ticket.

@Tkael Tkael added the question label Jul 3, 2020
@Labanden
Copy link
Author

Labanden commented Jul 3, 2020 via email

@Tkael
Copy link
Member

Tkael commented Jul 3, 2020

Thanks for clarifying. I need the logs requested above (ideally with a screenshot of the VoiceAttack command for context) to look for any issues in the back-end code.

@Labanden
Copy link
Author

Labanden commented Jul 4, 2020

Thanks for clarifying. I need the logs requested above (ideally with a screenshot of the VoiceAttack command for context) to look for any issues in the back-end code.

EDDI Logs.zip
VA extracts.zip

Note have modified EDDI.vap to use the Ship Loadout event to call the ship variables command, on the secondary it does not happen. On Primary it does. again on different Windows installs (But same versions of every thing)

@Tkael
Copy link
Member

Tkael commented Jul 4, 2020

Ok. Looks like the ((Ship loadout)) event is throwing an exception while being parsed.

System.InvalidOperationException: Nullable object must have a value.
   at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
   at EddiJournalMonitor.JournalMonitor.parseShipCompartment(String ship, String slot)
   at EddiJournalMonitor.JournalMonitor.ParseJournalEntry(String line, Boolean fromLogLoad)

That exception causes the event to fail / not execute in VoiceAttack.

Essentially, there was a problem with EDDI's internal definitions where we weren't expecting to see a military slot on Eagle Mk. II.

I've submitted PR #1874 to correct the exception. In the meantime, the issue may be resolved if you either use a different ship or remove the module from the military slot in your current ship.

@Tkael Tkael added 6. not up to spec The expected behaviour per the spec doesn’t match the observed behaviour. PR submitted A PR has been submitted, but not accepted yet. and removed question labels Jul 4, 2020
@Tkael Tkael self-assigned this Jul 4, 2020
@Labanden
Copy link
Author

Labanden commented Jul 4, 2020

Confirmed if I remove the Military slot entry it does allow the event to respond. Thanks for your help. Please pass on to all involved with EDDI I really appreciate the App. It is an excellent addition to Voice Attack

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. PR submitted A PR has been submitted, but not accepted yet.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants