Just now I almost ran out of fuel near Sagittarius-Carina mission camp 16. The reason: Two game crashes, both in the middle of a jump, and both used up fuel but did not place me into the destination system. Question: Is this a known bug? If not I will report this to FD, but maybe more experienced explorers are already aware that this can happen?
In my case I was lucky to a) be in a region of space where star density was sufficiently high to let me eco-jump to safety, and b) have enough fuel left to perform these eco-jumps. If circumstances had not been this fortuitous, though, it would have been time for the Fuel Rats...
Event log (partially taken from the ED Discovery journal):
Full Disclosure: Two days ago I re-installed ED onto a secondary SSD drive and updated my Windows installation and graphics drivers. Since that time I have had numerous game crashes, which is why after the second of the above crashes I was fed up and re-installed ED back onto my primary SSD drive. I mention this here so people get the full picture, but I don't think re-installing the game or updating Windows/graphics drivers should have any effect on the server-side game state, or how ED reacts to a crash. The crash, by the way, took the form of a Direct3D error message box that popped up in the middle of playing the game and which, after clicking the only available button "Abort", forcefully terminates the ED process. So maybe not a regular crash, because I didn't get the chance to submit a crash report to FDev?
In my case I was lucky to a) be in a region of space where star density was sufficiently high to let me eco-jump to safety, and b) have enough fuel left to perform these eco-jumps. If circumstances had not been this fortuitous, though, it would have been time for the Fuel Rats...
Event log (partially taken from the ED Discovery journal):
- I have a full tank of 32t after fuel scooping in Ploxuia DN-Q d6-7.
- Jump to Ploxuia AB-W e2-2. The jump requires 5.5t and leaves me with fuel level 26.510925.
- Attempt 1 to jump to Ploxuia IX-X a 55-0. This jump is not registered in ED Discovery.
- The game crashes.
- Logging in again. I am still at Ploxuia AB-W e2-2.
- Attempt 2 to jump to Ploxuia IX-X a 55-0. The jump requires 7.2t and leaves me with fuel level 11.783796. As can be seen, I have lost approximately 7.5t of fuel in the first failed jump attempt.
- The game crashes - again.
- Logging in again. I am still at Ploxuia AB-W e2-2.
- Attempt 3 to jump to Ploxuia IX-X a 55-0. This time the jump requires 7.0t (because I carry less fuel than in attempt 2) and leaves me with fuel level 4.750721.
- The jump succeeds. I now notice the critically low fuel level and eco-jump to safety to a nearby scoopable star.
Full Disclosure: Two days ago I re-installed ED onto a secondary SSD drive and updated my Windows installation and graphics drivers. Since that time I have had numerous game crashes, which is why after the second of the above crashes I was fed up and re-installed ED back onto my primary SSD drive. I mention this here so people get the full picture, but I don't think re-installing the game or updating Windows/graphics drivers should have any effect on the server-side game state, or how ED reacts to a crash. The crash, by the way, took the form of a Direct3D error message box that popped up in the middle of playing the game and which, after clicking the only available button "Abort", forcefully terminates the ED process. So maybe not a regular crash, because I didn't get the chance to submit a crash report to FDev?