Release EDDiscovery 18.X is now out! New modules panel upgrade and Engineering

I have an unusual situation in the Tahumbla system. I've just arrived, sent a disco honk and run FSS to pick up all the bodies, as apparently I've not been here before.
The scan window is not showing all the bodies in orbit about the binary system (AB1 - AB8) unless I also tick either EDSM, Spansh, or both to show their data.
I've for sure scanned them
e.g.
Code:
[EDDN] Sent Scan event (Detailed scan of AB 2)
[EDDN] Sent Scan event (Detailed scan of AB 8)
But they only show up when I enable the external data sources. Any idea why?
 
I have an unusual situation in the Tahumbla system. I've just arrived, sent a disco honk and run FSS to pick up all the bodies, as apparently I've not been here before.
The scan window is not showing all the bodies in orbit about the binary system (AB1 - AB8) unless I also tick either EDSM, Spansh, or both to show their data.
I've for sure scanned them
e.g.
Code:
[EDDN] Sent Scan event (Detailed scan of AB 2)
[EDDN] Sent Scan event (Detailed scan of AB 8)
But they only show up when I enable the external data sources. Any idea why?
Impossible to say without at least a screenshot and your journal from that session.
Join our Discord or open an issue on GitHub for further assistance.
 
I have an unusual situation in the Tahumbla system. I've just arrived, sent a disco honk and run FSS to pick up all the bodies, as apparently I've not been here before.
The scan window is not showing all the bodies in orbit about the binary system (AB1 - AB8) unless I also tick either EDSM, Spansh, or both to show their data.
I've for sure scanned them
e.g.
Code:
[EDDN] Sent Scan event (Detailed scan of AB 2)
[EDDN] Sent Scan event (Detailed scan of AB 8)
But they only show up when I enable the external data sources. Any idea why?
I get this a fair amount and I think it correlates with good old Cmdr Validating stinking the place up.
Thanks for the prod to update to latest and report this properly on Discord...
 
This has happened to me randomly for some time now as well. Clicking the refresh icon next to the commander selection box always corrects it. It isn't corrected instantly, but it does seem to take less than a full minute. I figured this was normal with three commanders, almost 2300 journal files, and three apps accessing them at the same time.
 
Could all of you who are affected by this please note down which panels you are using (all of them) and which of them might be set up to get data from EDSM or Spansh?
 
Could all of you who are affected by this please note down which panels you are using (all of them) and which of them might be set up to get data from EDSM or Spansh?
Would it help more if I provide specific files from EDD at the time this is happening? If so, let me know what to copy, and I'll get them to you via Discord soon after. I expect it to happen a few times over the weekend at least.
 
Would it help more if I provide specific files from EDD at the time this is happening? If so, let me know what to copy, and I'll get them to you via Discord soon after. I expect it to happen a few times over the weekend at least.
Sadly no. We got some journals from such sessions, but we can't reproduce it with them. It has to be some obscure settings or panel combination that we simply don't have set.
 
I believe I've added nine tabs to date. I still have the default History (grid) tab. Next to that, I have an Exploration (grid) tab. The Exploration grid includes System Information and Scan (screenshot below). After that, all tabs are standalone or default (no grid tabs). I also use the compass overlay on my center display (3840 x 2160 @ 150% scaling). EDD runs on my left display (1920 x 1200 @ 100% scaling). I have four displays overall.

The following screenshot illustrates all the other tabs I have setup. It also shows the most recent system that required clicking the "refresh the history" icon. A, ABC, AB 1, and AB 2 appeared immediately after the initial system honk. I then entered FSS, and zoomed in on AB 1 and AB 2 to uncover possible signals. After that, I continued to FSS the system. EDD's scan panel did not update after discovering ABC 2 and all it's moons, so I clicked the update icon at that time. After less than a minute, it refreshed, and further discoveries populated the scan panel normally.

I've noticed that the "Scan ##/##" at the top of the scan window almost always shows as if I've already discovered everything in the system. I could be mistaken, but I think it used to increment as bodies were newly discovered. In this particular system, it showed 38/38 right after the initial system honk. That may be related, so I thought it was worth sharing.

Let me know if there's anything else I can do to help.

Edit: I forgot to mention, the scan panel on my History tab is set to update from EDSM and Spansh. None of my other tabs are. I just discovered that, and have turned off the updater on the History tab. Also: this commander doesn't have a carrier. The carrier tab is only used by one of my three commanders for now.

Exploration Tab.jpg
 
Last edited:
I've noticed that the "Scan ##/##" at the top of the scan window almost always shows as if I've already discovered everything in the system.
That's a bug, thanks for mentioning. Basically the body count from panels that query Spansh or EDSM bleeds into the scan panel even if itself doesn't query the web.
 
I believe I've added nine tabs to date. I still have the default History (grid) tab. Next to that, I have an Exploration (grid) tab. The Exploration grid includes System Information and Scan (screenshot below). After that, all tabs are standalone or default (no grid tabs). I also use the compass overlay on my center display (3840 x 2160 @ 150% scaling). EDD runs on my left display (1920 x 1200 @ 100% scaling). I have four displays overall.

The following screenshot illustrates all the other tabs I have setup. It also shows the most recent system that required clicking the "refresh the history" icon. A, ABC, AB 1, and AB 2 appeared immediately after the initial system honk. I then entered FSS, and zoomed in on AB 1 and AB 2 to uncover possible signals. After that, I continued to FSS the system. EDD's scan panel did not update after discovering ABC 2 and all it's moons, so I clicked the update icon at that time. After less than a minute, it refreshed, and further discoveries populated the scan panel normally.

I've noticed that the "Scan ##/##" at the top of the scan window almost always shows as if I've already discovered everything in the system. I could be mistaken, but I think it used to increment as bodies were newly discovered. In this particular system, it showed 38/38 right after the initial system honk. That may be related, so I thought it was worth sharing.

Let me know if there's anything else I can do to help.

Edit: I forgot to mention, the scan panel on my History tab is set to update from EDSM and Spansh. None of my other tabs are. I just discovered that, and have turned off the updater on the History tab. Also: this commander doesn't have a carrier. The carrier tab is only used by one of my three commanders for now.

View attachment 391859
This was very helpful. Using that setup I was already able to reproduce the issue.
Screenshot 2024-05-04 210106.png

That's a big step forward to identifying the underlying issue.
 
That's a bug, thanks for mentioning. Basically the body count from panels that query Spansh or EDSM bleeds into the scan panel even if itself doesn't query the web.
These might be coincidence, or might be related:

I haven't had to use the refresh icon since disabling the "update from EDSM/Spansh" option on the history tab's scan window. I just completed a trip back from the NGC 7822 Nebula, about 25 jumps. The scan panel worked perfectly in every system. I'm taking a break from exploration for a few days. I'll add another reply if I see any more issues.

I'm not sure how the update was turned on at the History tab. I did use it once on my Exploration tab, right after it was updated. After trying it out, I turned it back off. It might have stayed on at the History tab, or it might be something totally different. I figured it was worth mentioning, just in case.
 
Is there something going on with exploration (especially mapping) payouts?

Running a new commander around some engineers I mapped the Earth-like world Rhodius - EDD recons it was worth over 1.5Mcr but on selling the data it was only 421,925cr.

Now I don't care about the amount, just flagging up that EDD seems to be widely out on this. I have not checked on other saves (out in the black / first discovery for example).

not right.jpg
 
It is impossible to correctly estimate the value of many bodies in the bubble. Even the game isn't sure about their values; some stations display amount X for body Z, and some display amount Y for the same body Z. There are also reports that the shown value and the actual received value are different.
There's nothing we can do about that, so we estimate them at a value that is (presumably) too low in most cases.
 
Last edited:
Back
Top Bottom