Glorious HIPs - 3306

Took a bit longer of a hiatus than I intended. Should be able to continue plugging away at slice 37 now. Got a new monitor and things look pretty good.

Just confirmed the codex entry for lividum brain trees poking around in HIP 26771, so that was kind of neat. Would have taken some close-up shots but they were in the mountains, and I was worried the ship would have a hard time finding another landing zone. Guess I better bring the Sidewinder next time, eh.
 
Every now and then I come across something curious, odd. Last time it was when I tried to jump my carrier into a Blue Hypergiant and it told me there were no free slots, ok I thought, maybe with really large stars you can't jump carriers in, when I jumped in with a regular ship it was the only body in the system. Today on the way to HD 150778 I set my carrier jump to a star relatively midway between the that system and the one I was in, HD 144719.

The galmap tells me there are 3 stars in the system, it also tells me this is just a standard Class A star, but when I try to navigate using the FC interface it tells me there are no free slots. I managed to find a G class that appears to be close enough to it for a premium Jumponium jump so I can check it out, but it's curious, have any other explorers come across similar situations?

Ok succesfully jumped in...and that was interersting, it could also mean that some systems on the edge, while close enough for carrier jumps, might currently still be inacccesible, it was a good job I could find a star close enough for a Jumponium jump in.
 
Last edited:
Every now and then I come across something curious, odd. Last time it was when I tried to jump my carrier into a Blue Hypergiant and it told me there were no free slots, ok I thought, maybe with really large stars you can't jump carriers in, when I jumped in with a regular ship it was the only body in the system. Today on the way to HD 150778 I set my carrier jump to a star relatively midway between the that system and the one I was in, HD 144719.

The galmap tells me there are 3 stars in the system, it also tells me this is just a standard Class A star, but when I try to navigate using the FC interface it tells me there are no free slots. I managed to find a G class that appears to be close enough to it for a premium Jumponium jump so I can check it out, but it's curious, have any other explorers come across similar situations?

Ok succesfully jumped in...and that was interersting, it could also mean that some systems on the edge, while close enough for carrier jumps, might currently still be inacccesible, it was a good job I could find a star close enough for a Jumponium jump in.

Had two of these situations,actually. One was in slice 33, but still managed to jump using a maxxed jumpaconda on jumponium. The second was a bridge system in slice 43, on the way out. This one was too far for jumpacondas, so I had to make a long detour down into "populated" space and up again. Glad to see you made it.

My hypothesis about these no-free-slots sitautions is that the game can't find a stable spot in orbit to spawn the carrier. Back in june there were still some issues with carriers jumping into multiple-star systems and becoming runaway carriers. These were "fixed" by a no-free-slots mesage whenever they could potentially get into that situation. Don't recall the actual parameters that led to it though, just that it used to happen in multi-star systems, regardless of main star size. Odd that you got one for a single-body system.

Anyway, good to see you made it. Anything out of the ordinary in the system?
 
Had two of these situations,actually. One was in slice 33, but still managed to jump using a maxxed jumpaconda on jumponium. The second was a bridge system in slice 43, on the way out. This one was too far for jumpacondas, so I had to make a long detour down into "populated" space and up again. Glad to see you made it.

My hypothesis about these no-free-slots sitautions is that the game can't find a stable spot in orbit to spawn the carrier. Back in june there were still some issues with carriers jumping into multiple-star systems and becoming runaway carriers. These were "fixed" by a no-free-slots mesage whenever they could potentially get into that situation. Don't recall the actual parameters that led to it though, just that it used to happen in multi-star systems, regardless of main star size. Odd that you got one for a single-body system.

Anyway, good to see you made it. Anything out of the ordinary in the system?

Yes, I was keeping you in suspenders, it appears these systems have unusually large asteroid belts around the primary star, in this case extending from near the star to out over 1,000ls, without any planets in orbit around the primary this means all the available slots are within the area of the asteroid belt and you apparently can't park an FC in an asteroid belt! Once I had mapped the other bodies in the system, 2 stars and 3 planets, I was able to bring my FC in to orbit around one of the planets.
 
Row 574 in the spreadsheet is wrong, it's supposed to be for HD 324 (HIP 627), but it's got the data for HIP 625.
Yes, That part of the spreadsheet is outside the normal slice range, so I'll have to correct it manually.

Edit: Now corrected.
 
Last edited:
OK, finally finished the first pass of Slice 23. Anything not listed below is either already done or to be visited.
I didn't find any systems with custom names that were not already in EDSM, so these are all complete.

Ahhh.. another excel user. Please read Varonica's post #619 above.
Although it doesn't matter much here since I can now correct for the weird characters.
Also, I don't need the original row numbers either, everything is indexed on the HIP numbers.

The data has now been included in the spreadsheet, with the progress report below.
Well done for increasing your progress by 54% !
 
slice​
Commander​
Status​
complete%​
δ complete%​
matched​
δ match​
not_found​
δ not found​
unreachable​
δ unreachable​
other​
δ others​
1​
Pirin​
Mostly complete​
99.8​
0.00​
311​
0​
126​
0​
62​
0​
1​
0​
2​
Mooing​
In progress​
64.2​
0.00​
318​
0​
3​
0​
0​
179​
0​
3​
Varonica​
Complete​
100​
0.00​
358​
0​
107​
0​
35​
0​
0​
4​
Rampant​
In progress​
17.2​
0.00​
85​
0​
1​
0​
0​
414​
0​
5​
jjgoldberg​
In progress​
91.8​
0.00​
367​
0​
68​
0​
24​
0​
41​
0​
6​
jjgoldberg​
In progress​
95.2​
0.00​
374​
0​
64​
0​
38​
0​
24​
0​
7​
Orvidius​
Mostly complete​
99.6​
0.00​
393​
0​
69​
0​
36​
0​
2​
0​
8​
Orvidius​
Complete​
100​
0.00​
408​
0​
68​
0​
24​
0​
0​
9​
Jackie Silver​
In progress​
43.6​
0.40​
179​
2​
39​
0​
0​
282​
-2​
10​
13A / 24B​
In progress​
25​
0.00​
120​
0​
5​
0​
0​
375​
0​
11​
Jackie Silver​
Pending​
16.8​
0.20​
83​
1​
1​
0​
0​
416​
-1​
12​
Varonica​
Mostly complete​
93.8​
0.00​
419​
0​
50​
0​
0​
31​
0​
13​
Expugnax​
Mostly complete​
97.6​
0.00​
396​
0​
66​
0​
26​
0​
12​
0​
14​
Expugnax​
Mostly complete​
98.6​
0.20​
425​
1​
43​
0​
25​
0​
7​
-1​
15​
Heavy Johnson​
In progress​
19​
0.40​
94​
2​
1​
0​
0​
405​
-2​
16​
Gaesat​
In progress​
20.2​
0.60​
97​
3​
4​
0​
0​
399​
-3​
17​
Jackie Silver​
Partially complete.​
46​
0.20​
211​
1​
19​
0​
0​
270​
-1​
18​
Spaceman Si​
In progress​
27​
0.00​
130​
0​
5​
0​
0​
365​
0​
19​
rOmiLaYu​
Mostly complete​
47.8​
0.00​
195​
0​
44​
0​
0​
261​
0​
20​
rOmiLaYu​
Partially complete.​
22.8​
0.00​
75​
0​
37​
0​
2​
0​
386​
0​
21​
In progress​
37.2​
1.60​
178​
8​
8​
0​
0​
314​
-8​
22​
Mercury 13​
Provisional​
18.2​
0.60​
88​
3​
2​
0​
1​
0​
409​
-3​
23​
Irisa Nyira​
In progress​
83.2​
54.00​
239​
103​
130​
121​
47​
46​
84​
-270​
24​
Factabulous​
In progress​
70.8​
0.00​
224​
0​
130​
0​
0​
146​
0​
25​
Maelstrom5K​
In progress​
55.6​
1.20​
116​
6​
153​
0​
9​
0​
222​
-6​
26​
Maelstrom5K​
In progress​
37.8​
2.40​
91​
12​
94​
0​
4​
0​
311​
-12​
27​
Bren64zzz​
In progress​
54.2​
0.00​
133​
0​
107​
0​
31​
0​
229​
0​
28​
15.4​
0.00​
73​
0​
4​
0​
0​
423​
0​
29​
Rollo​
In progress​
20.8​
0.40​
104​
2​
0​
0​
396​
-2​
30​
16.8​
0.00​
84​
0​
0​
0​
416​
0​
31​
25.8​
0.00​
126​
0​
3​
0​
0​
371​
0​
32​
Getedoi​
Mostly complete​
93.6​
0.00​
339​
0​
80​
0​
49​
0​
32​
0​
33​
Getedoi​
Mostly complete​
93​
0.00​
398​
0​
67​
0​
0​
35​
0​
34​
27.2​
1.00​
136​
5​
0​
0​
364​
-5​
35​
Preludeonlife​
In progress​
27.8​
0.80​
139​
4​
0​
0​
361​
-4​
36​
37.4​
1.00​
186​
5​
1​
0​
0​
313​
-5​
37​
Farran​
Pending​
37.8​
1.60​
188​
8​
1​
0​
0​
311​
-8​
38​
MattG​
Mostly complete (*)​
99.8​
0.00​
428​
0​
44​
0​
27​
0​
1​
0​
39​
36.6​
0.40​
181​
2​
2​
0​
0​
317​
-2​
40​
In progress​
72​
0.20​
318​
1​
42​
0​
0​
140​
-1​
41​
Expugnax​
Mostly complete.​
99​
0.00​
401​
0​
71​
0​
23​
0​
5​
0​
42​
Varonica​
Partially complete.​
95.8​
0.00​
403​
0​
75​
0​
1​
0​
21​
0​
43​
Getedoi​
In Progress​
99.4​
0.00​
398​
0​
67​
0​
32​
0​
3​
0​
44​
Maolagin​
In progress​
51.8​
0.00​
229​
0​
25​
0​
5​
0​
241​
0​
45​
19​
0.20​
91​
1​
4​
0​
0​
405​
-1​
46​
Varonica​
In progress​
56.2​
4.20​
277​
21​
4​
0​
0​
219​
-21​
47​
Jackie Silver​
Mostly complete.​
96.2​
0.00​
403​
0​
68​
0​
10​
0​
19​
0​
48​
Jackie Silver​
Mostly complete.​
90.6​
0.00​
397​
0​
56​
0​
0​
47​
0​
49​
Jackie Silver​
Mostly complete.​
90.4​
0.00​
388​
0​
63​
0​
1​
0​
48​
0​
50​
Jackie Silver​
Mostly complete.​
89.8​
0.00​
377​
0​
72​
0​
0​
51​
0​
51​
Jackie Silver​
Mostly complete.​
76.4​
0.40​
334​
2​
48​
0​
0​
118​
-2​
52​
Expugnax​
In progress​
66​
6.80​
257​
34​
73​
0​
0​
170​
-34​
53​
Expugnax​
In progress​
63​
7.20​
232​
36​
83​
0​
0​
185​
-36​
54​
Taketa​
In progress​
44.6​
0.00​
220​
0​
3​
0​
0​
277​
0​
55​
Tuomasi​
Mostly complete.​
99.52​
0.00​
150​
0​
44​
0​
17​
0​
1​
0​
 
Ahhh.. another excel user. Please read Varonica's post #619 above.
Although it doesn't matter much here since I can now correct for the weird characters.
Also, I don't need the original row numbers either, everything is indexed on the HIP numbers.
OK, will do.
The data has now been included in the spreadsheet, with the progress report below.
Well done for increasing your progress by 54% !
Thanks; I was a bit worried that I had so many "not founds" in my slice, but looking at the progress report it's a similar number to nearby slices.

I've managed to reach a couple that I thought were unreachable, which is nice. On the other hand I was especially frustrated with HD 24095, where I couldn't find anything closer than 522ly. There's also a little group of four systems that are within carrier jump range of each other, but the closest other system is 860ly away. Still, there will probably be a 1000ly range carrier coming out in a year or so.
 
Last edited:
OK, will do.

Thanks; I was a bit worried that I had so many "not founds" in my slice, but looking at the progress report it's a similar number to nearby slices.

I've managed to reach a couple that I thought were unreachable, which is nice. On the other hand I was expecially frustrated with HD 24095, where I couldn't find anything closer than 522ly. There's also a little group of four systems that are within carrier jump range of each other, but the closest other system id 860ly away. Still, there will probably be a 1000ly range carrier coming out in a year or so.

Not founds, I think my slice has a larger number than previous slices, but I expect that's because it's pointing closer to the center of the galaxy where a lot of dust clouds would get in the way of accurate observation and measurement. The closest I got to a target and couldn't reach was 511ly, and I also had a path of about 8 stars all looking to be within carrier jump range except for the first, frustrating indeed. Maybe when this is all finished we can have a list of out of carrier range targets that look good so we can swap around and check each others slices, you may spot a route I missed and vice versa.

Not sure about the 1000ly carrier, I am sure FDEV don't want to push it much further, first we had the 250ly megaships, then the 500ly carrier, I think the most they will do is play with the refueling to pander to the dissatisfied.
 
No names or unreachable stars reported this week, but 233 new names matched.
There are approximately 118,000 stars in the overall HIP catalogue, over 90% of them have now been accounted for.

This new forum sw does not easily allow you to create a large table. You are not limited to a 10x10 table, making one 56x12 is possible, but not easy.
So I have attached the data as a spreadsheet file. Of course, the only type of spreadsheet you're allowed to attach is a .xls file which is an old fashioned Excel format.
To overcome this I have converted the data to a tab delimited text file. Sorry about some of the number formats, couldn't easily see how to change them.
 

Attachments

  • progress.txt
    3.3 KB · Views: 115
Apropos my previous post, I think if anyone wants to report their findings of named stars, unreachable stars etc, it would now be easier to attach them as text files, rather than insert tables.
My preferred format is tab delimited as above, mostly because libreOffice can read them in fairly easiliy,
Unfortunately you are not allowed to attach .tsv or .csv files , so it has to be .txt .
 
A short update from me: Didn't explore too much last week, due to powerplay module shopping and the FSD CG. Around halfway through both of the slices now. I've visited almost all "non HIP/HD-named" systems, so I'll propably just double check the few remaining next weekend and post them all together. I missed a lot of permit locked systems in Slice 25 on the first pass. Except for really few missing icy moons, literally everything (HIPs and in-between) was discovered in-game, so instead I did a lot of first mapping. Until yesterday night, when I finally hit the first undiscovered HIP, so I'm kinda excited now.
 
So an update. I have changed my approach to scanning a slice. I used to scan the normable reachable stars of the slice in one go and leave the fleet carrier and out of range stars for my trip back. I have found this adds quite a bit of unnecessary travel going up and down through the thickness of the galaxy. So this time I have decided on a different method and visited everything below the galaxy center plane, including FC and checking out of range systems, this seems to work much better, I am now about half way through the slice. The last system on the lower part of the slice, HIP 71313 was way out beyond the rest by around 3,000ly and appeared to be to low so I left my FC back at the last star and headed out in Phantom. It was the right decision, and interestingly HIP 71313 is so far the only system I haven't been able to reach, there may be more above the galactic center plane.

An interesting fact, HD 140283 is the oldest known star, close to 14b years and as old as the universe itself. It's in the ED galaxy as Lalande 28607 so if you feel like visiting some ancient history there's one right there! Unfortunately the age data doesn't match the actual age recorded but oh well it's there anyway!
 
I'll have to go through my records to see if there are any systems I've visited that have custom names - I've already noticed one. HIP 7 is in-game as Deeli's Point for some reason. It's not like there's anyone living there or anything particularly interesting in the system.

There were lots. Matches.txt contains them.

Errors.txt contains a few systems where my records disagreed with the spreadsheet. I've checked in-game but you might want to double check. I did find about the same number that turned out to be mistakes in my records :)
 

Attachments

  • errors.txt
    665 bytes · Views: 190
  • matches.txt
    6.8 KB · Views: 165
There were lots. Matches.txt contains them.

Errors.txt contains a few systems where my records disagreed with the spreadsheet. I've checked in-game but you might want to double check. I did find about the same number that turned out to be mistakes in my records :)

Thanks for the data. I always find a number of issues when I do the merge, I try and fix them but a few always get through.

HIP 17750, Gliese 153 B, has been one of the problem stars. As the notes say, it is star B in the Atanua system. But the "name in elite" has to stay as Atanua for the match with the EDSM data to work. The EDSM dump file only has the main star names, not any subsidiary ones. That way the coordinates get picked up.
 
Last edited:
HIP 17750, Gliese 153 B, has been one of the problem stars. As the notes say, it is star B in the Atanua system. But the "name in elite" has to stay as Atanua for the match with the EDSM data to work. The EDSM dump file only has the main star names, not any subsidiary ones. That way the coordinates get picked up.
Ah, that makes sense. I guess it's not the only one in the spreadsheet like that, it's just the only one I've visited.
 
I found an oddity. 240 G. Aquarii at [1404/-1404/153] has the in-game catalogue IDs of HIPP: 221308 and HD: 116060. Looks like the values have been transposed at some point.

What's even more fun is that thee system HR 8928 has the catalogue numbers in the correct order!
 
Weird stuff going on with EDSM... note the dates... Edit: forget it, I can't count. It is possible someone visited the system later the same day.
2021-02-28 23_18_44-HIP 43198 _ EDSM - Elite Dangerous Star Map.png


And what does that bar mean, btw? Mapped planets? Before I did the EDDN sync, it showed 1 scanned (the blueish), rest black. After the sync it show 2 out of 11.
2021-02-28 23_19_02-HIP 43198 _ Celestial bodies _ EDSM - Elite Dangerous Star Map.png
 
Last edited:
So an update. I have changed my approach to scanning a slice. I used to scan the normable reachable stars of the slice in one go and leave the fleet carrier and out of range stars for my trip back. I have found this adds quite a bit of unnecessary travel going up and down through the thickness of the galaxy. So this time I have decided on a different method and visited everything below the galaxy center plane, including FC and checking out of range systems, this seems to work much better,
As I've mentioned previously, I use a completely different method. I get fairly good estimates of all the stars in the slice, and then feed them into Mathematica to come up with an optimum 3d route. This seems to work quite well. What is interesting is that I have noted that the route often consistently goes either above or below the plane, and rarely crosses the plane. This would suggest that there are fewer HIPs very close to the plane, which would make sense.

It also suggests that staying either above or below the plane is a good strategy.
 
Back
Top Bottom