New bug introduced with today's tick/weekly tick?
Signal 10
- Thread starter Mavadelo
- Start date
-
- Tags
- #fss question
No
I had it yesterday around 19:00 server time.
I'm guessing obviously but I think it's not a bug but the intended way for finding that thing in the Oochorrs sector. An extra signal that encourages an extended FSS leading to something that sounds very much like a high mass body without anything apparent. Repeating this in a few systems one might notice it always pointing in the same direction, ultimately leading to that sector (and a premature change of undies).
Sounds to me like something intentionally designed for the explorer crowd to pick up on. Shame it got insta-solved by another "coincidence" (allegedly).
Sounds to me like something intentionally designed for the explorer crowd to pick up on. Shame it got insta-solved by another "coincidence" (allegedly).
So everyone, ok, but not Horizons 3.8 users, so it's Odyssey and something to do with the anomaly and not a bug in the FSS because the FSS is the same for both verisions, and is new but not caused by yesterday's update because it was happening before that restart, also it wasn't happening after the previous week restart or I would have noticed it, this is not something I would have missed. I never noticed it before a lot of the noise about the anomaly started being made, so I am assuming when the presence of the anomaly was announced that was really just shortly after it appeared, interesting, I guess the new 4.0 build allows them to add major features between server restarts as long as it is a server side update.
It's funny getting 2 signals in the FSS for a single star system with no asteroids lol.
I doubt that's true in the general case. My guess would be that the anomaly code was added with the update but set to remain dormant until the server gave the go-ahead. It's still very nice to see that they have more abilities now to do events where things are evolving hour by hour instead of one Thursday at a time.
"It's a Countdown!"
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.
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.
Yeah that does look strange, I haven't had any more than 1 extra signal at all anywhere. There are no asteroid belts in the system map? Nothing in the nav panel?
Then maybe the full system data didn't properly download from the loading procedure, I have sometimes had invisible planets and other weird thing, these fix themselves, have you tried jumping out and back in again and see of that changes things? I agree the FSS isn't perfect, my game crashes on the odd occasion using the FSS, and sometimes that new feature that tells you whether or not there's a fuel star just doesn't appear at all for some jumps, so there is certainly room for bugs.
Hey glad you mentioned it I noticed this and figured I was not looking off the orbital plane effectively enough; I looked and looked but never quite certain sometimes. But it happened repeatedly to me as well, recently, about a few days ago.
(I thought I also seen something in the concentrated range but was misunderstanding - yeah handing myself my own _ss on that)
Last edited:
Yes. I also quit to desktop and came back. Still the same.
Was wondering that myself, but I still only get 1 extra signal!
By checking here: Link, it shows 11 bodies.And now suddenly way over here I have the exact same issue, I wonder if this could be something to do with the new anomoly? Maybe we are all detecting it? I have never seen this issue previously, they all normally add up;
Afaik, there are 2 classes of signals in logs:
- BodyCount (stars, planet)
- NonBodyCount => i still don't understand this one. Stations (and FC too), tourist beacons, NSP (Notable Stellar Phenomena) are counted. Weird thing: when you honk the system WITHOUT targeting any comet, it shows you a number. But when you target a comet and honk again, the number increase by 1 (the comet is counted in NonBodyCount class) but will not keep the increase if you un-target the comet.
In your picture of FSS, right up:
Bodies=BodyCount
Signals Detected=BodyCount+NonBodyCount
The missing element was here way before U13.
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.
Here's a post from another guy that's seeing more than 1 extra signal (click the link, don't just read the summary here):
forums.frontier.co.uk
Gotta just be a bug, right?
Signals: 17, Sources: 16
Greetings, I have a problem, which I can't solve (nor find it in the issue tracker or forums). Jump -> Scoop -> Scan -> Ride -> Stop -> VSS -> Detected Signals: 17 -> bodies: 12/12, asteroids: 4. I scanned every planet, every ring, landed where possible. One missing Signal Source. Any ideas?
Gotta just be a bug, right?
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.
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.