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
It means sending a constant signal of what is on the belt, as opposed to "pulse" that sends a short signal when an item enters the belt.
If your belt carries iron plates for example, the signal will be the amount of iron plates that are on the belt, on the "iron plates" signal.
As for the 50%, a belt can have up to 4 items at once per lane, so 8 in total so using "iron plates >= 4" for the enable condition would mean "enable this belt when there are at least 4 iron plates in the signals", and since the signal is the content of the other belt, it would do what you want.
Belt 1:
Check Read Belt Contents
Check Hold
Belt 2:
Check Enable/disable
Set product >= 4
Expectation is that belt 2 would stop producing if Belt 1 was low on product.
No matter the status of the belt, it still runs.
well you set it to: "<=" so it will run until 4 or more
I want to enable it when there are at least 4 items on the other belt.
"at least" means that the number should be 4 or higher, so ">=4".