I found a second Anomaly signal!

Searched the area around Slegi JD-W b46-0 found a empty Hyperbolic Orbiter that did not crash the game by drooping

{ "timestamp":"2022-09-09T19:52:49Z", "event":"SupercruiseExit", "Taxi":false, "Multicrew":false, "StarSystem":"Slegi GS-X b45-0", "SystemAddress":643840352649, "Body":"", "BodyID":17, "BodyType":"HyperbolicOrbiter" }

Slegi GS-X b45-278528

origin? i try to find more.
And more
From Reddit
 
Has anyone tried to triangulate a flightpath yet? Where is it coming from, where is it going?

I've noticed that, when in Slegi HI-W b46-0 and facing towards Slegi GS-X b45-0 so you can pick up the Stargoid, there's a galaxy in the background of the Stargoid that looks very much LIKE a Stargoid. As a matter of fact, at first I mistook the galaxy for the Stargoid. I'm currently heading in the general direction, trying to keep an as straight line as possible between Slegi HI-W b46-0, Slegi GS-X b45-0 and my next jump.

My theory is NOT that the Stargoid comes from that galaxy, but maybe from a system/planet in that direction. That is, until someone can confirm that the flight path of the Stargoid is going somewhere else entirely.

Second thought: has someone crunched the numbers for distance and flighttime yet? We assume Stargoid #1 launched somewhere in Barnard's Loop and is currently around system X. That means it has traveled X lightyears since activation. Assuming all Stargoids have launched at the same moment, Stargoid #2 should have traveled the same distance and may have started in a system without a permit lock, IF we can establish a rough flightpath
 
Second? I thought Buur's video today said there were up to three more!


STARGOID COMPLETED IT.jpg
 
Last edited:
Second? I thought Buur's video today said there were up to three more!


View attachment 321434

Second? I thought Buur's video today said there were up to three more!
there is one fss noise if facing coalsack from near T Tauri, apparently one towards sag a also but that one hasnt been properly heard and might be the same one depending where the cmdr was....So 3 like the 3 artistic splashs in the image posted by Sally
 
i am 0.57 ly away from the system and i can see a red faint dot!

Good job OP! You deserve applause!




20220910053808_1.jpg


Edit:
At 0.80 ly from the main star, the spiral arms became normally visible. It also appears with the normal screenshot (f 12).

This is a zoomed in high resolution screenshot. Nothing was done except zooming and converting to jpeg format.

2.jpeg

HighResScreenShot_2022-09-10_03-54-45-_2_.jpeg
 
Last edited:
Hello everyone, there is something that puzzles me, it was some time that I had all the time a signal (other than planet and star) in addition to what was really visible (for example by going to a system without any signal and just a star it told me that there was a signal (extracted from the log: "event": "FSSDiscoveryScan", "Progress":1. 000000, "BodyCount":1, "NonBodyCount":1, "SystemName": "Wredguia NJ-C c28-1", "SystemAddress":358596776690 } ) now it gives me two more signals, while the ASF sees nothing (
Praea Euq VN-J c9-8_()_Stivl Writh_00001.png
see image
) is this a bug, or would this be related to the anomaly? (extract from the log : { "timestamp": "2022-09-10T06:55:53Z", "event": "FSSDiscoveryScan", "Progress":1.000000, "BodyCount":1, "NonBodyCount":2, "SystemName": "Praea Euq VN-J c9-8", "SystemAddress":2284083942226 }
 
Looks like Slegi SP-E d12-5 is next - missed the transit ( :( ) but when you target that system there's a faint red glow around it and you get a strong FSS signal pointing back towards the current system. 50 Ly though - long trip
 
Hello everyone, there is something that puzzles me, it was some time that I had all the time a signal (other than planet and star) in addition to what was really visible (for example by going to a system without any signal and just a star it told me that there was a signal (extracted from the log: "event": "FSSDiscoveryScan", "Progress":1. 000000, "BodyCount":1, "NonBodyCount":1, "SystemName": "Wredguia NJ-C c28-1", "SystemAddress":358596776690 } ) now it gives me two more signals, while the ASF sees nothing (
) is this a bug, or would this be related to the anomaly? (extract from the log : { "timestamp": "2022-09-10T06:55:53Z", "event": "FSSDiscoveryScan", "Progress":1.000000, "BodyCount":1, "NonBodyCount":2, "SystemName": "Praea Euq VN-J c9-8", "SystemAddress":2284083942226 }

There's a couple of threads on this subject, around the first anomaly was found and extra signal appeared in the FSS, around the time the second anomaly was found a second extra signal appeared in the FSS, therefore there's a good chance it's related, I suggest looking at the relevant thread.
 
Has anyone tried to triangulate a flightpath yet? Where is it coming from, where is it going?
Well, we have three data points now, but we have seven for the Oochorrs flare and that still jumps around a lot on estimated destination and origin every time we get an extra data point.

Plotting a straight line between the ends of its known path and extrapolating forward, it looks like it's heading for the bubble in terms of X and Z but will pass well underneath - it could be heading towards HIP 1254, if they're dog fans.

Extrapolating backwards is even trickier since we have no good idea when it set off and still a fairly poor idea of how fast it's going. It's not impossible that it set off from GS-X b45-0 on Thursday and the reason it wasn't detected earlier is that it wasn't making a noise earlier. If it's been travelling a while ... then still probably somewhere well below the plane in this part of the galactic arm, but further out from the bubble.
 
Back
Top Bottom