-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vents lock out too easily #33390
Comments
Its partially caused by very high lockout pressure(like 20% loss already can lock most vents) but also by maps lack of airlocks to protect the atmos, little bit of spacing and half of station atmos are gone at times, bonus points if there is no power for some reason and the smart spessmen do not lock maints as usual. If nearby sets of airlocks were connected to eachother and set to close they could greatly reduce atmos drain while still not slowing crew too much as they go on their daily lives and spacing station via maints. Then we have firelocks that often are poorly placed, on door or literally adjacent to door so you can't create small pocket to open from without spacing bigger parts of station. 1-3 tiles of space between firelock and airlock/another firelock set would save stations a lot of atmos and lockouts. |
Really vent lockouts should be tied to firelocks and checking if the room is airtight before unblocking |
As AI, I could not agree more. Perhaps it should even bolt while in fill mode as safety measure and require hacking(safety wire wyci)/emag to bypass it. |
After discovering how this system works myself, I fully agree it is really, REALLY bad for station operation unless you have an insanely cracked Atmospherics Technican running around manually repressurizing everything The vent lockout should definitely be set MUCH lower so only rooms which are either obviously spaced or next to a breach don't get refilled. It's not normal that a few people quickly forcing a firelock causes the entire hallway to become permanently depressurized It's also a bit weird that the only way to fix this is to intentionally set the air alarm to Fill or screwdriver the vent repeatedly. You really have to be VERY aware to see the yellow vent or know what it means, and nowhere are you told that screwdrivering the vent allows you to refill the room if you can't access the alarm. It doesn't even tell you what you did when do end up screwdrivering it! |
So, what exactly screwdriving does? Forces fill for X seconds? Till air alarm changes it again? |
I was literally just told this by a developer, and apparently it disables the lockout for like 10 seconds maximum. But it allows someone without air alarm access to manually refill their room |
Our atmos simulation is kinda broken at the moment. We do have instant spacing using a floodfill algorithm, but it is supposed to stop at firelocks and activate them in between atmos ticks. This does not happen at the moment, causing the whole station to be depressurized and the firelocks trigger only when it is already too late. On top of that a few bandaid changes had been made to make spacing slower, which however causes the lockouts not to trigger correctly. |
it's intentionally set high, without this the vent just never becomes space and keeps voiding air even if there's a breach nearby |
theres an ancient pr to make lockout smarter |
Okay PR #29504 explains why lockout occurs so easily - it's because the threshold is 80 kPa
Can you link it |
Please take a look at this draft I just whipped up: #35489 |
Description
A single syndiebomb will usually cause vents all over the station to lock out, even if the pressure doesn't decrease substantially. This causes repressurisation to be almost impossible and require player intervention to manually unlock vents.
Reproduction
Somewhat difficult to reproduce reliably but it seems to occur after 'large' explosions (ranging from meteors to syndiebombs at the edges of the station), which will cause lockouts in a much larger radius. Needs further testing to check air alarms and pressure readings.
The text was updated successfully, but these errors were encountered: