安装 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(越南语)
Українська(乌克兰语)
报告翻译问题










Also, the error tooltip on the microcontroller just tells you when the PID is attempting to output a value outside the 0-1 range for the throttle. The reason you see a short flicker is because there is a 1 tick delay between each of the components of a microcontroller so it takes a couple ticks for the controller to detect the out of range condition and then clamp it to 0-1.
https://i.gyazo.com/1d6250f83f8e5add1150c4a95975be57.mp4
This is a video, although it did flicker the negative number on every bang for me (I think at 30fps it won't 'capture' every tick on the recording software).
Ultimately it will spend a lot of time backfiring, usually, when close to the speed it's trying to achieve.
shut down or have any issues. It's not something that occurs when using the throttle manually.
I tried monitoring the microcontroller and the Error YES flashes when this occurs, but the throttle value seems to remain at least the idle if not slightly higher throttle setting. I've had a play with the coef and it doesn't seem to make much difference.
If you didn't have audio you wouldn't notice anything out of ordinary. Any thoughts?