Glorious HIPs - 3306
- Thread starter Jackie Silver
- Start date
-
- Tags
- exploration
All it really needs is the ED names column filling in for your slice of stars (most of that will happen automatically as they go in to EDSM, except where the names are from odd catalogues or the stars have been renamed in Elite, but I've been filling all mine is as I find them anyway.)
I got in and back out. HIP 100596 was a sight to behold. K class star 47 times bigger than our sun! Unfortunately for me, the system has been previously visited but I FSS'ed the rest of the system and EDD should have pushed the data to EDSM.
ETA: Just checked, it must be real time as the data is already there: https://www.edsm.net/en/system/id/54386746/name/HD+194078
I'll do a sync tomorrow once tonight's nightly dump is done. I've finished fueling up Spencer Rifle (which took almost exactly the same length of time as watching Hot Fuzz) and now I'm heading up to the hard-to-reach stars.
Hot Fuzz is a great movie!
I have hit a few stars that are in EDSM already but the names have been changed. The stars that are already HIP and HD and other known names will of course update automatically as you say, but as I get closer to the bubble I am likely to hit a lot of them, should I wait until I have finished and post them, I don't have a google account so I can't do anything with the spreadsheet online to update it myself.
Yes that would be handy.
I'm updating the sheet in batches at the end of each session. I don't play for long, so manage 3 or 4 systems each time, updating the ED name and adding a note for those I can't reach with my jump range, those I can't plot and those that aren't in game.
It will keep me out of trouble for a while
It will keep me out of trouble for a while
There's also HD 90399, I am certain it is reachable with an FC but out of range of my Phantom.
I've been recording those as ??? for the name and "redirects to empty space" in the notes field.
My thinking is that once we've dealt with the stars which are definitely there, we can come back and look again at all the ones that are outright missing, empty and weird. Some of them are components of other systems, some belong to stars that have a "named" equivalent nearby, and so on.
---
I've visited all the HIPs above the plane that I could get to with my carrier - I'm dropping below the plane now to get those I can reach there, then I'll move on to a new slice
My thinking is that once we've dealt with the stars which are definitely there, we can come back and look again at all the ones that are outright missing, empty and weird. Some of them are components of other systems, some belong to stars that have a "named" equivalent nearby, and so on.
---
I've visited all the HIPs above the plane that I could get to with my carrier - I'm dropping below the plane now to get those I can reach there, then I'll move on to a new slice
I’m guessing these systems are either above +9015 or below -10,985. If you watch carefully the map shows them for a split second then snaps down / up to those Y values. No idea why. I’m recording them in my manual search sheet as ‘unselectable’.
I don't think that's the case for a lot of them. I have one that's 9000+ which does as you suggest, but I have 2 where the map takes you straight to an empty space without the 'snap'.
I suspect we'll finish up having to track them by trig, spectral class etc.
Alternatively we could mark them as 'here be star eating dragons'
There's a good chance the star in question is higher than the galaxy map can show, I have a couple of those, they can't display so the POV drops to the lowest level it can display with the star either far above or below. It was mentioned earlier in the thread about the limits to display above and below the galaxy map, if you end up in empty space far above or below the galaxy that's the problem here, what HIP number is it? I will test it just in case it's an issue at your end.
Here's a couple of examples to show the difference:
HIP 88559 - Goes up to the star then drops to +9015
HIP 95951 - Goes direct to an empty space at -350:29:180. If you select one of the stars next to that location, then search for HIP 95951 again, the focus barely moves. 75415 & 102532 do the same. I'm sticking with my star-eating-dragons theory for these ones
Here's a couple of examples to show the difference:
HIP 88559 - Goes up to the star then drops to +9015
HIP 95951 - Goes direct to an empty space at -350:29:180. If you select one of the stars next to that location, then search for HIP 95951 again, the focus barely moves. 75415 & 102532 do the same. I'm sticking with my star-eating-dragons theory for these ones
What I found out recently when preparing my slice 55 route:
HIP 78738: resolves normally to "Kalb" (name in ED) and is star A of the system.
HIP 78739: galmap resolves to an invisible/empty space nearby but by chance when exploring "Kalb" I see that it is star B of that system.
So in these cases, stars unable to resolve might be secondary stars found in already discovered or not yet discovered systems.
And another observation:
HIP 86963 = LTT 7072 in ED galmay but LT 7073 in the sysmap.
I think a lot of them are associated with nearby "named" stars - as if the hips were added first, then a second pass added named stars and a third removed the duplicates.
It'll be interesting to have a look through the "empties" and see what is nearby.
Same here. No shift, no quick movements, just a slow move to the left.HIP 95951 - Goes direct to an empty space at -350:29:180. If you select one of the stars next to that location, then search for HIP 95951 again, the focus barely moves. 75415 & 102532 do the same. I'm sticking with my star-eating-dragons theory for these ones