Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
You can connect two switches to the final output.
Spoiler:
Connect input one to switch one's input. Connect input two to a not, then to the first switch's toggle.
Connect input two to switch two's input. Connect input one to a not, then to the second switch's toggle.
Connect both switches to the final output.
That's exactly what I did. The problem is that on the 4th tick (both inputs on), the two switches are both giving no output (grey) instead of off (red) due to the switch toggles (bottom inputs) being off. This causes a combined output of grey rather than off.
I can move the NOTs to before the primary inputs of the switches, but that causes the same issue on the first tick (both inputs off).
(For context, I've beaten this game up to the point of building a custom 64-bit architecture with variable instruction width on the stable build)
I haven't found one, sadly. My friend and I spent half an hour on call trying to find an alternative design/workaround, but we got nowhere.