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

Possible log crossover information #641

Closed
LordNyte opened this issue Jun 12, 2018 · 3 comments
Closed

Possible log crossover information #641

LordNyte opened this issue Jun 12, 2018 · 3 comments
Labels
duplicate Please comment with the duplicate ID and close

Comments

@LordNyte
Copy link

EDDI version in which issue found

[please give the full version number here, not just "latest" or "current", and also say whether you are running under Voice Attack or standalone]

Steps to reproduce

  1. [give the fullest and most reproducible steps you can]
  2. [the more reproducible, the better our chances of fixing it]

Expected

[describe what you expected to happen]

Observed

[describe what happened instead]

Investigation

[any investigation you have done, regression tests against earlier versions, etc]

@LordNyte
Copy link
Author

Hello. I'm using EDDI v.3.0 within VoiceAttack 1.7, and as a standalone. I usually use it within VA, but since this issue appeared, I've been running standalone to try to fix. I have 2 Elite Dangerous accounts, and keeping the data separate on EDSM and EDDI has been a chore, but so far successful. Until 3 days ago. I have a python in my 1st account, and a cobra in my second account. EDDI seems to think that the cobra, is the python. I have tried to resolve the mistake best I can, but it doesnt seem to work. EDDI always sees the cobra as the python from a different account. Thats the best and shortest way I know how to describe the problem. I could really use some help with this as I don't want the 2 account info to get merged.

@Tkael
Copy link
Member

Tkael commented Jun 12, 2018

Closing as a duplicate of #505.
EDDI's config files are currently saved to %APPDATA%/EDDI and are unique to your Windows account. The cleanest workaround is to use different Windows logins for each account.

@Tkael Tkael closed this as completed Jun 12, 2018
@Tkael Tkael added the duplicate Please comment with the duplicate ID and close label Jun 12, 2018
@Tkael
Copy link
Member

Tkael commented Jun 12, 2018

.It sounds like your config file has been corrupted by using multiple accounts. You may wish to delete your current data at %APPDATA%/EDDI/shipmonitor.json and let EDDI rebuild it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Please comment with the duplicate ID and close
Projects
None yet
Development

No branches or pull requests

2 participants