-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
'whats left to scan' reporting a blank list when entering system #64
Comments
Ah, good. I was worried I hadn’t understood what happened there. For the record, close or not doesn’t matter for stars. The trigger here is a race condition when you finish scanning the entire system (that triggers this) too fast after entering a system. That can happen when you don’t have anything left to scan after honking because there are either only stars or only stars and bodies that are within honking distance (50 ls). NB: that should also be able to happen when you have the “announce R2R mapping candidates” option enabled since that triggers this after honking, no matter the system scan state. Moving it from the Bottom line is still: this looks like an EDDI issue to me. I suspect that it’s not done getting system data from EDSM yet when this happens, and the |
So current EDDI beta lists this change:
I suspect this bug here might be the result of a race condition that existed before, when the new system name had not been set. So the beta might fix this. |
@SiIason have you run into this since? I haven’t, but I haven’t really been looking out for it. |
Just ran into this, so it’s definitely still a thing :-/ |
Anyone still seeing this? I’m not really playing anymore so couldn’t tell. |
Happening when one a single star in the system,
Have since noticed it once when 2 stars were in close.
The text was updated successfully, but these errors were encountered: