Without Oxygen the Engine Hamsters die.
i'm with you concerning the timer - without a pilot, the ship shouldn't need "life support". but than - we actually don't know a lot about the technical design. if you run out of oxygen, your are ejected, and your ship blows up. why does a ship blow up, if you run out oxygen? to me it looks, as if the ship self-destructs if it has ejected the pilot. some kind of safety procedure, maybe?
--- @kaybe said it all
Will the new M3 also be equipped with a fusion reactor?Safety procedure...yeah...that's a good one. I hear BMW is adding that to their next M3 - " and now as a safety feature if your vehicle runs out of gas you will be ejected and it will self-destruct" lol....
Safety procedure...yeah...that's a good one. I hear BMW is adding that to their next M3 - " and now as a safety feature if your vehicle runs out of gas you will be ejected and it will self-destruct" lol....
OP is absolutely correct. That timer is NOT a self destruct timer, presumably the only reason your ship blows up at the end is that FD haven't gotten around to making a choking animation for your pilot. The timer clearly tells you it is an O2 depletion timer, and there is functionally no reason for the ship to scuttle itself once it reaches zero. Exiting the ship should pause the timer, since there is no longer anyone aboard to consume oxygen.
You dont die, you use the escape pod. The destruction could indeed be a 'safety procedure'. But not one intended to keep the pilot safe, but to keep the ship from falling in enemy hands.
Its not a self-destruct timer. Its an oxygen countdown. When the oxygen is gone, the pilot is ejected and self-destruct engaged. With no pilot present, there is no oxygen being removed from the closed circuit, so the oxygen countdown is paused. Before 2.0 there was no difference between what you say and how it should be, and they went with the easier way to code it. With 2.0 there is a difference, and it should be fixed. Remember that the countdown start AFTER general life support fails, and that the oxygen countdown is from the personal remlok system. As said, hypothetically one should be able to get in an SRV, find materials for the AFMU and repair the life support. Its a rare but cool scenario. The way it is currently programmed that is impossible.
...or to minimize environmental impact. I believe our reactor can create a tiny cute supernova, once it run out of fusion material.![]()
If it runs out of fusion feed, it should just sputter out and die.
Makes sense, but why you'd shut everything off is what's getting me I guess, there's no point in doing that, and if you KNOW doing it will result in ship destruction, bug report it and STOP doing it, the other thing that's getting me. Fire burns, so I'll tell someone fire burns and keep putting my hand into the fire until....*shakes head*
Its a RP thing. As he said, when he stops in space he turns everything off except LS (the kind of thing you'd do if your character would go to sleep), and on a surface, there is no need for LS either so he turned that off as well. As that doesn't work as it should, he reported it as a bug, after which FD asked him to re-post it here. The OP isn't as silly as it may look at first glance.![]()
Ok, neither of those situations would have me, as the captain of the ship, turning off everything so I could sleep. I'd leave my sensors and thrusters and FSD all online in case something happens that means I need to haul ass suddenly. !
your ship may not have enough fuel to run those for 8 hours - just saying... i had the same habit out exploring, really irritating that if you log in the next day, your heat is normal and directly starts cooling down. a friend of mine doesn't quit the game for that, and fuelscoops before and after work
![]()
anyway, for me it it doesn't make sense for a ship exploding after ejecting its cmdr ... but i take it as a feature. maybe they are afraid of ships going wild.
If your ship can't run for 8 hours while you sleep, you shouldn't be sleeping in it would my first thought, guess that's just me though
As for the ships exploding when we eject, yeah, that's more of an instance thing, instances vanish the moment we, the players, leave them, so when we eject, instance is gone, which means anything in it is gone, like our ships. Ceasing to exist is actually what happens to the ship, there's no explosion, it just goes poof as the instance is closed down. Just imagine if it was persistent however, think of all the ships that would be sitting out there, hazards to navigation since most of them are ruined shells, all that data accumulating and clogging up the servers, bad bad juju that! Easy solution to an ugly problem really, but this particular issue, really should be classified as a bug I suppose, although I'm still failing to see why you'd shut down all systems on a lifeless planet without atmosphere, even a single seater without crew, that's just not good planning by any means. Exploration should be done in ships that have at least 8 hours of fuel, mine can go well over 30 hours with everything running, over double that if I shut off everything but life support, actually around quadruple that with nothing but life support running. 64 tons on my Asp Explorer and my current Anaconda has 64 tons of fuel as well. If I can't make at least 8 max distance jumps without needing to refuel, that's bad planning on my part, I know there's sections of the galaxy where that's not even enough jumps at max distance to hit scoopable stars, got to be real careful out there in the Black, definitely no way in hell I'd take a ship out that can't go 8 hours on it's fuel tank just sitting in space with systems running, much less without them running. And yes, I've done that, left my game running for days on end while I was exploring, because my ship will sit there for days without running out of fuel![]()
Sorry but the player, which happened to start this thread, mentions that whilst in the SRV in the same instance as his ship, the ship then self destructs. That wouldn't be an instance problem at all.
Sorry but the player, which happened to start this thread, mentions that whilst in the SRV in the same instance as his ship, the ship then self destructs. That wouldn't be an instance problem at all.
I... am not completely positive on that that's how fusion reactors work.
Ok, neither of those situations would have me, as the captain of the ship, turning off everything so I could sleep. I'd leave my sensors and thrusters and FSD all online in case something happens that means I need to haul ass suddenly. And Life Support would definitely NOT be something I'd turn off when on a planet or moon that has no atmosphere, matter of fact, I'd leave the same systems on that I'd leave on in space while getting some sack time, for the exact same reasons. I'm not overly fond of how the thrusters get shut off when we land now, I'd personally prefer an option to NOT have them shut off, for emergency situations and fast get take offs.
I also look at the other aspects of the ship, like the fact that my Anaconda is SUPPOSED to have another 40+ people on board it besides myself, minimum crew required for her after all, so I definitely wouldn't be turning off life support just because I'm stepping out for a bit. Smaller ships that don't have crew requirements, you won't be killing others, but seriously, that's not something you should be turning off anyway, life support is MORE than just oxygen after all, it's also heating and cooling inside the ship. Night time on a planet without atmo, turn that off, inside of that ship is not going to be a good place to be when you return and it's been off for a while, daytime, same thing different end of the spectrum. Sticking your tongue to a pole when it's really cold is NOTHING compared to what would happen inside that ship when it's been sitting for a bit without life support on...just saying.
*edit*
That said, one thing, DAMNED good bug finding by the OP, doing something that wouldn't normally be done to find things like this, should apply for a QA position somewhere, need more people like that doing it!