Skip to content
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 set to a different frequency are still available to all air alarms. #11953

Closed
kyrahabattoir opened this issue Sep 23, 2015 · 3 comments
Closed
Labels
Bug Correct Functionality Tested/Reproduced There might be a hope in hell of getting this fixed.

Comments

@kyrahabattoir
Copy link
Contributor

They cannot be controlled but are still listed in the individual vent control section.

@Dorsisdwarf Dorsisdwarf added Bug Correct Functionality Atmos Needs Reproducing Nobody will fix your issue unless you do this labels Sep 23, 2015
@kyrahabattoir
Copy link
Contributor Author

Reproduction process:

In a map put multiple air alarms and vents in the same area but group the vents to different air alarms (lets say 1 vent 1 scrubber per alarm)
Unlock the air alarm and use one of the presets (panic syphon, etc...) only the frequency matched vents will respond.

Check the individual vent/scrubber settings: all the vents/scrubbers in the area will show, but only the frequency matched ones will actually "obey" to controls. Seems to me that the UI doesn't filter out vents that do not match the air alarm frequency.

@Dorsisdwarf
Copy link
Contributor

I'm pretty sure there are supposed to only ever be one air alarm per area, and that that's enforced by code limits on building them.

@kyrahabattoir
Copy link
Contributor Author

The mapping primer say that multiple air alarms are ok if you assign them their own vents through frequencies.

And if you check on box, there is a bunch of areas with multiple air alarms sharing vents (i'm still convinced that without separating them by frequency, that's bad)

@Dorsisdwarf Dorsisdwarf added Tested/Reproduced There might be a hope in hell of getting this fixed. and removed Needs Reproducing Nobody will fix your issue unless you do this labels Sep 24, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Correct Functionality Tested/Reproduced There might be a hope in hell of getting this fixed.
Projects
None yet
Development

No branches or pull requests

2 participants