ติดตั้ง 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 (เวียดนาม)
Українська (ยูเครน)
รายงานปัญหาเกี่ยวกับการแปลภาษา
I'm sorry if my English got things confusing on any point, but it isn't my mother language :( ... also, excuse me for the amount of comments... But it was the only way to post these thoughts since there's a 1000 characters limit for comments...
**10th: "Delay" feature on logic blocks will start its counting since the first active input it is receiving, even if that input is not enough to activate the block's output. This means, for example, that if having a constant ON sensor outputting 1 to an AND gate called X, and another logic block outputs 1 to X after a few seconds, the AND gate X will output 1 immediatly even if it has a delay activation time of 1 second set, since it counted that from the sensor's outputs and not the second block validating the AND function. This is IMPORTANT! It leads to many errors.
**7th: Speed sensors only measure "Linear velocity", so they can behave "weird" on very specific situations.
**8th: Having multiple seats in a build change the way logic gates keybinded inputs are evaluated. For example, if having two seats and one AND gate whose keybinded input is W, the AND gate will only input 1 if both SEATS are inputting W. This can be a headache to people who don't know it, since some circuits would stop working if AND gates to receive inputs from the user.
**5th: OR gates with toggle activated can be used as a latch/memory bit. The only requirement for this to work is that the block that gives input to them must have an active time of "0.02 seconds" (so it will send a pulse instead of a constant output). This requirement is already fulfilled by sensors, since they only send pulses.
**3rd: "Delay...", "active time..." and "time before..." functions are bugged, and they'll only work if at least two of their values are different from zero. However, if only one of those features is wanted to be used, this can be fixed by typing "0.0000001" in the "delay" rectangle. It is a really low number and won't have any noticeable effect on action.