Signal 10

a bug
interesting phrase

it could be, but I am inclined to think fdev is paying very close attention to this 'anaomaly' and are aware of this scan discrepancy
I expect it is an expected effect from whatever is going on.

so many tin hat threads at this time, fun stuff.
I posted out of confusion. I never encountered this before. I want to know what it is. I kinda expected to get one comment reading "known bug" or something.
 
No it wasn't, I would have noticed if the numbers weren't correct previous to update 13, up until a couple of days ago the number was ALWAYS correct, it's only since the anomaly has appeared that it has played up. There is no other object in the system that shows up on the honk. You have also forgotten USS and human/thargoid conflict zones, they also appear as non-body counts.
I forgot USS in NonBodyCount indeed (y).
I'm currently at Oochorrs CS-F c13-0 and the count is here. In another system like Oochorrs NI-R d5-0, there is 1 signal unknow (not a comet, not the FC on the system, and no pending FC on depart/arrival).

Mea culpa: as i never look at USS, the counts were always good in my old logs.
In NonBodyCount i have so far:
  • Stations/FC
  • Installations
  • Nav Beacons
  • Tourist Beacons
  • NSP
  • Asteroid Clusters (not asteroid origin)
  • USS

It seems to be a nice bug indeed if you are so far from Oochorrs systems.
By the past, people reported multiple triggers of "FSSDiscoveryScan" event (triggered by each star in system) but the count of bodies were good.
It's either a bug or "intended feature" :p
 
Certainly agreed there, but the extra signals above 1 for some people strongly tend towards the bug explanation, I haven't seen any more than 1 so far so keeping my mind open, but not so open my brains fall out :ROFLMAO:
Someone said (watching too many threads at a time) that the bug may be odyssey-related.
Maybe it doesn't exist in horizons. I cant check right now but i'll do it later.
 
So I'm out in the Norma Arm, pretty far from everything. I check a couple of systems and I saw the extra signal.

But then there was this system. I'm the only one here, it's uninhabited. My carrier is in another system. It's just me and my DBX. But I'm seeing 19 signals, 4 more than the number of bodies.

This makes me think "bug" more than "interesting feature."

To be honest I've never really paid attention to that number.

View attachment 320200

Ah I had to come back to this again, you have 4 more signals than the number of bodies, but that number of bodies doesn't count the stars does it? Looks like you have 3 asteroid clusters, 2 rocky and 10 icy bodies and, yes that's 15, and then the number of stars? Because your count here of bodies and signals doesn't include the stars, whereas mine do. My latest system shows 10 signals, 9 of 9 bodies, but only 8 listed in the FSS because the 9th is the star. Yours shows 15 of 15 bodies, your count in the FSS adds up to 15, but it shouldn't, it should only total at the most 14. That's bizarre! Where are your stars? You have none at all!

Here's mine, the number of bodies shown in the FSS should ALWAYS be lower than the total number of bodies by at least one or more!

MpWWb08.jpg



Ah I get it, the asteroid clusters don't count as bodies, the total number of bodies listed in your screenshot is actually 12, the three asteroid clusters add 3 signals, that's 15 signals, and then the stars need to be added, so I am assuming your system has 3 stars, which would make 18 signals, and an extra would be the 1 extra signal we are all seeing, can you confirm if that is correct? If it is then a lot of players are making the same mistake.

It appears to be confusion caused by the number of discovered objects adding up to the exact same number of bodies, but they don't, there's actually 3 less.

If I am right and you have 3 stars then you actually only have 1 extra signal!
 
Last edited:
{ "timestamp":"2022-07-30T19:04:58Z", "event":"FSSDiscoveryScan", "Progress":1.000000, "BodyCount":1, "NonBodyCount":0, "SystemName":"Bei Dou Sector CQ-Y b4", "SystemAddress":9466510845337 }
{ "timestamp":"2022-08-15T16:01:43Z", "event":"FSSDiscoveryScan", "Progress":1.000000, "BodyCount":1, "NonBodyCount":0, "SystemName":"Bei Dou Sector CQ-Y b4", "SystemAddress":9466510845337 }
{ "timestamp":"2022-09-02T14:29:49Z", "event":"FSSDiscoveryScan", "Progress":1.000000, "BodyCount":1, "NonBodyCount":1, "SystemName":"Bei Dou Sector CQ-Y b4", "SystemAddress":9466510845337 }

{ "timestamp":"2022-08-06T10:40:45Z", "event":"FSSDiscoveryScan", "Progress":1.000000, "BodyCount":1, "NonBodyCount":0, "SystemName":"Bei Dou Sector CQ-Y b3", "SystemAddress":7267487589785 }
{ "timestamp":"2022-08-15T16:00:50Z", "event":"FSSDiscoveryScan", "Progress":1.000000, "BodyCount":1, "NonBodyCount":0, "SystemName":"Bei Dou Sector CQ-Y b3", "SystemAddress":7267487589785 }
{ "timestamp":"2022-08-15T16:01:13Z", "event":"FSSDiscoveryScan", "Progress":1.000000, "BodyCount":1, "NonBodyCount":0, "SystemName":"Bei Dou Sector CQ-Y b3", "SystemAddress":7267487589785 }
{ "timestamp":"2022-08-28T23:02:51Z", "event":"FSSDiscoveryScan", "Progress":1.000000, "BodyCount":1, "NonBodyCount":1, "SystemName":"Bei Dou Sector CQ-Y b3", "SystemAddress":7267487589785 }

{ "timestamp":"2022-08-03T00:24:27Z", "event":"FSSDiscoveryScan", "Progress":1.000000, "BodyCount":3, "NonBodyCount":0, "SystemName":"Gliese 9263", "SystemAddress":1041303079267 }
{ "timestamp":"2022-08-03T04:18:17Z", "event":"FSSDiscoveryScan", "Progress":1.000000, "BodyCount":3, "NonBodyCount":0, "SystemName":"Gliese 9263", "SystemAddress":1041303079267 }
{ "timestamp":"2022-08-31T04:46:56Z", "event":"FSSDiscoveryScan", "Progress":1.000000, "BodyCount":3, "NonBodyCount":1, "SystemName":"Gliese 9263", "SystemAddress":1041303079267 }

{ "timestamp":"2022-08-22T02:35:11Z", "event":"FSSDiscoveryScan", "Progress":1.000000, "BodyCount":2, "NonBodyCount":0, "SystemName":"Synuefe FE-L c10-3", "SystemAddress":909022859866 }
{ "timestamp":"2022-08-28T16:02:17Z", "event":"FSSDiscoveryScan", "Progress":1.000000, "BodyCount":2, "NonBodyCount":1, "SystemName":"Synuefe FE-L c10-3", "SystemAddress":909022859866 }



I couldn't find a real paydirt either except, I reviewed over about 700 systems in my logs that originally had a Non Body Count of zero, since I set this computer up in July, and the earliest I see of this were 8/28 (Sunday), and there's a few samples in the raw which changed to 1.
-- My 20th/21st century friend knows a little sed, grep.. even jq could be of great utility for this kind of research.. but, he mainly comes here to get away from all that :).
 
Last edited:
Ah I had to come back to this again, you have 4 more signals than the number of bodies, but that number of bodies doesn't count the stars does it?

Ah I get it, the asteroid clusters don't count as bodies, the total number of bodies listed in your screenshot is actually 12, the three asteroid clusters add 3 signals, that's 15 signals, and then the stars need to be added, so I am assuming your system has 3 stars, which would make 18 signals, and an extra would be the 1 extra signal we are all seeing, can you confirm if that is correct? If it is then a lot of players are making the same mistake.
I'm fairly sure any stars are included in the body count: when you start to scan a system the body count never starts at zero, always at the number of stellar objects (plus any planets close enough to the entry point to be scanned automatically).
This is my current system:
1662134670736.png

The analysis shows:
6 asteroid clusters (not counted) and 13 HMC + 3 rocky bodies = 16
Adding the two stars to the planets gives 18/18 bodies, 6 clusters and one unknown signal.
I haven't been paying attention either.

One thing I haven't come across in the last recent thousand unmapped systems are any Notable Stellar Phenomena.

Edit: @varonica - I may have misread your post: the Analysis strip doesn't show stellar bodies; if I got this wrong, apologies.

Edit 2: Just checked this system in Horizons - signal count = 24.
 
Last edited:
I'm fairly sure any stars are included in the body count: when you start to scan a system the body count never starts at zero, always at the number of stellar objects (plus any planets close enough to the entry point to be scanned automatically).
This is my current system:
View attachment 320326
The analysis shows:
6 asteroid clusters (not counted) and 13 HMC + 3 rocky bodies = 16
Adding the two stars to the planets gives 18/18 bodies, 6 clusters and one unknown signal.
I haven't been paying attention either.

One thing I haven't come across in the last recent thousand unmapped systems are any Notable Stellar Phenomena.
Yes, Stars, planets and moons are all in the "bodies" (I think Black Holes as well) All other detectables are only in the signals.
 
I'm fairly sure any stars are included in the body count: when you start to scan a system the body count never starts at zero, always at the number of stellar objects (plus any planets close enough to the entry point to be scanned automatically).
This is my current system:
View attachment 320326
The analysis shows:
6 asteroid clusters (not counted) and 13 HMC + 3 rocky bodies = 16
Adding the two stars to the planets gives 18/18 bodies, 6 clusters and one unknown signal.
I haven't been paying attention either.

One thing I haven't come across in the last recent thousand unmapped systems are any Notable Stellar Phenomena.

Edit: @varonica - I may have misread your post: the Analysis strip doesn't show stellar bodies; if I got this wrong, apologies.
Starting from left of scanner, there are low emission degraded signals, NHSS, comets (concentrated signal sources) and then NSP just before asteroid clusters.
In this picture, the missing signal is a bug (no USS, no NSP).
 
I'm not sure I'm following your logic exactly, but the system does indeed have 3 stars.

Therefore you have the correct number of signals, plus one. 12 planets, 3 asteroid clusters and 3 stars make 18 signals. You have, like the rest of us, 1 extra signal, not 4. The easiest way to double check is to count the number items in the nav panel, each body and signal including stars will appear there, if you were still in the area you can go back and count them, it will total to 18.

I think we can say that people getting extra signals over the normal 1 extra are actually misreading the data, it's easy to do, I only realised it when I thought I had extra signals above 1 and had to spend 5-10 minutes checking everything before realising that yes, I only had 1 extra, and checking the nav panel count confirmed that.
 
Last edited:
It seems fDev has started an ARG of sorts. The binary code decripted at 03:44 reads "Just because you can't see something, doesn't mean it is not real"
Which could be pointing to our mysterious signal.
We can't "see" it, but it is definitely there.
 
It seems fDev has started an ARG of sorts. The binary code decripted at 03:44 reads "Just because you can't see something, doesn't mean it is not real"
Which could be pointing to our mysterious signal.
We can't "see" it, but it is definitely there.

A would think that refers to the Anomaly and not necessarily to a meaningless extra signal while fss-ing a random system
 
Back
Top Bottom