安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
0 
举报此帖
I haven't tested it in multiplayer at all since survival mode came out. I noticed vanilla logic gates have the exact same problem you're describing when changing their state repeatedly.
I'll do some more investigating when I have the time for it.
And yeah we noticed that too, 0 tick logic clocks are pushing the latency really fast.
For a quick fix I'd just change the last else to elseif and compare the current value to the previous as the previous if statements already do that, or just simply wrap it all up in a check if it's changed at all
EDIT: That's under XYZ_Converter.server_onFixedUpdate()
EDIT:
I wrapped a change statement around each update, as mentioned by @Faupi, so it only triggers once, if you press/release the button. That will fix most, if not all lag that would build up. But I didn't tested this yet.
I also found out, that the A and D Converter where broken in survival, because the getPoseWeight() function is out of bounds with the new seats. You have to use getSteeringAngle() to get them work in survival. They output integer between -1 and 1 just like getPower() and work with the old seats, too.
The setPower() function doesn't work with the new survival engines anymore. They require isActive() to receive power with setPower(). You could redefine some function, but changing the WASD Converters back to Logic Output only again and adding Steer and Power Converters for Power Outputs would be the easier approach.