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
So maybe your condition component doesn't handle the "always" condition correctly?
To debug it, set a breakpoint at one (or both) of the "checkForRats always" lines (click at the very beginning of the line and a red dot should appear), then click Run / F6 and it will run up to that line and pause there.
As it will have paused on the register loading with the label value (i.e. on "checkForRats"), click Next / F5 once so it advances forward to the "always" branch instruction.
(alternatively, you could also move your "always" instruction onto a separate line; that way you could set a breakpoint directly at the "always")
In that state, check the output of your condition component. It ought to output a 1 / On. It's possible that it doesn't, which would mean it ignores the branch.
If it is indeed 1 / On, though, it might be that your branching circuitry fails to load a new value into the counter in another way. So also check that your Counter's "Overwrite" input receives a 1 / On signal.
I also played around a bit with "The Lab" (don't remember when it unlocks), but I only came up with a convoluted way to test jumps/branches and wasn't able to use expect with the program counter. So I guess the usefulness of "The Lab" for testing jumps and branches is currently limited.