Because it is so clear, it takes a longer time to realise it. If you immediately know the candlelight is fire, then the meal was cooked a long time ago.
It’s the end of the road for me. I didn’t make it any further than Pru Aescs NC-M d7-192. It’s still my wish to visit Beagle Point, but not now.
The expedition made it to Beagle Point without me, and most other commanders are already back home. There’s no point in me trying to continue this quest at the present time. I can get a proper shipyard to fix this ship back at Flade Enterprise.
Breaking out of game character, the reason for my lack of play-time on Elite has been a combination of real-life factors, and the change of my primary operating system from Windows to Linux – it’s got to the point where Elite: Dangerous is the only thing I used Windows for.
With the release of Valve’s Proton 4.2, I’ve now successfully managed to get E:D running on Linux, so jumping in-game for a bit of play-time doesn’t feel so disruptive to everything else. In addition, EDDiscovery also (sort-of) works under Mono, though you can’t edit your CMDR settings in EDDiscovery. I found that I could open the EDDUser databse file with DataGrip and set the settings directly in the file though.
If you’re interested, this is the document I followed to get E:D working on Proton.
Curse this blasted new ship! It was only yesterday that everything seemed to be working fine. Today, it’s decided to stop logging journal data. Not only that, but the heatsink trigger appears to be far too sensitive. Breathe on it and it’ll drop a heatsink. :(
I made it as far as Waypoint 1, which I think was 71 jumps (by a quick spot of maths), but I honestly don’t know due to the loss of tracking data. I’m going with 71 jumps.
On the up side, there’s an asteroid base at this waypoint, so I was able to drop some cartographic data off in case of incidents later on.
| Item | DR | CR | Balance |
|---|---|---|---|
| Replacement heatsink | -25 CR | -25 CR | |
| Ship integrity repair | -5,489 CR | -5514 CR | |
| Cartographical data | 3,878,472 CR | 3872,958 CR | |
| Cartographical data | 3,823,645 CR | 7,696,603 CR | |
| First discovery bonus | 98,000 CR | 7,794,603 CR | |
| Cartographical data | 1,956,710 CR | 9,751,313 CR | |
| First discovery bonus | 37,000 CR | 9,788,313 CR | |
| Total | 9,788,313 CR |
I went on to do another 89 jumps after that, using 416.6t fuel, but suffered even more issues with tracking. I’m going to dig into the ship’s computer and see if I can figure out what is going on…
Nothing much to report as I head out of the bubble.
I’m already playing catchup to the expedition – unfortunately the replacement ship I bought from Bakewell Point in Pallaeni (replacing the one destroyed by CMDR Rivertide) has been plagued with technical issues that I’ve had to spend far too long rectifying. I’m happy to report that I’ve managed to make a good number of jumps today, so hopefully I can play catchup and continue onwards to the rest of the expedition without further incident.
On Saturday, I was made aware of a video by Real Engineering – a YouTube channel I already followed – which goes into the details of how a company is running an autonomous drone-based delivery service for critical medical supplies including blood in remote regions of Rwanda.
I’ve been aware of companies like Amazon and Domino’s wanting to get into the drone delivery service using quad-copter type drones, but this stunned me as an absolutely incredible use of technology for humanitarian purposes.
We departed!
I headed from Flade Enterprise out to the fleet departure point at Pallaeni to await the first mass jump to HR 5413 as the fleet departed
Unfortunately, as I was awaiting the departure, I was brutally murdered by CMDR Rivertide, a Dangerous-ranked commander in a Mamba. Thankfully, I’d docked at Bakewell Point in the Pallaeni system, so I didn’t have far to travel back to the departure point.
Due to issues with server lag, I didn’t continue the journey beyond the initial jump.
Yesterday I thought I had a bad day with white dwarves.
Today, I jumped with my pre-charged FSD to another neutron star, charged and jumped again, and tried to charge a third time on a third neutron star.
I got too close to the neutron star while inside the jet cone, and was kicked out of supercruise while still inside the jet cone.
Because you get buffeted around inside the jet cone, and remaining in the jet cone for too long causes a lot of damage, my ship quickly lost the ability to fly.
I couldn’t jump to supercruise because I couldn’t reorient to the escape vector – assuming my FSD didn’t glitch out before that point. My AFMU couldn’t keep both my thrusters and FSD healthy enough not to glitch out.
Eventually, my canopy shattered, and at that point it was clearly game over. Being 7.7kly away from home, there’s no way I had any hope of getting to a station for repairs in the 25 minutes of life support I had available.
Thankfully, someone has kindly grabbed my escape pod and escorted me back to Flade Enterprise in LHS 28, where I’ve managed to convince the insurance people to give me a new ship.
Whether or not I’m going to actually get to see these bubblegum worlds now before the update is another matter, but alas I shall try again. Probably spending little to no time gathering exploration data while en-route – I can do that on the way back.