Is there any way to safe guard against this?
Quit the game.
So just to be clear, it's possible to have your computer "go to sleep" but still be burning fuel, yeah?
If the computer sleeps, the client will disconnect.
Is there any way to safe guard against this?
So just to be clear, it's possible to have your computer "go to sleep" but still be burning fuel, yeah?
Yeah, sure. I more meant for ED itself. You know, like the way your laptop goes to sleep when you don't touch it for 30 mins or whatever you have it set to.As far as your ship is concerned there is no such thing as "Inactivity".
Oh, okay. This must have failed then.If the computer sleeps, the client will disconnect.
Oh, okay. This must have failed then.
My PC does have a tendency to not hibernate properly and I've never been able to work out why. It may have something to do with running a Plex server on this system as well or something.
My anaconda uses 2.75/h in supercruise. With 64t, that's less than a day.If you had a full tank of fuel, then your ship is unlikely to have blown up due to lack of fuel even after two days (especially an AspX). Supercruise doesn't use that much fuel. I suspect something else happened (maybe you'd stopped in the orbital path of a planet).
Yes. I think it's actually the X-56 that prevents Windows from hibernating but who knows, ED itself could well be preventing it too. I've tried to look into it before but was never able to get to the bottom of what was really going on.A Windows computer won't go to sleep if there is a game running. Certain other applications prevent this (media player does too).
Well, yes. And obviously I usually do but somehow, this time I must not have.You should always log out of/close down games directly - not sure how you could mistake this in E: D, really.
Oh, that sounds fascinating. I'll look into that.In the case it's still the same PC and ED installation, there's a chance that that death is still in the logfiles. You could either read them yourself (they're plain XML, so somewhat readable), or install one of the applications that read them and present them in a friendlier manner - I use EDDiscovery.
To be perfectly clear:Oh, okay. This must have failed then.
My PC does have a tendency to not hibernate properly and I've never been able to work out why. It may have something to do with running a Plex server on this system as well or something.
Okay, so I downloaded and installed ED Discovery and I have to say it is a fascinating tool, though I can't help but feel i have a lot to learnOh, that sounds fascinating. I'll look into that.
Didn't realise it was even possible.
Thank you.
I think I had to retrace steps from Colonia once going via Sag A then back to the bubble. It wasted a few weeks of my time.Yeah, I guess it's mainly the explore data, and the fun of discovering the codex items, not to mention the achievement of venturing out and back again.
Of course I can attempt to do it again but it's just kind of galling to be blown back to Sag A through a failed logout.
I'm doing my best to make sense of this, but is this saying that I entered Supercruise at quarter past midnight, did an FSS Scan a minute later, then did nothing till I automatically exited Supercruise (presumably due to running out of fuel) at 5:40 pm and promptly died some 7 minutes later?
How do I get an estimate of the value of the scans I lost? I appreciate it's been lost but more for curiosity's sake than anything I'd like to know How much it was.
Thanks for confirming....In other words, as far as the logs can tell, you simply went AFK for two days.
I actually haven't resurrected as of yet.Unfortunately, since you're resurrected in a space station after death, I think the figure it returns will be "0".
I believe that tab lists constants that are used in the calculation. I haven't really been able to workout what they do exactly but I'm guessing you can tweak these values to give what you believe would be a more accurate estimate:I think it's that "Estimated Values" tab in EDD.
Dude, I'm trying to understand what happened and aren't wasting supports time.You made a mistake and now just deal with it instead of wasting support's time.
So I assume this means I had an estimated value of 15M credits in scans (not including first to find bonuses etc) at the time I blew.