Glorious HIPs - 3306

Now that's nice, I'm less than 1,000ly from Sol, the servers are coming down in a couple of minutes, lets get this one last HIP system, so in I jump.

Previously unexplored, no tags anywhere, 4 gas giants, all Helium rich, a couple of small moons with biology, Brain Trees, one body has a 11m klm radius ring system, this is a nice one to log off in before the update, see you all after, have fun!
 
I have just reported a problem on the EDSM thread that when a Commander jumps into a system on board a fleet carrier, the system data does not get loaded into EDSM. I think this is because EDDiscovery does not recognise that the Cmdr was onboard when the carrier arrived, and so does not send the data to EDSM. Anyone else noticed this ?
 
I have just reported a problem on the EDSM thread that when a Commander jumps into a system on board a fleet carrier, the system data does not get loaded into EDSM. I think this is because EDDiscovery does not recognise that the Cmdr was onboard when the carrier arrived, and so does not send the data to EDSM. Anyone else noticed this ?
EDMC was updated for the new carrier events, so seems to pick up things correctly, is your EDDiscovery up to date?
 
Whilst visiting HD 124170 (HIP 69274) in sector 14 I unexpectedly came across HIP 67396, which is not in your spreadsheet (at least I couldn't find it).
I just had a quick look at the main HIP catalogue and it is there, but I couldn't work out whether it is in the correct position.
It is 219ly from HD 124170 and contains a class B primary, a class A secondary, but nothing else.

Just thought you'd like to know.

It's on the sheet - row 99017 - can't see it on edsm yet tho.

I'll do another sync tomorrow morning, currently suffering from a catastrophic bout of tidying. :)
 
EDMC was updated for the new carrier events, so seems to pick up things correctly, is your EDDiscovery up to date?

Yes, my EDdiscovery is up to date, but I also have EDMC and could try that instead.

Also, HIP 67396 is caught up in this problem as well, so has not yet appeared in EDSM ( and am very reluctant to go back there, it was quite difficult to reach)
 
I also have EDMC and could try that instead.
I'd give it a go - I took Romilayu to a HIP has week and was surprised edsm had me down as the only visitor (it wasn't possible to jump in & out in a ship).

The other way to get the system to appear is to relog in the system (I think you need to be in your ship). May only have been an EDMC workaround though 🤷‍♂️
 
Yes, my EDdiscovery is up to date, but I also have EDMC and could try that instead.

Also, HIP 67396 is caught up in this problem as well, so has not yet appeared in EDSM ( and am very reluctant to go back there, it was quite difficult to reach)

Are you trying to update using two different tools, EDSM recommends against that practice, it could be causing an issue.
 
I've also noticed that the system will be missing from the jump history on EDSM, if I arrive with the carrier. For an isolated system that can only be reached that way, it's a problem. The scans and discovery info update normally, however. To correct this, you can upload your journals into EDSM manually, and the missing jumps will get filled in.

Anyway, that's what I've observed with EDD lately. YMMV.
 
I've also noticed that the system will be missing from the jump history on EDSM, if I arrive with the carrier. For an isolated system that can only be reached that way, it's a problem. The scans and discovery info update normally, however. To correct this, you can upload your journals into EDSM manually, and the missing jumps will get filled in.

Anyway, that's what I've observed with EDD lately. YMMV.
A couple of carrier expeditions have noticed that too. The easy workarounds are to either jump out and back in to the system, or to relog in the system (since that also generates a Location journal event).
 
I've also noticed that the system will be missing from the jump history on EDSM, if I arrive with the carrier. For an isolated system that can only be reached that way, it's a problem. The scans and discovery info update normally, however. To correct this, you can upload your journals into EDSM manually, and the missing jumps will get filled in.

Anyway, that's what I've observed with EDD lately. YMMV.

I have uploaded the relevant journal into EDSM manually. Didn't seem to work.
The missing stars did not appear and are not in my EDSM history (but are in my EDD history).

My recent star visits are
HD 121147
HD 126007 *
HD 129921
HD 124896 *
HD 124170 *
HIP 67396 *
HD 126199
HIP 70420 *
HD 125919 *
HIP 70617

Those marked with a star are missing from EDSM.

I don't really want to go back to those systems to relog in the system, and jumping in and out with a carrier wouldnt make any difference I guess (no way to jump in and out with a ship 'cos they're too far apart).

Now thinking I might spoof my journals with a dummy log-in/out entry, but don't really want to do that.
 
Last edited:
So, here we are - I've tried a bit more mining (mostly laser mining, single tritium hotspot) post- patch 4 and while it's better than patch 3 levels it's still more time consuming than I'm happy with. The situation in the Bubble seems the same as patch 3 levels, i.e. there's no tritium available for a reasonable price anywhere so fully fueling a carrier is going to run to nearly a billion credits. Meh. Puts a serious damper on things - I don't even have a bee lion credits in ready money at the moment, so I'll not be chasing the more outre stars with my carrier.

On the plus side for me, nearly finished on slice 49, got another 50 or so stars to go.
 
Yeah, I'm not sure what to do with some of the more distant ones that require the carrier. I have one in slice 7 that's all the way out in the further half of Temple, and will need the carrier to reach.

I freed up a bunch of my bookmarks which will let me more efficiently pound through the remaining stars in slice 7, so hopefully I can speed this up a little. I should probably go ahead and reserve slice 8 and start at the near-bubble end, and combine the trip to get the outermost stars in both slices that I haven't gotten to yet.
 
I am seriously thinking of leaving my carrier at Sadr Logistics (a remote mining outpost in sector 14) .
I have about 35 systems left to explore. Most of them are far away from the galactic plane, and most likely unreachable even with a carrier.
I will continue to explore the remaining systems if I think they are reachable with an Anaconda.
 
I've also noticed that the system will be missing from the jump history on EDSM, if I arrive with the carrier. For an isolated system that can only be reached that way, it's a problem. The scans and discovery info update normally, however. To correct this, you can upload your journals into EDSM manually, and the missing jumps will get filled in.

Anyway, that's what I've observed with EDD lately. YMMV.

Well I'm back again after another session of blocked forum account, this time I have cancelled all forum email alerts so I hope it won't happen again.

Now this FC stuff is a bit worrying, there are some systems that may not be reachable in my slice without an FC so maybe I should wait for another FC update before charging in, of course of there are any nearby systems it may be possible to jump to the nearest system in jumponium reach so taking a long jumper with me may help.

Still that's probably a week away for me yet, I have finished bookmarking all my reachable systems, and it's surprising how many within 1kly of Sol that are only partially explored or even not at all.

Fly safe all o7
 
The good news is that you can get the EDSM jump history to fill in either by logging out and back in, while in those systems. Or you can manually upload the journal to EDSM later. The scans still fill in anyway, it's just your jump history looks incomplete if you don't do one of those workarounds.

What's amusing is that the in-game "visited stars" filter also doesn't do the right thing if you jumped in with the carrier. It'll show as red/unvisited.
 
Uh oh - there's a discrepancy between the row numbers on the sheet and the row numbers on the last upload, this isn't good. Only 20 lines or so. Could everyone hold off on making any edits until I track down where it is please?

Phew, found and fixed. Fortunately the break was near the end of the sequence so I believe it's only my data that was affected. Looks like something had broken the matching script and it dropped 20 lines out of the output file - I'll include a check on the output so it shouldn't happen again. I'll do some further checking just to be sure things are back as they should be.

...well that was downright weird, when I checked further. There's supposed to be 118801 lines, the downloaded file has 118801 lines, the script runs and finds 118801 lines, then it writes out and claims to have written 118801 lines... but the output .csv only contained 117780 lines, with a missing section towards the end - I couldn't find anything odd about the line but when I edited the note text for it and re-ran the script it went fine. Hidden characters or something, anyway, it's all good now.
 
Last edited:
Uh oh - there's a discrepancy between the row numbers on the sheet and the row numbers on the last upload, this isn't good. Only 20 lines or so. Could everyone hold off on making any edits until I track down where it is please?

Phew, found and fixed. Fortunately the break was near the end of the sequence so I believe it's only my data that was affected. Looks like something had broken the matching script and it dropped 20 lines out of the output file - I'll include a check on the output so it shouldn't happen again. I'll do some further checking just to be sure things are back as they should be.

...well that was downright weird, when I checked further. There's supposed to be 118801 lines, the downloaded file has 118801 lines, the script runs and finds 118801 lines, then it writes out and claims to have written 118801 lines... but the output .csv only contained 117780 lines, with a missing section towards the end - I couldn't find anything odd about the line but when I edited the note text for it and re-ran the script it went fine. Hidden characters or something, anyway, it's all good now.

So what you're saying is I shouldn't add "DROP TABLE stars" as a comment to all my EDSM systems?
 
Some conclusions after scanning all reachable systems in slice 32 (final numbers are similar to my previous report):
Out of all 500 systems
-78 are not in-game
-3 are glitched and point to multiple systems, indicating a possible data issue.
-1 system points to empty space
-68 are unreachable, with seemingly no other systems within 500ly
-32 are permit locked
-66 are already in game under different names (Atropos, Nevermore, lots of Canis Majoris-es )
-18 should be reachable by carriers

The remaining 243 have been reached (minus one late discovery that somehow escaped me). Out of these only 30-40 were actual first discoveries, the rest being already discovered in-game but not EDSM. Most of these were discovered by the very thorough CMDR Star Falcon. Commander, if you're reading this, I tip my helmet to you. 🍺

It feels weird that only about half of the 500 systems were reachable by regular ship, but I probably just picked an "unlucky" slice. Anyways, I will add all the details in Jackie's sheet soon and leave approximate coordinates for unreachables and carrier-reachable systems.

Now it's time to replenish jumponium and continue to slice 33, if it's available. Regarding the carrier reachables, I will leave them unchecked for now, since the recent tritium market changes have put a bit of cold water on my carrier plans.

o7 CMDRs
 
So what you're saying is I shouldn't add "DROP TABLE stars" as a comment to all my EDSM systems?

Ah yes, little Bobby Tables. :)

exploits_of_a_mom.png
 
Back
Top Bottom