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.