Goonhub
As far as I know, air, on turfs, processes once every second now.
That said, there's a lot of atmospheric machinery, such as canisters, coolers, furnaces, scrubbers, pumps, and the works, that are on the machine controller, meaning they only fire once every 3.3 seconds.
likewise, pipenets themselves are within the machine controller, which also means they fire once every 3.3 seconds.
This would require some changes; there's a few atmospherics machinery that aren't explicitly /obj/machinery/atmospherics.
I'd suggest moving most atmospheric machinery and pipenets to the air controller, so that it all processes, as a unified system, and in sync.
There's probably be a few things that would have to be adjusted; for instance, it's probably best that cryo cell's occupant processing is still in sync with the machine controller, but the air mechanics of cryo is processed with the rest of atmospherics machinery (likewise, the generator should probably stay a 3.3 second entity).
This would help atmospherics feel a little bit more "real time", while also unifying the processing; a benefit of this is that if the air system lags, its tick gets delayed, as an entire controller (and thus, again, the system stays in unison) rather than being broken up across multiple controllers.
That said, there's a lot of atmospheric machinery, such as canisters, coolers, furnaces, scrubbers, pumps, and the works, that are on the machine controller, meaning they only fire once every 3.3 seconds.
likewise, pipenets themselves are within the machine controller, which also means they fire once every 3.3 seconds.
This would require some changes; there's a few atmospherics machinery that aren't explicitly /obj/machinery/atmospherics.
I'd suggest moving most atmospheric machinery and pipenets to the air controller, so that it all processes, as a unified system, and in sync.
There's probably be a few things that would have to be adjusted; for instance, it's probably best that cryo cell's occupant processing is still in sync with the machine controller, but the air mechanics of cryo is processed with the rest of atmospherics machinery (likewise, the generator should probably stay a 3.3 second entity).
This would help atmospherics feel a little bit more "real time", while also unifying the processing; a benefit of this is that if the air system lags, its tick gets delayed, as an entire controller (and thus, again, the system stays in unison) rather than being broken up across multiple controllers.
