If signals are placed on both sides but not opposite to each other the track becomes a "no-way" track: it can't be used by automatic trains but still traversed manually. If signals are only placed on one side the track becomes one-way. The example below shows two different two-way tracks. That said, a two-way rail system will get you really far, by the time you may start to need to upgrade to a serious dual-lane system you'll probably have a small army of construction bots at your disposal to do the upgrade anyway.Īs automatic trains can only pass signals if they're on their right, a two-way stretch of track needs either opposing signals or no signals. A pretty basic one-way dual track system will likely support at least 10x the throughput of a two-way system, a well designed one will support even more. The main drawback is, of course, throughput. Compared to one-way dual-track systems you'll save about 50% on the rails an probably at least 75% on signals, not much in the grand scheme of things but noticeable during the initial setup. The main motivation for using two-way rails is that they're cheap and super easy to build, especially before bots and blueprints. Hopefully this will cover the most common pitfalls but if I've missed something, or if something is unclear, please let me know and I'll try to include/fix that. This guide aims to explain how to set up simple and reliable two-way rail systems, how to signal/schedule them to avoid deadlocks and some techniques to address throughput issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |