Well, that's your one mulligan for the game Mengy.
From here on, be very careful
From here on, be very careful
Need a good laugh? Watch my DBX lose power and explode on the surface right in front of my SRV!
- Thread starter Mengy
- Start date
Well now that it is confirmed to be pilot error, should the hand of FDev smote thee back to the bubble?
j/k, of course and glad it worked out! Probably chalk it up to good karma for saving that guy that time...
j/k, of course and glad it worked out! Probably chalk it up to good karma for saving that guy that time...
This is no offence, and dont take this to seriously. But why fdev rebuild your ship at this starsystem?
It was clearly a pilot error with the energyconfiguration and not a bug. You should see the rebuyscreen.
So if i crash next time outside the bubble i can contact fdev and they rebuild my ship and i can go on on my tour and dont loose any scandata?
good to know.
It was clearly a pilot error with the energyconfiguration and not a bug. You should see the rebuyscreen.
So if i crash next time outside the bubble i can contact fdev and they rebuild my ship and i can go on on my tour and dont loose any scandata?
good to know.
Out of interest, what range do you get on your DBX? While mine is currently configured for Bubble hopping, it still gets 50Ly jump range with shields and weapons - and can run with everything switched on. On previous occasions when I have gone exploring, I pretty much just swap the cargo bay for an AFMU and head out. Have you been able to get significantly more range by reducing module performance (I assume that's what you've done and is why you haven't enough power)?
Probably. Support are quite friendly and actually want people to enjoy the game. Though I wouldn't like to bet on the chances of them restoring a ship twice due to pilot error...
Probably. Support are quite friendly and actually want people to enjoy the game. Though I wouldn't like to bet on the chances of them restoring a ship twice due to pilot error...
Yes you can, but only once I believe. Whether you take the hit on the chin or carry on is up to you I suppose
![[DOOK] Droogie](https://forums-cdn.zaonce.net/data/avatars/m/124/124078.jpg?1553527149){kind=avatar}
Did you have to make a trip to the ATM machine to get money to pay for it, interrupting your reading of DC Comics?
Actually, in his situation it was a combination of both pilot error and a bug.
The bug is that the ship can take off but then not have enough power to maintain thrust. It shouldn't even be able to take off at all to begin with.
That's a valid point. Has a bug been raised?
It's not so much a bug as it is just the autopilot not being smart enough to manage underpowered ships with badly set up power priorities. Frontier support mentioned that it's a problem with the autopilot, it will turn systems on and off when it needs to but not always in ways that are "correct". The autopilot managed the systems to get the ship off the ground, but once airborne it went to re-manage the systems to get the FSD online and subsequently killed the thrusters in doing so. The end result was my DBX lifting off and then losing all power moments later. If I had set my AFMU priority properly it wouldn't have happened, but yeah the autopilot did in effect crash my ship, lol.
Hmmmm... I agree with Han Zulu. If the autopilot can take off, what does it then suddenly do that causes the thrusters to stop working? It shouldn't need to change power settings at all - it just needs to retract landing gear and head off. If power settings are such that thrusters don't have power - then the ship shouldn't be able to take off.
It had enough power to take off, but it wasn't enough to enable the FSD. When you dismiss your ship it uses the FSD to get into the orbit. So the autopilot decided to disable the thrusters... It's a real HAL move.
Hey ... I resent that
I'm not convinced that this is what happened.
It's what Frontier Support told Mengy
I would gladly blame T.j. but this really is a HAL move... Know what? Forget about, let's blame T.j anyway.
It's what Frontier Support told Mengy
I'm still not convinced.
Support have told me all sorts of rubbish when I've contacted them previously.EDIT: FSD and thrusters are both enabled at take-off. It isn't that FSD takes more power when you try to frameshift - either it has power or it doesn't. The screenshots Mengy has posted show a ship with no power (due to limit exceeded). It shouldn't have been able to take off.
Last edited:
I'm still not convinced.
EDIT: FSD and thrusters are both enabled at take-off. It isn't that FSD takes more power when you try to frameshift - either it has power or it doesn't. The screenshots Mengy has posted show a ship with no power (due to limit exceeded). It shouldn't have been able to take off.
It had enough power for the FSD after Mengy disabled the AMFU. Look at the upper screenshot. The autopilot didn't 'think' about disabling the AMFU and disabled the Thrusters instead.
It doesn't matter if the ship didn't have enough power for take off when the autopilot was in charge because it can simply disable random modules. Let's say it first disabled Life Support and after take off it disabled Thrusters because it still wasn't enough for the FSD.
Last edited:
There is no way to know exactly what happened, but I think this might be how the scenario played out:
I landed, activated the AFMU and repaired the FSD which requires turning it off first. Thrusters were turned off as they always do when landing so there was plenty of power. I deployed my SRV and dismissed my ship, this is where the autopilot turned the thrusters back on. Note that the SRV bay is still on, as is the AFMU which is set to priority 1 by accident, but because the FSD is still powered down there is enough power. However, right after taking off the autopilot went to turn on the FSD drive to prepare to warp into orbit. Doing so at this point, with the power priorities set as they were, would have resulted in the unpowered mess I witnessed when I first logged back in after support fixed me up, which is this:
Thus, a dead ship going limp just meters above the ground.
Like I said I can't know for certain, but all of the evidence seems to point to precisely this. All due to a combination of my incorrect power setup and the autopilot being crappy at managing flight system power in less than ideal situations. Very easily avoidable with some due diligence and careful piloting, both of which I slacked in here and paid the price. Support saved my bacon this time, but I think I learned (re-learned?) a lesson nonetheless.
I landed, activated the AFMU and repaired the FSD which requires turning it off first. Thrusters were turned off as they always do when landing so there was plenty of power. I deployed my SRV and dismissed my ship, this is where the autopilot turned the thrusters back on. Note that the SRV bay is still on, as is the AFMU which is set to priority 1 by accident, but because the FSD is still powered down there is enough power. However, right after taking off the autopilot went to turn on the FSD drive to prepare to warp into orbit. Doing so at this point, with the power priorities set as they were, would have resulted in the unpowered mess I witnessed when I first logged back in after support fixed me up, which is this:
Thus, a dead ship going limp just meters above the ground.
Like I said I can't know for certain, but all of the evidence seems to point to precisely this. All due to a combination of my incorrect power setup and the autopilot being crappy at managing flight system power in less than ideal situations. Very easily avoidable with some due diligence and careful piloting, both of which I slacked in here and paid the price. Support saved my bacon this time, but I think I learned (re-learned?) a lesson nonetheless.
There is no way to know exactly what happened, but I think this might be how the scenario played out:
I landed, activated the AFMU and repaired the FSD which requires turning it off first. Thrusters were turned off as they always do when landing so there was plenty of power. I deployed my SRV and dismissed my ship, this is where the autopilot turned the thrusters back on. Note that the SRV bay is still on, as is the AFMU which is set to priority 1 by accident, but because the FSD is still powered down there is enough power. However, right after taking off the autopilot went to turn on the FSD drive to prepare to warp into orbit. Doing so at this point, with the power priorities set as they were, would have resulted in the unpowered mess I witnessed when I first logged back in after support fixed me up, which is this:
Thus, a dead ship going limp just meters above the ground.
Like I said I can't know for certain, but all of the evidence seems to point to precisely this. All due to a combination of my incorrect power setup and the autopilot being crappy at managing flight system power in less than ideal situations. Very easily avoidable with some due diligence and careful piloting, both of which I slacked in here and paid the price. Support saved my bacon this time, but I think I learned (re-learned?) a lesson nonetheless.
I think you are not to blame for it, who would've thought about this? I (and I expect everyone else) didn't even know that this is possible.