Very strange occurence...
- Thread starter B33 ENN
- Start date
As I'm suspected of pilot error, I have decided to consult a lawyer from the Pilot's Federation.
It could be worse, you could have fallen asleep at the end of a late evening session heading back to dock for the night only to awake to the sound of "Hull integrity compromised!" *KABOOM* - Nothing wakes you quicker than that - in fact I'm betting theres a market for Elite Dangerous Alarm Clocks with that very sound as the wakeup alarm
That's why I always fly with Admiral Multi-Ship insurance for those facepalm moments in space!
Indeed, learned that lesson myself after being hit by one too many asteroids under the influence.
Did you forget to put 50p in the meter OP? (one for all the teenagers out there
I maintain my innocence! I demand an inquest!
...And there's also this: I just started up again into my recovered new insurance replaced Cobra, and hit launch. My controls and throttle etc. seem to be working fine, however, same problem. No drive:
Exhibit A - Healthy powerplant at 0%:
Exhibit B - Silent Running not active:
Exhibit C - No thrust, bricked ship:
What am I doing wrong, any ideas? :S
Since I exited the game with a couple of minutes to go to update the thread, I've probably got a fine and been blown up again by the station for not leaving!
...Actually, why am I laughing, that's not funny. Anyway, I'm going to go back and see if I can use that reboot idea or something.
Last edited:
Your first screenshot shows a lot of modules deactivated, maybe the thrusters are off as well?
To the original issue: My first guess would have been lack of fuel as well, or a faulty macro / HOTAS command.
...UPDATED...
Okay, restarted, it spawned me outside the station and I was able to bring all my modules back online one by one. I may have been reading the 0% thing wrong on the panel. I guess that just means the reactor doesn't draw power itself. Doh!
That part is probably the game defaulting the settings to how they were before I blew up, i.e. all modules turned off.However, this time it has let me reactivate my modules, where in the main incident I was unable to do that, they just changed colour to red when I tried to activate them so there was definitely no power causing my untimely demise.
I shall play on, and hope it doesn't happen again... or if it does, I'll take pics for closer analysis. I should say thanks for all the input and suggestions so far from everyone. Much appreciated.
i found the X52/55 issue is tied to the programming software that it comes with, when it was installed it would cause some buttons not to work and flicker rapidly when others were pressed. This was despite allowing the USB3 port to provide as much power as it could handle. When i did a clean install of my system and forgot to install it again and only set the bindings using the in game menu's it works fine. it does however mean that i cannot use any macro's but thats fine for me as i like doing things manually adds to the immersion for me personally.
I'm back in the thick of battle! There are a few hours left in the CG, and I hope to make a contribution this time! Once moar unto the breach, dear friends...!
So basically, just attach the X52, but don't install the software? Using a different stick right now, but I'll bear that in mind when I hook my X52 up again.
So basically, just attach the X52, but don't install the software? Using a different stick right now, but I'll bear that in mind when I hook my X52 up again.
Maybe you are now part in the global ED story arch about mysterious energy malfunctions as reported now repeatedly throughout the bubble in various stations ... ?
While inconvenient to you I would welcome such a type of encompassing gameplay
AHA he is one of those station Zombies you read about on Galnet. The ship goes Zombie first.. then the Commanders! Much like the Zombie faction in EVE online.. Sansha? Forget the name its been many years.
I'm back in the thick of battle! There are a few hours left in the CG, and I hope to make a contribution this time! Once moar unto the breach, dear friends...!
So basically, just attach the X52, but don't install the software? Using a different stick right now, but I'll bear that in mind when I hook my X52 up again.
I have had similar problems with my X55 but it hasn't turned out to be the Madcatz software. It has turned out to be the fact I had a Logitech game pad connected. I have stress tested it and every time I have it connected at random times it starts playing tunes with my X55's all on its own, regardless whether I have the Saitek(Madcatz) software installed or not.
I also tried my Razor gamepad and the same problem arose when it was plugged in. Yet no problems with an MS gamepad (the one that looks like PS4 ones).
Either its Saitek being susceptible to the Logitech and Razor or those two interfering with the Saitek operation seems the only logical explanations.
Last edited:
I am no zombie! I hate zombies!
Wouldn't surprise me.
I should make sure my next ship has embedded Linux.They responded with a kind gesture of reimbursing my lost bounties.
No specifics on the issue, so I'm going with the suggestion by you guys that I ran out of fuel, but perhaps the indicator malfunctioned.In any case, I have been exonerated of pilot error by the official Frontier investigators, so my record remains untarnished and this inquest is now closed!
A big thanks to the Frontier Support guys for a fast response, expecially considering how this must be a busy time for them.
I've got pretty good at understanding how those work and how to set them. Usually, in a combat rig where I'm on the line for power with hardpoints deployed, I have least essential things like the cargo hatch and FSD go out first so I can operate the ship fine during fights. Always have that stuff ranked and prioritised from 1-5 before I leave the station after any loadout changes.
Combat loadout I don't have cargo space so never use it. I always turn it off or have it set at priority 5 to go out manually. Right now I don't even have a key bound for it.
I do recall hearing a fuel low warning earlier, but the gauge appeared to read there was a good deal available, so I took it as a default warning for low percentage. Not a mistake I aim to make again no matter what the gauge says!
The reservoir pulls 1 ton from the main tank each time it needs to be refilled. Is it possible the reservoir won't be refilled if there is greater than 0t but less than 1t left in the main tank? (basically only allowing for a very, very short Hyperjump). Basically causing a situation where you don't actually hear a "Fuel Tank Empty" warning, but you are in fact out of fuel as far as your power plant is concerned? (as the power plant draws directly from the reservoir).
Assuming your memory of the event is correct and you weren't ACTUALLY 100% out of fuel, I propose this is what happened. When you attempted to power all your modules on/off, you actually switched them all off as they were on but unpowered. This setting was saved when you reloaded. Since your thrusters were powered off, you got your second instance of brick-ship. You powered them back on, and now you're good to go.
Mystery solved??? (I'm working on a lot of assumptions here)
Assuming your memory of the event is correct and you weren't ACTUALLY 100% out of fuel, I propose this is what happened. When you attempted to power all your modules on/off, you actually switched them all off as they were on but unpowered. This setting was saved when you reloaded. Since your thrusters were powered off, you got your second instance of brick-ship. You powered them back on, and now you're good to go.
Mystery solved??? (I'm working on a lot of assumptions here
)
Last edited:
...Mystery solved??? (I'm working on a lot of assumptions here
That all sounds good to me, as long as pilot error wasn't one of your assumptions.