Glorious HIPs - 3306

OMG, it's full of stars. Ok, people have been before, but it's new to EDSM - had a double take when I spotted the 2 BH :D

lQ2JGo5.png
 
@Jackie Silver
I collated the HIP systems I've registered in EDSM since the original post:

HR 8689 - HIP 112924
HD 216876 - HIP 113407
HR 8509 - HIP 110311
HR 8889 - HIP 115433
HD 204128 - HIP 106031
HR 8233 - HIP 106419
HR 7992 - HIP 103206
HIP 103693
HR 8271 - HIP 107030
HR 8794 - HIP 114268
HIP 102426
HD 201484 - HIP 104613
HIP 41252
HIP 99496
HIP 93629

Don't want anyone to waste their time dragging around systems that are already recorded
 
Last edited:
@Jackie Silver
I collated the HIP systems I've registered in EDSM since the original post:

HR 8689 - HIP 112924
HD 216876 - HIP 113407
HR 8509 - HIP 110311
HR 8889 - HIP 115433
HD 204128 - HIP 106031
HR 8233 - HIP 106419
HR 7992 - HIP 103206
HIP 103693
HR 8271 - HIP 107030
HR 8794 - HIP 114268
HIP 102426
HD 201484 - HIP 104613
HIP 41252
HIP 99496

Don't want anyone to waste their time dragging around systems that are already recorded

Cool - as they're all systems that are in-game under their catalog numbers, they should be picked up and automatically added to the sheet (if not already, then when I run the next merge vs EDSM, which I'll do tomorrow) - I'll use this as a test that the merge is working as intended.
 
Cool - as they're all systems that are in-game under their catalog numbers, they should be picked up and automatically added to the sheet (if not already, then when I run the next merge vs EDSM, which I'll do tomorrow) - I'll use this as a test that the merge is working as intended.

I was tooling around and adding bookmarks to my map, going fast not, and came across a system that was listed in my slice but was way out of place, I think it must have been a mistake. I will post it later when I get a chance.
 
700 LY from Sol, HIP system, B class star and I'm getting 1st Discovered on all the gas giant moons.
Wasn't expecting that.
I've been very surprised at what I am finding still undiscovered. I found a completely virgin system just over 500ly from Sol. It's been interesting.

Slice 19 is completed minus one that I can't get to and one that resolves into empty space. I'm going to see if there's a route to the unreachable and then move on to another slice, I think. But first, I'm going to spend some time in Sothis/Ceos and get me a Vette. Had one on XBox and miss it on PC. @Factabulous, you still up for a trip to the unknown?
 
@Factabulous, you still up for a trip to the unknown?
Sure thing! DM me where you want picking up if you don't want these fiends snaffling it(y)

I seem to have been (un)luckier than some, with lots of high/low/far systems, so it would be good to help someone finish a slice as it looks like I'll be a while on mine :)
 
@Jackie Silver
I collated the HIP systems I've registered in EDSM since the original post:

HR 8689 - HIP 112924
HD 216876 - HIP 113407
HR 8509 - HIP 110311
HR 8889 - HIP 115433
HD 204128 - HIP 106031
HR 8233 - HIP 106419
HR 7992 - HIP 103206
HIP 103693
HR 8271 - HIP 107030
HR 8794 - HIP 114268
HIP 102426
HD 201484 - HIP 104613
HIP 41252
HIP 99496
HIP 93629

Don't want anyone to waste their time dragging around systems that are already recorded
Interesting - I'm also going through the HIP 110xxx range (as I worked out the coords before Jackie split the list into segments and didn't want to waste that work). So some overlap with your list.

I only came across one that was already in EDSM so far, but when I looked it up I found that the discoverer was ... me, yesterday - I'd forgotten to check it off my list :ROFLMAO: :oops:
 
Interesting - I'm also going through the HIP 110xxx range (as I worked out the coords before Jackie split the list into segments and didn't want to waste that work). So some overlap with your list.

I only came across one that was already in EDSM so far, but when I looked it up I found that the discoverer was ... me, yesterday - I'd forgotten to check it off my list :ROFLMAO: :oops:

Not the first time I have had that happen to me. After years of exploring I get to an area and wonder if anyone has been to that black hole before, I get there and it was, you guessed it, me. Oh well!
 
I'm now about half way through slice 14. 200 plus HIPs visited, and fully scanned. Another 200 to go.
I got to the point of needing my carrier to reach some very low stars, so brought the Iron Vengeance out to help.
Unfortunately I had forgotten that there was 10k tons of liquor on board rather than tritium, so have had to send her back.
Fortunately my alt account can do the refill.

I am amazed about how many systems have already been visited, but are not fully scanned or in EDSM. It just shows how few commanders are using EDdiscovery etc.
 
I've done the merge for today, looks like everything is working as it should be with the automatic recognition so I'm happy there. We're going well!

Ok here's a few strange ones, they were in my list but they aren't in my slice, HD 163428, which is 3kly out of my slice and HIP 66141 which is only around 500ly away from the slice towards the galactic core and HIP 55314 which is out of position the other way about the same. The closer ones I can get but it will take me into neighbouring slices but HD163428 is to far away to really bother with, I should leave that to the one doing that area, but there's a chance it won't be in their list so it may need to be added manually.
 
I'm getting almost half-way through my slice. Something that's mildly annoying, but not really unexpected, is just how far off the in-game systems can be from the catalog locations. I sorted the list by catalog distance, and in the game the distances are quite randomized, only "generally" following the distances. Since I'm trying not to delete my bookmarks, I'm only able to bookmark 10-20 of these at a time, and some are a distance away and I won't get to them for a while. So this is causing me to do a lot of zig-zagging and only hitting a few at a time. But, it's keeping me moving, which suits me well. ;)

 
Hit a major anomaly, and I mean major, system HD 106863 refuses to update in EDSM although I have scanned it, when I click on the button in EDDiscovery tp open EDSM with the system HD 106863 it jumps me instead to system Trienee OD-M c10-0, over 22,000ly away and there's also an entry in my journal indicating a jump to that system! A search in EDSM also indicates no records for system HD 106863, very strange, I will try jumping on and rechecking but it appears I may not be able to update that system, is it possible a duplicate index file in the galaxy database could be causing an issue? Have you come across this before?

When I check in the 3D map it clearly shows a 22kly jump to the core instead of to HD 106863.

Jumping to the next system didn't fix it, and now of course I have scanned them all I can't go back and try again because they have already been scanned by me, I may need another cmdr to fly out and test it, meanwhile I will just continue on with what I have and mark that as a problem system.

Checking my session log in game it doesn't show an anomalous jump to Trienee region so it looks like an issue only with EDDiscovery, but it will indeed require another cmdr to visit and scan, howver if you could kindly wait until I have turned in the data since it was all first discovery that would be much appreciated.
 
Last edited:
Hit a major anomaly, and I mean major, system HD 106863 refuses to update in EDSM although I have scanned it, when I click on the button in EDDiscovery tp open EDSM with the system HD 106863 it jumps me instead to system Trienee OD-M c10-0, over 22,000ly away and there's also an entry in my journal indicating a jump to that system! A search in EDSM also indicates no records for system HD 106863, very strange, I will try jumping on and rechecking but it appears I may not be able to update that system, is it possible a duplicate index file in the galaxy database could be causing an issue? Have you come across this before?

When I check in the 3D map it clearly shows a 22kly jump to the core instead of to HD 106863.

Jumping to the next system didn't fix it, and now of course I have scanned them all I can't go back and try again because they have already been scanned by me, I may need another cmdr to fly out and test it, meanwhile I will just continue on with what I have and mark that as a problem system.

Checking my session log in game it doesn't show an anomalous jump to Trienee region so it looks like an issue only with EDDiscovery, but it will indeed require another cmdr to visit and scan, howver if you could kindly wait until I have turned in the data since it was all first discovery that would be much appreciated.

I have a few weird legacy jumps from when EDSM didn't know that (for example) 'e Carinae' is different from 'E Carinae', but never anything as weird as what you're seeing.

Have you tried checking that the GalMap doesn't have two entries for HD 106863?

Edit:
Hopefully it isn't that the EDSM database has looped around a MaxInt limit and all future discoveries will be duplicates! 😱
 
Hit a major anomaly, and I mean major, system HD 106863 refuses to update in EDSM although I have scanned it, when I click on the button in EDDiscovery tp open EDSM with the system HD 106863 it jumps me instead to system Trienee OD-M c10-0, over 22,000ly away and there's also an entry in my journal indicating a jump to that system! A search in EDSM also indicates no records for system HD 106863, very strange, I will try jumping on and rechecking but it appears I may not be able to update that system, is it possible a duplicate index file in the galaxy database could be causing an issue? Have you come across this before?

When I check in the 3D map it clearly shows a 22kly jump to the core instead of to HD 106863.

Jumping to the next system didn't fix it, and now of course I have scanned them all I can't go back and try again because they have already been scanned by me, I may need another cmdr to fly out and test it, meanwhile I will just continue on with what I have and mark that as a problem system.

Checking my session log in game it doesn't show an anomalous jump to Trienee region so it looks like an issue only with EDDiscovery, but it will indeed require another cmdr to visit and scan, howver if you could kindly wait until I have turned in the data since it was all first discovery that would be much appreciated.

Sounds like it might be a duplicate id64 (or an incorrect id64 in the EDSM database).

One to poke @AnthorNet about methinks.
 
I detoured to check out HD 106863 - I'm seeing the same behaviour. Now back on track at HD 118674, which was previously unknown to EDSM and is now known, so it looks like there's just a problem with HD 106863.

(Or it could be Raxxla. On ne sait jamais!)

Also - nothing in the system was tagged at all, it will be interesting to see what happens when I sell up.
(eta - that went fine so no problems with the system in-game at least)
 
Last edited:
Back
Top Bottom