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
EDIT: Okay, I understand your answer now. You mean I create a feedback loop between two OR gates that creates a little memory cell that can be adjusted by other outputs (another OR gate, a seat, a sensor, etc.). Thanks for pointing this out; my brain works better with typed code than with circuits and blocks.
EDIT 2: This becomes too cumbersome too quickly. The suggestion is still a nice one that would have its applications for sure.
I first heard of this idea from the YouTuber Yzuei. Here's the link to a video where Yzuei incorporates this throttle mechanism into an F-35 creation of his (try skipping to 1:28 in the video to see his explanation of the throttle):
https://youtu.be/KZKDhMRE0zQ?t=89
Using pistons takes more space and complexity, uses the space in a less flexible way (blocks must be in a specific position relative to eachother rather than where they fit like pure logic circuits), is slower to update, and has less finer control (4 values vs thousands)