Discussion Warning! Galaxy Map operating beyond safety limits.

i finally got an odyssey character into the system and FSS to generate the logfiles BodyID's. Including asteroids, barycentres and rings, there are 77 bodies in the system. unfortunately, its a layer G system , so only the first four bodies (two suns, a barycentre and an asteroid) are targetable by the overflow method. If there is a hidden spacestation here, it will be body 78. If anyone has any other ideas or suggestions, I'd appreciate your thoughts. cheers
 
i finally got an odyssey character into the system and FSS to generate the logfiles BodyID's. Including asteroids, barycentres and rings, there are 77 bodies in the system. unfortunately, its a layer G system , so only the first four bodies (two suns, a barycentre and an asteroid) are targetable by the overflow method. If there is a hidden spacestation here, it will be body 78. If anyone has any other ideas or suggestions, I'd appreciate your thoughts. cheers
? the layer does not limit how many bodys are targetable. the Body ID is always the 9 most significant bits. thus having a max of 512 0-511 ID per System, no matter what layer
Lets say u have something Like SectorName FG-Y G15 and wanne target Body
5: 15 + 5 * 2^29 -> SectorName FG-Y G2684354575 (whit explicit System ID ...FG-Y G0-15 -> ...FG-Y G0-2684354575)
6: 15 + 6 * 2^29 -> SectorName FG-Y G3221225487
...
78: SectorName FG-Y g0-41875931151
 
Thanks for this :)

I've thrown together a python script to simplify looking up the addresses and copy them to the clipboard to assist in tracking down the HyperbolicOrbiters believed to be associated with the new Thargoid anomaly:

https://github.com/DarkStarSword/edgalmap

e.g. Looking up Sol:

Code:
./edgalmap.py 10477373803
Copied to clipboard: "Wregoe AC-D d12-0"

e.g. Looking up various HyperbolicOrbiters:

Code:
./edgalmap.py Oochorrs UF-J c11-0 --body-id 17
Copied to clipboard: "Oochorrs UF-J c11-2228224"

./edgalmap.py 1327473756 -b 17
Copied to clipboard: "Oochorrs GR-V e2-142606336"

./edgalmap.py Col 69 Sector LM-U c3-1 -b 28
Copied to clipboard: "Col 69 Sector LM-U c3-3670017"

More info on the anomaly hunting: Source: https://www.reddit.com/r/EliteDangerous/comments/x469h2/following_the_breadcrump_trail_thargoid_anomaly/
 
The method fails for some systems - the generated string causes a crash but there is a gap in the bodyid between the last one that works and a known space station. E.g Colonia, Tir, Luchtaine;
 
Last edited:
The method fails for some systems - the generated string causes a crash but there is a gap in the bodyid between the last one that works and a known space station. E.g Colonia, Tir, Luchtaine; see my body search sheet via signature link
In systems that have been overwritten by hand, this may well be the case. Maybe the developers want to leave room for possible future additions. It may even be that some systems have bodies that only got an ID halfway, or something. You can only find out by trying all 512 possibilities. And even then, there may be placeholders that simply don't work by design. But who wants to see over 500 CTDs for just one system. Did that once, took a little over 24 hours. I guess I still haven't fully recovered from it. o_O
 
In systems that have been overwritten by hand, this may well be the case. Maybe the developers want to leave room for possible future additions. It may even be that some systems have bodies that only got an ID halfway, or something. You can only find out by trying all 512 possibilities. And even then, there may be placeholders that simply don't work by design. But who wants to see over 500 CTDs for just one system. Did that once, took a little over 24 hours. I guess I still haven't fully recovered from it. o_O
Possibility of future additions is ok, but can we be sure that there aren't currently bodyids that aren't being detected?
(E.g. Raxxla?? 🥺)
 
hey mods this can be closed since it is obsolete now.
no actually not if i think about it. still useful to know how System Names are derived from System Addresses.
 
Last edited:
Someone just made a new script for this... how is this obsolete? Did FDev patch it so it's become impossible now?
it got patched today. u can no longer search for Body IDs, but i changed my mind. i still think its useful to at least know how System Name work. u still can find potential System names for given Coords and so on. just the carry bits in the body ID part is of no use anymore.
 
Any work done on translating the SystemAddress.

Trying to translate 90440608533569
spreadsheet gives as gazelle wrote:
Pyroomuae FM-Q b7-41
somewhere in the 20ly Boxel with this center:
-29075 x1745 y24705 z

SystemIDSector:XBoxel:xSector:ZBoxel:zSector:YBoxel:yLayer
41162133243881

 
Last edited:
Back
Top Bottom