Инсталирайте Steam
вход
|
език
Опростен китайски (简体中文)
Традиционен китайски (繁體中文)
Японски (日本語)
Корейски (한국어)
Тайландски (ไทย)
Чешки (Čeština)
Датски (Dansk)
Немски (Deutsch)
Английски (English)
Испански — Испания (Español — España)
Испански — Латинска Америка (Español — Latinoamérica)
Гръцки (Ελληνικά)
Френски (Français)
Италиански (Italiano)
Индонезийски (Bahasa Indonesia)
Унгарски (Magyar)
Холандски (Nederlands)
Норвежки (Norsk)
Полски (Polski)
Португалски (Português)
Бразилски португалски (Português — Brasil)
Румънски (Română)
Руски (Русский)
Финландски (Suomi)
Шведски (Svenska)
Турски (Türkçe)
Виетнамски (Tiếng Việt)
Украински (Українська)
Докладване на проблем с превода
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.