安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
this will turn the switch on and off several times per second, according to your framerate. if you are running at 60fps, the switch will turn itself on and off (1 & 0) about 60 times per second. What you do is set up another math brick for whatever you are tying it to. For example, if you had a thruster controlled by speed you would set up a math brick to multiply the output of the speed sensor by the output of the clock math brick. Or, if you wanted to simply silence thrusters connected to throttle, you would set up a multiply math brick, with input A to the clock math brick, and input B to simply be throttle.
The way it functions is of course by multiplying the sensor's output by 1 and 0 unbelievably fast. This toggles the thruster on and off so quickly that it doesn't have time to render sound or smoke.
[
min in: 1
max in: 0
min out: 1.1
max out: 0
]
with the input channel tied to a math brick (we will call this the clock math brick)
[
operation: greater
input A: disable steering (this bind will enable the clock - if you want it to be always on, simply set it to a constant value of 1)
input B: output channel, tie it to the clock switch
]
I am trying to replicate the system, but I didn't understand.
btw its just for the throttle, because I pretend to make a PBR and also to emulate this as a hybrid system