search

EDCD / EDDI

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

EDDI "Lost track of things" upon second jump from starting system at time of login #1103

Closed angrmgmt closed 5 years ago

angrmgmt commented 5 years ago

EDDI version in which issue found

v3.3.4-b1, running as VoiceAttack plugin.

Steps to reproduce

  1. Log in.
  2. Jump to new system. FSS, fly to and map all bodies.*
  3. Jump to third system (from login system). No error jumping back to starting system.*

Expected

Nothing, actually. At most, the default 'Fuel check' script would fire. I have not modified the 'Jumped' script; it is the default. I am hundreds of light years from the bubble, toward the southern rim.

Observed

Received spoken error message "Sorry commander, I've lost track of things and need you to high wake or relog to reestablish." (possible slight paraphrasing from memory)

Investigation

This never happened to me in my year-long history of using EDDI, and certainly not in the previous version (v3.3.3). Possibly related to #1102; it seems that maybe something has happened with the handling of the state global variable? Happy to provide any journal files, if needed.

Edit: Results of additional testing included in steps with *.

Tkael commented 5 years ago

Please provide a copy of the applicable journal file.

angrmgmt commented 5 years ago

Attached. Journal.190119074009.01.log

angrmgmt commented 5 years ago

If I jump to a new system, do nothing but honk and scoop, and then return to the previous system I was in, the error does not occur. This is after a log out and log in.

Edit: Unable to reproduce after the first two instances. I'm thinking maybe a Frontier issue? Not sure, but comment below me indicates that this wasn't just me.

kamikazeedriver commented 5 years ago

Ok I installed v3.3.4-b1 last night and it worked just fine. But this morning, I'm getting the exact same error and I haven't even turned on the game yet. Whether I directly load the EDDI (to pull up configuration) or let it load through VA, it will repeat that message about 8 times. "Sorry commander, I've lost track of things and need you to high wake or relog to reestablish."

randyDarsh commented 5 years ago

I've heading out on DW2, and I was also getting the same message with using the 3.3.4-b1. Jumping into any system would give the same message.

I have uninstalled the beta, and gone back to 3.3.3

kamikazeedriver commented 5 years ago

I should add, that I continued into the game after the message stopped repeating, and everything worked liked normal.

Tkael commented 5 years ago

Unclear what's going on here. When I load and "replay" your log file, I don't trigger the "Sorry commander" speech. If you still have the log file from this play session, would you please attach it here for review? Logs are located at %appdata%/eddi

angrmgmt commented 5 years ago

This is the oldest one I have, and might be it, but it might be from the next play session, where I could no longer reproduce it myself. I did too many tests that day, and it fell off the back end, I think. The timestamps approximately match the right UTC (if that's what it's using), but seems just a smidge later, and I'm not sure of the errors. I'm UTC - 7h. If it's timestamping local time, it's way later.

At the end there is a '[Warning] EDDNResponder:CheckLocationData The EDDN responder is in an invalid state and is unable to send messages.', but it seems it's from when I was leaving the game, apparently.

Hope it's not from too late a point in time, and also that this was just a transient issue that affected some people due to no fault of EDDI's.

eddi9.log

Redrayg commented 5 years ago

EDDI will not retain the details of my EDSM log. I can retrieve my EDSM log okay within EDDI as a stand alone which cancels the repeating voice that says "sorry commander I have lost track etc " However when i close the program and re-launch it the recurring voice comes back, indicating it has not retained the log, and when I check its asking me to obtain the log again. Any suggestions as to whats going on?

kamikazeedriver commented 5 years ago

By the way, I haven't had my variation of the problem anymore.
The day I had it, I tried exiting the program, and reloading. Still had it. Tried a pc restart. Still had it. So I posted here, and then went on into game. It behaved normally in game and I have not had it pop up again, so I never went looking for my log file.

JCanlett commented 5 years ago

this fix out yet?

luzclasil commented 5 years ago

+1 Having the same issue as well. I only use EDDI (3.3.4) to help identifying terraformables when FSSing without having to manually check the entire system map but this message is almost making me disable the program. I get it literally every single time I jump. And btw, not sure it it matters but I'm thousands of lys far from the bubble.

Tkael commented 5 years ago

If you're not using rc1, please try rc1 and let us know if it helps.

luzclasil commented 5 years ago

If you're not using rc1, please try rc1 and let us know if it helps.

I have absolutely no idea what rc1 means. But sure, I can give it a try (once I figure out what it actually is).

angrmgmt commented 5 years ago

I have absolutely no idea what rc1 means. But sure, I can give it a try (once I figure out what it actually is).

Pre-release versions of software are often classified into three broad groups: alpha (a), beta (b), and release candidate (rc). On the Releases page, you should see a tag appended to the end of the file name for any pre-release versions specifying which type of pre-release it is.

If you're interested in the topic, you can familiarize yourself with the idea of semantic versioning here. It demystifies and regularizes version numbers so that users (and developers) can keep themselves apprised of the dynamic status of projects and/or releases.

luzclasil commented 5 years ago

I have absolutely no idea what rc1 means. But sure, I can give it a try (once I figure out what it actually is).

Pre-release versions of software are often classified into three broad groups: alpha (a), beta (b), and release candidate (rc). On the Releases page, you should see a tag appended to the end of the file name for any pre-release versions specifying which type of pre-release it is.

If you're interested in the topic, you can familiarize yourself with the idea of semantic versioning here. It demystifies and regularizes version numbers so that users (and developers) can keep themselves apprised of the dynamic status of projects and/or releases.

I was running the beta so hopefully this version is going to work as intended. Thank you!

Edit: while I do need to perform some more testing, at first it seems to have solved it. Highly appreciate your fast response, thank you!

Tkael commented 5 years ago

Thanks for the support assist, @angrmgmt . :-)

angrmgmt commented 5 years ago

o7