Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=3369638879
The differences between the ROS#0 and this ROS#1 are:
[olist]
[*] it only makes one layer per platform, instead of two, but, it can crystalize it.
[*] it requires 4x platforms for a group making 4-layers, instead of two
[*] it has the same shapes+paint inputs on one side, but the other side only has paint for crystalizing
[/olist]
This one also uses back-to-back MAMs so the supply trains can deliver to both at once and then loop around to deliver to the other side.
The ROS#0 is 6x platforms, and this ROS#1 is 12x platforms, so, they can be tiled together with the same grid. The ROS#0's will be back-to-back to be the same length as a single ROS#1. Then, the two ROS#1's are back-to-back with space in between for the nearby ROS#0 outputs. It requires 4x ROS#0's to use the same length as the two ROS#1's.
They both use static mixing for faster changeover than dynamic mixing.