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
Personally I would put the switchboxes in chain cycle and cycle them per tick.
Also maybe use one of the channels on each composite as an index so you can easily identiy which one you're currently reading.
Here's a good example of tick based multiplexing with regular logic, not composite but the idea is the same:
https://steamcommunity.com/sharedfiles/filedetails/?id=1416526228
The only thing to watch out for is that you'll get some input delay if you put too much things in chain. (1 tick for each block or logic gate the signal passes through)
Multiplexing on the other hand is mainly useful when you need to pipe more than 32 inputs through a composite connection, which is rarely necessary.